[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CB745FC.5090504@gmail.com>
Date: Thu, 14 Oct 2010 20:03:40 +0200
From: Tejun Heo <htejun@...il.com>
To: richard -rw- weinberger <richard.weinberger@...il.com>
CC: Chris Frey <cdfrey@...rsquare.net>,
Jens Axboe <jaxboe@...ionio.com>,
Richard Weinberger <richard@....at>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jdike@...toit.com" <jdike@...toit.com>,
"user-mode-linux-devel@...ts.sourceforge.net"
<user-mode-linux-devel@...ts.sourceforge.net>,
"user-mode-linux-user@...ts.sourceforge.net"
<user-mode-linux-user@...ts.sourceforge.net>,
"janjaap@....nl" <janjaap@....nl>,
"geert@...ux-m68k.org" <geert@...ux-m68k.org>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"adobriyan@...il.com" <adobriyan@...il.com>,
"syzop@...nscan.org" <syzop@...nscan.org>
Subject: Re: [PATCH 1/1] um: ubd: Fix data corruption
Hello,
On 10/14/2010 04:20 PM, richard -rw- weinberger wrote:
> It does not work for me.
> But the error is a different one. :-)
> Without your patch I've never got this kernel trace.
>
> [ 59.850000] kworker/0:1: page allocation failure. order:0, mode:0x20
Hmm... you're seeing out of memory condition. If the code screws up
filesystem access, I suppose it could make that happen too but can you
please check the configuration just in case (especially the memory
size)? Also, if you can reliably reproduce the filesystem corruption
w/o the patch, can you please tell me how to do it?
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists