mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: dlemoal@kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, Pei Xiao <xiaopei01@kylinos.cn>
Subject: Re: [PATCH v2 0/2] ata: pata_parport: fix UAF on protocol module unload
Date: Thu, 10 Sep 2026 19:19:46 +0200	[thread overview]
Message-ID: <aqLmskJMHq2iMetP@ryzen> (raw)
In-Reply-To: <178895116744.2768460.12721406127250514018.b4-ty@kernel.org>

On Wed, Sep 09, 2026 at 12:52:47PM +0200, Niklas Cassel wrote:
> On Tue, 08 Sep 2026 19:47:26 +0800, Pei Xiao wrote:
> > This series fixes use-after-free issues in pata_parport when a protocol
> > module goes away while pi_adapter devices created by it are still
> > attached.
> > 
> > Patch 1 pins the protocol module before the device becomes visible.
> > Previously try_module_get() ran after device_register(), so a forced
> > module unload in between left pi->proto dangling from the moment the
> > device appeared on the bus.
> > 
> > [...]
> 
> Applied to libata/linux.git (for-7.4), thanks!
> 
> [1/2] ata: pata_parport: pin the protocol module before device_register()
>       https://git.kernel.org/libata/linux/c/5d3355c7
> [2/2] ata: pata_parport: unregister devices on protocol unregister
>       https://git.kernel.org/libata/linux/c/d82c5cf6

This series was dropped because of kernel test robot reporting
build error.

(Interestingly, Sashiko did only reported an unrelated pre-existing issue,
but did not report the build error.)


Kind regards,
Niklas

      reply	other threads:[~2026-09-10 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 11:47 Pei Xiao
2026-09-08 11:47 ` [PATCH v2 1/2] ata: pata_parport: pin the protocol module before device_register() Pei Xiao
2026-09-08 11:47 ` [PATCH v2 2/2] ata: pata_parport: unregister devices on protocol unregister Pei Xiao
2026-09-09 10:52 ` [PATCH v2 0/2] ata: pata_parport: fix UAF on protocol module unload Niklas Cassel
2026-09-10 17:19   ` Niklas Cassel [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=aqLmskJMHq2iMetP@ryzen \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiaopei01@kylinos.cn \
    /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

all inboxes | Powered by JetHome®