[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18319.57748.532354.179523@notabene.brown>
Date: Fri, 18 Jan 2008 10:15:32 +1100
From: Neil Brown <neilb@...e.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Jiri Slaby <jirislaby@...il.com>, linux-kernel@...r.kernel.org,
Torsten Kaiser <just.for.lkml@...glemail.com>,
mingo@...hat.com, linux-raid@...r.kernel.org
Subject: Re: do_md_run returned -22 [Was: 2.6.24-rc8-mm1]
On Thursday January 17, akpm@...ux-foundation.org wrote:
> On Thu, 17 Jan 2008 16:23:30 +0100 Jiri Slaby <jirislaby@...il.com> wrote:
>
> > On 01/17/2008 11:35 AM, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc8/2.6.24-rc8-mm1/
> >
> > still the same md issue (do_md_run returns -22=EINVAL) as in -rc6-mm1 reported
> > by Thorsten here:
> > http://lkml.org/lkml/2007/12/27/45
>
> hm, I must have been asleep when that was reported. Neil, did you see it?
No, even though it was Cc:ed to me - sorry.
Maybe a revised subject line would have helped... maybe not.
>
> > Is there around any fix for this?
>
> Well, we could bitbucket md-allow-devices-to-be-shared-between-md-arrays.patch
Yeah, do that. I'll send you something new.
I'll move that chunk into a different patch and add the extra bits
needed to make that test correct in *all* cases rather than just the
ones I was thinking about at the time.
My test suit does try in-kernel-autodetect (the problem case) but it
didn't catch this bug due to another bug. I'll fix that too.
Thanks,
NeilBrown
--
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