The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: syzbot <syzbot+690d666eb12fca6e1e61@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	Danilo Krummrich <dakr@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	driver-core@lists.linux.dev, Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, Ian Abbott <abbotti@mev.co.uk>
Subject: Re: [syzbot] [kernel?] WARNING: proc registration bug in unregister_irq_proc (2)
Date: Tue, 28 Jul 2026 21:09:53 +0200	[thread overview]
Message-ID: <87qzkngcce.ffs@fw13> (raw)
In-Reply-To: <2026072703-sandbox-oven-5235@gregkh>

On Mon, Jul 27 2026 at 16:33, Greg Kroah-Hartman wrote:
> On Mon, Jul 27, 2026 at 04:22:58PM +0200, Thomas Gleixner wrote:
>> I rather go and harden the interrupt core against such bogosities.
>
> Sure, but really, anyone doing a manual "unbind" gets to keep the pieces
> if the kernel can't handle it. The comedi driver really aren't all that
> ready for stuff like this as they are in systems that are fixed to the
> shop floor, driving big stone cutters.
>
> So no real rush/need that I can see here.

I understand, but it bothers me that the leakage is detected way too
late and only unearthed by removing a proc entry. There might be actual
references dangling. The interrupt core code knows all that at the point
where the teardown starts and that's where it can cleanup the mess and
emit a warning message.

Thanks,

        tglx

  reply	other threads:[~2026-07-28 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25 22:42 [syzbot] [kernel?] WARNING: proc registration bug in unregister_irq_proc (2) syzbot
2026-07-27 14:22 ` Thomas Gleixner
2026-07-27 14:33   ` Greg Kroah-Hartman
2026-07-28 19:09     ` Thomas Gleixner [this message]
2026-07-27 15:03   ` Ian Abbott

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=87qzkngcce.ffs@fw13 \
    --to=tglx@kernel.org \
    --cc=abbotti@mev.co.uk \
    --cc=bhelgaas@google.com \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=syzbot+690d666eb12fca6e1e61@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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