From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, Martin Wilck <mwilck@suse.com>,
Steffen Maier <maier@linux.ibm.com>,
Hannes Reinecke <hare@suse.de>,
Sachin Sant <sachinp@linux.ibm.com>,
Benjamin Block <bblock@linux.ibm.com>
Subject: Re: [PATCH] scsi: core: Fix the scsi_device_put() might_sleep annotation
Date: Thu, 26 Jan 2023 22:22:12 -0500 [thread overview]
Message-ID: <167478903314.4070509.17553562843256554477.b4-ty@oracle.com> (raw)
In-Reply-To: <20230125194311.249553-1-bvanassche@acm.org>
On Wed, 25 Jan 2023 11:43:11 -0800, Bart Van Assche wrote:
> Although most calls of scsi_device_put() happen from non-atomic context,
> alua_rtpg_queue() calls this function from atomic context if
> alua_rtpg_queue() itself is called from atomic context. alua_rtpg_queue()
> is always called from contexts where the caller must hold at least one
> reference to the scsi device in question. This means that the reference
> taken by alua_rtpg_queue() itself can't be the last one, and thus can be
> dropped without entering the code path in which scsi_device_put() might
> actually sleep. Hence move the might_sleep() annotation from
> scsi_device_put() into scsi_device_dev_release().
>
> [...]
Applied to 6.2/scsi-fixes, thanks!
[1/1] scsi: core: Fix the scsi_device_put() might_sleep annotation
https://git.kernel.org/mkp/scsi/c/2542fc9578d4
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-01-27 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 19:43 [PATCH] scsi: core: Fix the scsi_device_put() might_sleep annotation Bart Van Assche
2023-01-25 20:03 ` Martin Wilck
2023-01-27 3:22 ` Martin K. Petersen [this message]
2023-01-30 7:58 ` Christoph Hellwig
2023-01-30 17:04 ` Martin Wilck
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=167478903314.4070509.17553562843256554477.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bblock@linux.ibm.com \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.ibm.com \
--cc=mwilck@suse.com \
--cc=sachinp@linux.ibm.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 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.