From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: Jens Axboe <axboe@suse.de>, linux-ide@vger.kernel.org
Subject: Re: Crash in ide_do_request() on card removal
Date: Tue, 2 Aug 2005 15:28:50 +0200 [thread overview]
Message-ID: <58cb370e05080206282af4cf0a@mail.gmail.com> (raw)
In-Reply-To: <42EF69AD.30201@imc-berlin.de>
On 8/2/05, Steven Scholz <steven.scholz@imc-berlin.de> wrote:
> Jens Axboe wrote:
> do_ide_request() could check hwif->present and/or drive->present.
> BUT: at this point the request is already made and the low level block layer is
> sleeping and waiting for it's completion.
> I could not figure out how to kill a request in do_ide_request() and wake up the
> block layer (sleeping in __wait_on_buffer()).
> That's why I thought preventing the generation of such reuqests would be the
> right way.
>
> > I suggest you take it up with Bart how best to solve this. He might even
> > already have patches.
> Bart? Are you there?
IDE device unplug TODO :)
* add ide_device_get() helper which will check for drive->present
+ increase reference count on drive->gendev and ide_device_put()
helper which will decrease reference count on drive->gendev
* propagate usage of these helpers to device drivers (ide_disk_get() etc.)
so there won't be _new_ requests after removal of the device
* if !drive->present fail _old_ requests (as already mentioned by Jens)
* add proper locking around drive->present
* ...
first three points should be relatively easy
Bartlomiej
next prev parent reply other threads:[~2005-08-02 13:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 12:01 Crash in ide_do_request() on card removal Steven Scholz
2005-08-02 9:57 ` Steven Scholz
2005-08-02 10:48 ` Jens Axboe
2005-08-02 11:10 ` Steven Scholz
2005-08-02 11:13 ` Jens Axboe
2005-08-02 11:17 ` Steven Scholz
2005-08-02 11:28 ` Jens Axboe
2005-08-02 11:30 ` Steven Scholz
2005-08-02 11:33 ` Jens Axboe
2005-08-02 12:09 ` Steven Scholz
2005-08-02 12:26 ` Jens Axboe
2005-08-02 12:40 ` Steven Scholz
2005-08-02 12:54 ` Jens Axboe
2005-08-02 13:03 ` Steven Scholz
2005-08-02 13:06 ` Jens Axboe
2005-08-02 13:38 ` Steven Scholz
2005-08-02 13:45 ` Jens Axboe
2005-08-02 13:54 ` Steven Scholz
2005-08-02 14:11 ` Jens Axboe
2005-08-08 9:00 ` Steven Scholz
2005-08-02 13:28 ` Bartlomiej Zolnierkiewicz [this message]
2005-08-18 12:59 ` Steven Scholz
2006-01-31 14:28 ` Steven Scholz
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=58cb370e05080206282af4cf0a@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=axboe@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=steven.scholz@imc-berlin.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 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).