From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
Mike Christie <michael.christie@oracle.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Himanshu Madhani <himanshu.madhani@oracle.com>
Subject: Re: [PATCH v2] scsi: target: Avoid smp_processor_id() in preemptible code
Date: Sat, 22 May 2021 00:40:34 -0400 [thread overview]
Message-ID: <162165838886.5676.10914513483315221530.b4-ty@oracle.com> (raw)
In-Reply-To: <20210515070315.215801-1-shinichiro.kawasaki@wdc.com>
On Sat, 15 May 2021 16:03:15 +0900, Shin'ichiro Kawasaki wrote:
> The BUG message "BUG: using smp_processor_id() in preemptible [00000000]
> code" was observed for TCMU devices with kernel config DEBUG_PREEMPT.
>
> The message was observed when blktests block/005 was run on TCMU devices
> with fileio backend or user:zbc backend [1]. The commit 1130b499b4a7
> ("scsi: target: tcm_loop: Use LIO wq cmd submission helper") triggered
> the symptom. The commit modified work queue to handle commands and
> changed 'current->nr_cpu_allowed' at smp_processor_id() call.
>
> [...]
Applied to 5.13/scsi-fixes, thanks!
[1/1] scsi: target: Avoid smp_processor_id() in preemptible code
https://git.kernel.org/mkp/scsi/c/70ca3c57ff91
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-05-22 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 7:03 [PATCH v2] scsi: target: Avoid smp_processor_id() in preemptible code Shin'ichiro Kawasaki
2021-05-15 16:17 ` michael.christie
2021-05-22 4:40 ` Martin K. Petersen [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=162165838886.5676.10914513483315221530.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Damien.LeMoal@wdc.com \
--cc=himanshu.madhani@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=target-devel@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 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.