From: Christoph Hellwig <hch@infradead.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: "James E.J. Bottomley" <JBottomley@odin.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
"K. Y. Srinivasan" <kys@microsoft.com>,
Bart Van Assche <bart.vanassche@sandisk.com>
Subject: Re: [PATCH RESEND_2] scsi_sysfs: protect against double execution of __scsi_remove_device()
Date: Thu, 19 Nov 2015 05:40:37 -0800 [thread overview]
Message-ID: <20151119134037.GA12247@infradead.org> (raw)
In-Reply-To: <1447938139-22072-1-git-send-email-vkuznets@redhat.com>
This looks fine to me. I wonder why we even bother returning
deleted devices for a normal scsi_device_lookup, but let's get
this isolated fix in for now and sort out the big picture later.
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2015-11-19 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 13:02 Vitaly Kuznetsov
2015-11-19 13:40 ` Christoph Hellwig [this message]
2015-11-19 17:16 ` Martin K. Petersen
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=20151119134037.GA12247@infradead.org \
--to=hch@infradead.org \
--cc=JBottomley@odin.com \
--cc=bart.vanassche@sandisk.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vkuznets@redhat.com \
/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
all inboxes | Powered by JetHome®