Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: bvanassche@acm.org
Cc: linux-scsi@vger.kernel.org
Subject: [bug report] scsi: core: Release SCSI devices synchronously
Date: Wed, 26 Oct 2022 16:58:17 +0300	[thread overview]
Message-ID: <Y1k8+fDG7FFOnbBG@kili> (raw)

Hello Bart Van Assche,

The patch f93ed747e2c7: "scsi: core: Release SCSI devices
synchronously" from Oct 14, 2022, leads to the following three Smatch
static checker warnings:

1) drivers/scsi/bfa/bfad_bsg.c:2551 bfad_iocmd_lunmask_reset_lunscan_mode() warn: sleeping in atomic context

bfad_iocmd_lunmask() <- disables preempt
-> bfad_iocmd_lunmask_reset_lunscan_mode()
   -> scsi_device_put()

(This is inside the calls to bfad_reset_sdev_bflags() macro).

2) drivers/scsi/device_handler/scsi_dh_alua.c:853 alua_rtpg_select_sdev() warn: sleeping in atomic context

alua_rtpg_work() <- disables preempt
-> alua_rtpg_select_sdev()
   -> scsi_device_put()

3) drivers/scsi/device_handler/scsi_dh_alua.c:1013 alua_rtpg_queue() warn: sleeping in atomic context

alua_check_vpd() <- disables preempt
-> alua_rtpg_queue()
   -> scsi_device_put()

Hopefully, this bug report is straight forward.  The fixes are probably
complicated though.  :P Basically the function marked "disables preempt"
takes a spin lock and calls the other function which calls
scsi_device_put().

regards,
dan carpenter

             reply	other threads:[~2022-10-26 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 13:58 Dan Carpenter [this message]
2022-10-26 18:39 ` [bug report] scsi: core: Release SCSI devices synchronously Bart Van Assche

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=Y1k8+fDG7FFOnbBG@kili \
    --to=dan.carpenter@oracle.com \
    --cc=bvanassche@acm.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