This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Oops from loop driver on IA64

To: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Oops from loop driver on IA64
From: Kouya SHIMURA <kouya@xxxxxxxxxxxxxx>
Date: Tue, 18 Apr 2006 19:41:55 +0900
Cc: Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Tue, 18 Apr 2006 03:42:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

We encounter a Oops message from loop driver when vbd is used
in dom0 kernel with CONFIG_VIRTUAL_MEM_MAP on ia64.

I investigated this and might find a serious bug.
On x86, flush_dcache_page() does nothing and there is no problem.
But on ia64 flush_dcache_page() might access a wrong page struct
and destroy the kernel memory.

Attached patch fixes this problem but it seems bad idea to modify
a linux driver. How should we fix it?


Signed-off-by: Kouya Shimura <kouya@xxxxxxxxxxxxxx>

Attachment: loop.patch
Description: Binary data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>