From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH] scsi: target: tcm_loop: fix wrong abort tag
Date: Mon, 17 Mar 2025 21:53:26 -0400 [thread overview]
Message-ID: <yq1o6xzcdg8.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250313014728.105849-1-kanie@linux.alibaba.com> (Guixin Liu's message of "Thu, 13 Mar 2025 09:47:27 +0800")
Guixin,
> When the tcm_loop_nr_hw_queues is set to a value greater than 1, the
> tags of requests in the block layer are no longer unique. This may
> lead to erroneous aborting of commands with the same tag. The issue
> can be resolved by using blk_mq_unique_tag to generate globally unique
> identifiers by combining the hardware queue index and per-queue tags.
Applied to 6.15/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2025-03-18 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 1:47 [PATCH] scsi: target: tcm_loop: fix wrong abort tag Guixin Liu
2025-03-14 3:06 ` Guixin Liu
2025-03-18 1:53 ` Martin K. Petersen [this message]
2025-03-21 0:36 ` 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=yq1o6xzcdg8.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=kanie@linux.alibaba.com \
--cc=linux-scsi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox