Message-Id: <1170865619.16808.1173403963@webmail.messagingengine.com>
From: "Kai" <epimetreus@fastmail.fm>
To: linux-kernel@vger.kernel.org
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
References: <1170734919.15636.1173102761@webmail.messagingengine.com>
   <20070205203750.7be7f772.akpm@linux-foundation.org>
   <17864.4339.925700.626157@notabene.brown>
   <17865.3776.511594.763544@notabene.brown>
Subject: Re: [PATCH] Re: Bio device too big | kernel BUG at mm/filemap.c:537!
In-Reply-To: <17865.3776.511594.763544@notabene.brown>
Date: Wed, 07 Feb 2007 08:26:59 -0800
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1192
Lines: 29


On Wed, 7 Feb 2007 10:26:56 +1100, "Neil Brown" <neilb@suse.de> said:
> On Tuesday February 6, neilb@suse.de wrote:
> > 
> > This patch should fix the worst of the offences, but I'd like to
> > experiment and think a bit more before I submit it to stable.
> > And probably test it too - as yet I have only compile and brain
> > tested.
> 
> Ok, I've experimented and tested and now I know what was causing the
> double-unlock.
> 
> The following patch is suitable for 2.6.20.1 and mainline.  There is
> room for a bit more improvement, but only for performance, not
> correctness.  I'll look into that later.
> 
> Thanks,
> NeilBrown

I figure I should test this on my hardware, but since the RAID array
resynched itself when I rebooted back into an earlier kernel version,
I'm guessing it means this bug introduced some corruption into the
array, when it occurred, so I'd like some pointers on how I can test it
out without compromising my data.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/