Public bug reported: Binary package hint: linux-source-2.6.22
When xen in combination with xfs is used, the problem described in http://lkml.org/lkml/2007/10/12/298 leads quite fast to crashes with very hard to associate backtraces (as they just need to use vmap somewhere, if I have understood the problem correctly). If you wish I can attach some of them textually, and more as images (I have an remote access card which allows to take images - quite often I could not directly access any consoles anymore). After applying the patch out of this mail http://lkml.org/lkml/2007/10/12/310 the kernel survives till now (20 hours of generated high io load) when earlier under IO it survived for approx 30 minutes (sometimes didnt even boot up). As this bug causes random crashes, can lead to data corruption, is hard to diagnose and the fix is obviously correct I would suggest adding the patch at least to the xen custom flavour if not to the normal kernel for gutsy. diff -urNd linux-source-2.6.22-2.6.22/debian/binary-custom.d/xen/patchset.old/004-xfs_vmfree.patch linux-source-2.6.22-2.6.22/debian/binary-custom.d/xen/patchset/004-xfs_vmfree.patch --- linux-source-2.6.22-2.6.22/debian/binary-custom.d/xen/patchset.old/004-xfs_vmfree.patch 1970-01-01 01:00:00.000000000 +0100 +++ linux-source-2.6.22-2.6.22/debian/binary-custom.d/xen/patchset/004-xfs_vmfree.patch 2007-11-23 21:11:12.000000000 +0100 @@ -0,0 +1,14 @@ +diff -urNd custom-source-xen{,old}/fs/xfs/linux-2.6/xfs_buf.c +--- custom-source-xen.old/fs/xfs/linux-2.6/xfs_buf.c 2007-11-23 21:06:08.000000000 +0100 ++++ custom-source-xen/fs/xfs/linux-2.6/xfs_buf.c 2007-11-23 21:05:32.000000000 +0100 +@@ -184,6 +184,10 @@ + { + a_list_t *aentry; + ++#ifdef CONFIG_XEN ++ vunmap(addr); ++ return; ++#endif + aentry = kmalloc(sizeof(a_list_t), GFP_NOWAIT); + if (likely(aentry)) { + spin_lock(&as_lock); ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New ** Tags: xen -- stray mappings left behind by xfs make xen kernels crash. https://bugs.launchpad.net/bugs/164904 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
