From: Neil Brown <neilb@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org,
Torsten Kaiser <just.for.lkml@googlemail.com>,
mingo@redhat.com, linux-raid@vger.kernel.org
Subject: Re: do_md_run returned -22 [Was: 2.6.24-rc8-mm1]
Date: Fri, 18 Jan 2008 10:15:32 +1100 [thread overview]
Message-ID: <18319.57748.532354.179523@notabene.brown> (raw)
In-Reply-To: message from Andrew Morton on Thursday January 17
On Thursday January 17, akpm@linux-foundation.org wrote:
> On Thu, 17 Jan 2008 16:23:30 +0100 Jiri Slaby <jirislaby@gmail.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
prev parent reply other threads:[~2008-01-17 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080117023514.9df393cf.akpm@linux-foundation.org>
2008-01-17 15:23 ` do_md_run returned -22 [Was: 2.6.24-rc8-mm1] Jiri Slaby
2008-01-17 19:01 ` Andrew Morton
2008-01-17 23:15 ` Neil Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18319.57748.532354.179523@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).