From: Mike Fedyk <mfedyk@matchmail.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: md: bug in file raid5.c, line 540 was: Re: Linux 2.4.22-rc1
Date: Fri, 22 Aug 2003 14:26:59 -0700 [thread overview]
Message-ID: <20030822212659.GK1040@matchmail.com> (raw)
In-Reply-To: <20030822155039.GA6980@marowsky-bree.de>
On Fri, Aug 22, 2003 at 05:50:39PM +0200, Lars Marowsky-Bree wrote:
> On 2003-08-22T15:24:46,
> Neil Brown <neilb@cse.unsw.edu.au> said:
>
> > This bug could happen if you try to fail a device that is not active.
>
> Yes, thats not generally a tested code path in 2.4. On removing the
> BUG() statement, also check that all counters get in/decremented
> correctly, or the next lurking bug will hit you.
>
> I fixed that for multipath in 2.4 too, but I can't get around to clean
> up the patchset *sigh*
Then send the patch to someone who can...
Has anyone attempted to create a testbed for md? If not, can you list all
of the states, and state transitions that are legal. I might be able to
cook something up when I get some time.
next prev parent reply other threads:[~2003-08-22 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 18:44 Linux 2.4.22-rc1 Marcelo Tosatti
2003-08-07 10:56 ` Erik Heinz
[not found] ` <20030819202629.GA4083@matchmail.com>
2003-08-19 21:09 ` md: bug in file raid5.c, line 540 was: " Mike Fedyk
2003-08-22 5:24 ` Neil Brown
2003-08-22 15:50 ` Lars Marowsky-Bree
2003-08-22 21:26 ` Mike Fedyk [this message]
2003-08-23 15:28 ` Lars Marowsky-Bree
2003-08-26 17:22 ` Mike Fedyk
2003-08-26 17:30 ` Lars Marowsky-Bree
2003-08-19 21:18 ` md: bug in file raid5.c, line 1909 " Mike Fedyk
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=20030822212659.GK1040@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=marcelo@conectiva.com.br \
--cc=neilb@cse.unsw.edu.au \
/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).