mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Michael Bommarito <michael.bommarito@gmail.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Cc: xen-devel@lists.xenproject.org, linux-scsi@vger.kernel.org,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] xen/scsiback: free unsubmitted command instead of double-putting it
Date: Mon, 15 Jun 2026 17:14:00 +0200	[thread overview]
Message-ID: <dbc707b0-accd-49a0-96b8-7be2f19dac2f@suse.com> (raw)
In-Reply-To: <20260611123046.2323342-2-michael.bommarito@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1549 bytes --]

On 11.06.26 14:30, Michael Bommarito wrote:
> scsiback_get_pend_req() obtains a command tag and returns a
> vscsibk_pend whose embedded se_cmd has only been memset to 0, so
> its cmd_kref is 0; the se_cmd is initialised (kref_init() via
> target_init_cmd()) only later, in scsiback_cmd_exec(), on the
> successful VSCSIIF_ACT_SCSI_CDB path. The two error paths in
> scsiback_do_cmd_fn() taken before the command is submitted -- a
> failed scsiback_gnttab_data_map() and an unknown ring_req.act --
> call transport_generic_free_cmd(&pending_req->se_cmd, 0), which
> kref_put()s a refcount of 0. That underflows it ("refcount_t:
> underflow; use-after-free") and, as the release function is not
> run, leaks the command tag.
> 
> Impact: a pvSCSI guest can leak every command tag of a LUN's
> session, stopping the LUN, by submitting requests with a bad
> grant reference or an unknown request type; under panic_on_warn
> the refcount underflow panics the host.
> 
> Add a helper that just returns the tag with target_free_tag() and
> sends the error response. It frees the tag while the v2p reference
> still pins the session, and snapshots the response fields
> beforehand because freeing the tag can let another ring reuse the
> pending_req slot.
> 
> Fixes: 2dbcdf33dbf6 ("xen-scsiback: Convert to percpu_ida tag allocation")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2026-06-15 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 12:30 [PATCH 0/2] xen/scsiback: fix command-tag handling on pre-completion error paths Michael Bommarito
2026-06-11 12:30 ` [PATCH 1/2] xen/scsiback: free unsubmitted command instead of double-putting it Michael Bommarito
2026-06-15 15:14   ` Juergen Gross [this message]
2026-06-11 12:30 ` [PATCH 2/2] xen/scsiback: free the command tag on the TMR submit-failure path Michael Bommarito
2026-06-15 15:14   ` Juergen Gross
2026-06-16  2:00 ` [PATCH 0/2] xen/scsiback: fix command-tag handling on pre-completion error paths 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=dbc707b0-accd-49a0-96b8-7be2f19dac2f@suse.com \
    --to=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michael.bommarito@gmail.com \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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

Powered by JetHome