From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Decotigny <decot@googlers.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: avoid use of reclaimed reference
Date: Tue, 12 Nov 2013 17:57:10 -0800 [thread overview]
Message-ID: <1384307830.2248.17.camel@dabdike> (raw)
In-Reply-To: <643cda2192c25962f37c8bba65e22f70a57167d0.1384304973.git.decot@googlers.com>
On Tue, 2013-11-12 at 17:10 -0800, David Decotigny wrote:
> This patch avoids to use an object after it was potentially reclaimed
> by scsi_device_put().
The analysis is wrong, I'm afraid. __scsi_remove_device() does the
final put for devices that are being destroyed. If the device isn't in
the created state, then it's long lived and nothing in the report lun
scan does the final put.
James
next prev parent reply other threads:[~2013-11-13 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1384304973.git.decot@googlers.com>
2013-11-13 1:10 ` [PATCH] scsi: avoid use of reclaimed reference David Decotigny
2013-11-13 1:57 ` James Bottomley [this message]
2013-11-13 2:09 ` David Decotigny
2013-11-13 6:46 ` James Bottomley
2013-11-13 12:06 ` Bart Van Assche
2013-11-14 2:50 ` David Decotigny
2013-11-14 6:15 ` James Bottomley
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=1384307830.2248.17.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=decot@googlers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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