From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "Zhao, Forrest" <forrest.zhao@intel.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix oops caused rescanning NULL sdev
Date: Mon, 12 Jun 2006 10:23:58 -0400 [thread overview]
Message-ID: <448D78FE.4020806@pobox.com> (raw)
In-Reply-To: <20060612135114.GC5751@htj.dyndns.org>
Tejun Heo wrote:
> Depending on timing, ata_scsi_dev_rescan() might encounter a device
> which is enabled but not yet attached to sdev. On such cases, the
> original code caused oops. This patch makes ata_scsi_dev_rescan()
> rescan only device which are attached to sdevs.
>
> While at it, properly indent leading comment and add description about
> how it's synchronized with sdev attach/detach.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
applied
prev parent reply other threads:[~2006-06-12 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 13:51 [PATCH] libata: fix oops caused rescanning NULL sdev Tejun Heo
2006-06-12 14:23 ` Jeff Garzik [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=448D78FE.4020806@pobox.com \
--to=jgarzik@pobox.com \
--cc=forrest.zhao@intel.com \
--cc=htejun@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).