From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@suse.de>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Subject: Re: [PATCH] libata: fix use-after-free during driver unload/unplug
Date: Thu, 26 May 2005 21:32:32 -0400 [thread overview]
Message-ID: <429678B0.7000009@rtr.ca> (raw)
In-Reply-To: <42967601.7080003@pobox.com>
Jeff Garzik wrote:
>
> qstor's ->host_stop() disables global interrupts, and I didn't know if
> you really wanted to do that prior to ->port_stop().
>
> I would much prefer to eliminate the ->host_stop_prewalk() hook, and
> simply call ->host_stop after all ->port_stop() calls complete, if qstor
> doesn't need the pre-walk.
Ahh.. of course. I must have misread your original.
Yes, sata_qstor generally assumes that host_stop should completely
stop the host from operating.. and thereby expects any port_stop()
calls to happen before host_stop(). So, yup, the changes you have
seem to be useful here.
If we didn't want to have a prewalk() method, then we could hack
sata_qstor to keep a count of active ("non stopped") ports,
and automatically do the global (chip) interrupt disable from
port_stop() whenever the count hits zero.
Cheers
next prev parent reply other threads:[~2005-05-27 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 19:28 [PATCH] libata: fix use-after-free during driver unload/unplug Jeff Garzik
2005-05-26 21:33 ` Mark Lord
2005-05-27 1:21 ` Jeff Garzik
2005-05-27 1:32 ` Mark Lord [this message]
2005-05-27 2:00 ` [PATCH][RFT] " Jeff Garzik
2005-05-27 4:18 ` Jeff Garzik
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=429678B0.7000009@rtr.ca \
--to=liml@rtr.ca \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.