linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Steven Dake <sdake@mvista.com>, linux-raid@vger.kernel.org
Subject: Re: raid1 critical sections not protected in 2.4.x?
Date: Fri, 10 Oct 2003 10:14:46 +0200	[thread overview]
Message-ID: <20031010081445.GC29059@marowsky-bree.de> (raw)
In-Reply-To: <1065721318.4761.138.camel@persist.az.mvista.com>

On 2003-10-09T10:41:59,
   Steven Dake <sdake@mvista.com> said:

> I have been looking at the raid1.c code.  There is a kernel thread
> raid1d that could be scheduled on processor A.  Then on processor B,
> other raid code could be scheduled as per each block I/O request.

Did you follow the recent locking fixes to md I discussed with Neil? I
think this fixes some of these; at least we have a confirmation from IBM
that some raid1 races (not resyncing after a hotadd, no progress during
resync etc) went away with it.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering		ever tried. ever failed. no matter.
SuSE Labs				try again. fail again. fail better.
Research & Development, SUSE LINUX AG		-- Samuel Beckett

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2003-10-10  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 17:41 raid1 critical sections not protected in 2.4.x? Steven Dake
2003-10-10  8:14 ` Lars Marowsky-Bree [this message]
2003-10-13 21:29   ` Steven Dake
2003-10-14  7:13     ` Lars Marowsky-Bree

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=20031010081445.GC29059@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=sdake@mvista.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).