From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: David Disseldorp <ddiss@suse.de>, target-devel@vger.kernel.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
michael.christie@oracle.com
Subject: Re: [PATCH 0/3] scsi: target: se_cmd cleanups and race fix
Date: Tue, 10 Aug 2021 01:20:43 -0400 [thread overview]
Message-ID: <162857263914.15955.13769529744088744487.b4-ty@oracle.com> (raw)
In-Reply-To: <20210728115353.2396-1-ddiss@suse.de>
On Wed, 28 Jul 2021 13:53:51 +0200, David Disseldorp wrote:
> While looking into XCOPY sense propagation issues (see Sergey's
> patchset), I came across some se_cmd members which are unneeded. This
> series also carries a fix for a theoretical lun_tg_pt_gp race condition.
>
> Cheers, David
>
>
> [...]
Applied to 5.15/scsi-queue, thanks!
[1/3] scsi: target: avoid using lun_tg_pt_gp after unlock
https://git.kernel.org/mkp/scsi/c/7e457e5efc28
[2/3] scsi: target: sbp: drop incorrect asc/ascq usage
https://git.kernel.org/mkp/scsi/c/35410f862426
[3/3] scsi: target: drop unnecessary se_cmd asc/ascq members
https://git.kernel.org/mkp/scsi/c/40fd8845c025
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-08-10 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 11:53 [PATCH 0/3] scsi: target: se_cmd cleanups and race fix David Disseldorp
2021-07-28 11:53 ` [PATCH 1/3] scsi: target: avoid using lun_tg_pt_gp after unlock David Disseldorp
2021-07-28 11:53 ` [PATCH 2/3] scsi: target: sbp: drop incorrect asc/ascq usage David Disseldorp
2021-07-28 11:53 ` [PATCH 3/3] scsi: target: drop unnecessary se_cmd asc/ascq members David Disseldorp
2021-08-01 18:55 ` [PATCH 0/3] scsi: target: se_cmd cleanups and race fix Mike Christie
2021-08-03 2:57 ` Martin K. Petersen
2021-08-10 5:20 ` 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=162857263914.15955.13769529744088744487.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=ddiss@suse.de \
--cc=michael.christie@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox