[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101007202339.GA8338@foursquare.net>
Date: Thu, 7 Oct 2010 16:23:39 -0400
From: Chris Frey <cdfrey@...rsquare.net>
To: Jens Axboe <jaxboe@...ionio.com>
Cc: Tejun Heo <htejun@...il.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
On Thu, Oct 07, 2010 at 09:58:16AM +0200, Jens Axboe wrote:
> So how about this? Note that I haven't even compiled this. The request
> handling logic really should be fixed in there, it's horribly
> inefficient.
Thanks. I fixed the compile error with:
> + .rq_offset 0, \
to
> + .rq_offset = 0, \
But after testing, I still got the same errors:
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 964816
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 964862
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 964786
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 964815
...
- Chris
--
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