linux-kernel - Re: 2.6.23.1: mdadm/raid5 hung/d-state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e9c3a7c20711081002k5c3be41doa700afce7c1a7a6e@mail.gmail.com>
Date:	Thu, 8 Nov 2007 11:02:36 -0700
From:	"Dan Williams" <dan.j.williams@...el.com>
To:	"Bill Davidsen" <davidsen@....com>
Cc:	"Jeff Lessem" <Jeff@...sem.org>,
	"BERTRAND Joël" <joel.bertrand@...tella.fr>,
	"Justin Piszcz" <jpiszcz@...idpixels.com>,
	"Neil Brown" <neilb@...e.de>, linux-kernel@...r.kernel.org,
	linux-raid@...r.kernel.org
Subject: Re: 2.6.23.1: mdadm/raid5 hung/d-state

On 11/8/07, Bill Davidsen <davidsen@....com> wrote:
> Jeff Lessem wrote:
> > Dan Williams wrote:
> > > The following patch, also attached, cleans up cases where the code
> > looks
> > > at sh->ops.pending when it should be looking at the consistent
> > > stack-based snapshot of the operations flags.
> >
> > I tried this patch (against a stock 2.6.23), and it did not work for
> > me.  Not only did I/O to the effected RAID5 & XFS partition stop, but
> > also I/O to all other disks.  I was not able to capture any debugging
> > information, but I should be able to do that tomorrow when I can hook
> > a serial console to the machine.
>
> That can't be good! This is worrisome because Joel is giddy with joy
> because it fixes his iSCSI problems. I was going to try it with nbd, but
> perhaps I'll wait a week or so and see if others have more information.
> Applying patches before a holiday weekend is a good way to avoid time
> off. :-(

We need to see more information on the failure that Jeff is seeing,
and whether it goes away with the two known patches applied.  He
applied this most recent patch against stock 2.6.23 which means that
the platform was still open to the first biofill flags issue.

--
Dan
-
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/