All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: shinichiro.kawasaki@wdc.com, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org,
	Mike Christie <michael.christie@oracle.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: target: iblock: Fix smp_processor_id BUG messages
Date: Sat, 22 May 2021 00:40:33 -0400	[thread overview]
Message-ID: <162165838887.5676.11490489872740728440.b4-ty@oracle.com> (raw)
In-Reply-To: <20210519222640.5153-1-michael.christie@oracle.com>

On Wed, 19 May 2021 17:26:40 -0500, Mike Christie wrote:

> This has us use raw_smp_processor_id in iblock's plug_device callout.
> smp_processor_id is not needed here, because we are running from a per CPU
> work item that is also queued to run on a worker thread that is normally
> bound to a specific CPU. If the worker thread did end up switching CPUs
> then it's handled the same way we handle when the work got moved to a
> different CPU's worker thread, where we will just end up sending IO from
> the new CPU.

Applied to 5.13/scsi-fixes, thanks!

[1/1] scsi: target: iblock: Fix smp_processor_id BUG messages
      https://git.kernel.org/mkp/scsi/c/5aaeca258f55

-- 
Martin K. Petersen	Oracle Linux Engineering

      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-19 22:26 [PATCH] scsi: target: iblock: Fix smp_processor_id BUG messages Mike Christie
2021-05-20 13:12 ` Shinichiro Kawasaki
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=162165838887.5676.11490489872740728440.b4-ty@oracle.com \
    --to=martin.petersen@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.