From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
Cc: Suresh Grandhi <Sureshg@ami.com>,
"'linux-ide@vger.kernel.org'" <linux-ide@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: IDE Hotswap
Date: Wed, 29 Sep 2004 18:46:23 +0100 [thread overview]
Message-ID: <1096479982.15905.71.camel@localhost.localdomain> (raw)
In-Reply-To: <200409292020.25192.bzolnier@elka.pw.edu.pl>
On Mer, 2004-09-29 at 19:20, Bartlomiej Zolnierkiewicz wrote:
> > Doesn't occur in the 2.4 situation or the 2.6 stuff with the locking in
> > the 2.6.8.1-ac patch.
>
> I will verify this in a few days, I have some real work to do first.
2.6 is the important stuff sure.
> > > - double unlock obvious mistake
> > Details ?
>
> 2003/08/16 alan | /* Drive shutdown sequence done */
> 2003/08/16 alan | /* Prevent new opens ?? */
> 2003/08/16 alan | spin_unlock_irqrestore(&io_request_lock, flags);
> 2003/08/16 alan | /*
> 2003/08/16 alan | * Flush kernel side caches, and dump the /proc files
> 2003/08/16 alan | */
> 2003/08/16 alan | spin_unlock_irqrestore(&io_request_lock, flags);
>
Thanks. I'll go over this when I dig out the one little bit 2.4.2x needs
for hotplug to behave right with hard disks that I should get to
Marcelo.
> OK BKL protects us against i.e. concurrent HDIO_GETGEO
> and hotplug ioctl. There is however no protection for controller
> hotplug.
Agreed.
prev parent reply other threads:[~2004-09-29 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8CCBDD5583C50E4196F012E79439B45C069657DB@atl-ms1.megatrends.com>
2004-09-28 21:38 ` IDE Hotswap Bartlomiej Zolnierkiewicz
2004-09-28 21:45 ` Alan Cox
2004-09-29 1:54 ` Bartlomiej Zolnierkiewicz
2004-09-29 1:50 ` Alan Cox
2004-09-29 12:08 ` Bartlomiej Zolnierkiewicz
2004-09-29 14:35 ` Alan Cox
2004-09-29 18:20 ` Bartlomiej Zolnierkiewicz
2004-09-29 17:46 ` Alan Cox [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=1096479982.15905.71.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Sureshg@ami.com \
--cc=bzolnier@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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