From: duoming@zju.edu.cn
To: "James Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
martin.petersen@oracle.com, stable@kernel.org
Subject: Re: [PATCH RESEND] scsi: ppa: Fix use-after-free caused by unfinished delayed work
Date: Sat, 3 Jan 2026 10:24:46 +0800 (GMT+08:00) [thread overview]
Message-ID: <3a85ddef.523b2.19b81abea97.Coremail.duoming@zju.edu.cn> (raw)
In-Reply-To: <91a16901ab4cd35fa00011a472c025f55068a4c7.camel@HansenPartnership.com>
On Thu, 01 Jan 2026 10:21:28 -0500, James Bottomley wrote:
> > diff --git a/drivers/scsi/ppa.c b/drivers/scsi/ppa.c
> > index ea682f3044b..8da2a78ebac 100644
> > --- a/drivers/scsi/ppa.c
> > +++ b/drivers/scsi/ppa.c
> > @@ -1136,6 +1136,7 @@ static void ppa_detach(struct parport *pb)
> > ppa_struct *dev;
> > list_for_each_entry(dev, &ppa_hosts, list) {
> > if (dev->dev->port == pb) {
> > + disable_delayed_work_sync(&dev->ppa_tq);
> > list_del_init(&dev->list);
> > scsi_remove_host(dev->host);
> > scsi_host_put(dev->host);
>
> This fix looks bogus: if there's an active workqueue on ppa it's
> because there's an outstanding command and it's emulating polling. If
> you stop the polling by disabling the workqueue, the command will never
> return and the host will never get freed, so this will leak resources,
> won't it?
I believe that disabling the ppa_tq delayed work will not affect the Scsi_Host
release process. The lifetime of the Scsi_Host is managed by tagset_refcnt.
The tagset_refcnt is initialized to 1 in scsi_add_host_with_dma() and decreased
to 0 in scsi_remove_host(). since the delayed work callback ppa_interrupt()
does not modify tagset_refcnt in any way, the host could be freed as expected.
> Also the race condition you identify is one of many tied to an
> incorrect ppa_struct lifetime: it should never be free'd before the
> host itself is gone because a live host may do a callback which will
> get the ppa_struct from hostdata, so if the host is still alive for any
> reason when ppa_detach() is called, we'll get the same problem.
The ppa_struct is properly freed only after ensuring the complete removal
of the associated Scsi_Host in ppa_detach(). The detailed sequence is as
follows:
...
scsi_remove_host(dev->host);
scsi_host_put(dev->host); //the host is gone
parport_unregister_device(dev->dev);
kfree(dev); //free ppa_struct
...
The scsi_remove_host() initiates the host removal process, transitioning
it through appropriate states(SHOST_CANCEL, SHOST_DEL) and ensuring all
pending I/O operations are properly handled. This sequence ensures that
all resources associated with the Scsi_Host are properly cleaned up before
the ppa_struct is freed.
Best regards,
Duoming Zhou
next prev parent reply other threads:[~2026-01-03 2:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 13:55 [PATCH RESEND] scsi: ppa: Fix use-after-free caused by unfinished delayed work Duoming Zhou
2026-01-01 15:21 ` James Bottomley
2026-01-03 2:24 ` duoming [this message]
2026-01-03 19:55 ` James Bottomley
2026-01-04 14:35 ` duoming
2026-01-04 23:30 ` James Bottomley
2026-01-06 5:35 ` duoming
2026-01-07 3:35 ` James Bottomley
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=3a85ddef.523b2.19b81abea97.Coremail.duoming@zju.edu.cn \
--to=duoming@zju.edu.cn \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@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