From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Race condition in write_sb_page?
Date: Mon, 20 Apr 2009 10:03:02 +0200 [thread overview]
Message-ID: <20090420080301.GA28593@darkside.22.kls.lan> (raw)
In-Reply-To: <dad4be16a03ccd96d073ecb16b937183.squirrel@neil.brown.name>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Mon, Apr 20, 2009 at 11:57:54AM +1000, NeilBrown wrote:
> The comment lists a number of conditions that are all true when
> something is remove from (or added to) the list. So we only need
> to be sure that one of these is true to be sure the thing wont be removed
Okay, I guess I just confused the component's descriptor index (desc_nr,
which changes when a resync finishes) and it's position in mddev->disks
(which doesn't change).
Mario
--
File names are infinite in length where infinity is set to 255 characters.
-- Peter Collinson, "The Unix File System"
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2009-04-20 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 18:15 Incorrect in-kernel bitmap on raid10 Mario 'BitKoenig' Holbe
2009-04-19 6:24 ` Neil Brown
2009-04-19 22:55 ` Mario 'BitKoenig' Holbe
2009-04-19 23:27 ` Neil Brown
2009-04-20 0:13 ` Race condition in write_sb_page? (was: Re: Incorrect in-kernel bitmap on raid10) Mario 'BitKoenig' Holbe
2009-04-20 1:57 ` NeilBrown
2009-04-20 8:03 ` Mario 'BitKoenig' Holbe [this message]
2009-04-22 18:45 ` Incorrect in-kernel bitmap on raid10 Mario 'BitKoenig' Holbe
2009-04-28 14:05 ` Mario 'BitKoenig' Holbe
2009-05-01 2:11 ` Neil Brown
2009-05-01 17:55 ` Mario 'BitKoenig' Holbe
2009-05-01 21:36 ` NeilBrown
2009-05-02 19:52 ` Mario 'BitKoenig' Holbe
2009-05-02 22:41 ` NeilBrown
2009-05-03 13:22 ` Mario 'BitKoenig' Holbe
2009-05-07 20:25 ` Mario 'BitKoenig' Holbe
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=20090420080301.GA28593@darkside.22.kls.lan \
--to=mario.holbe@tu-ilmenau.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.