From: Ruslan Valiyev <linuxoid@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
John Ogness <john.ogness@linutronix.de>,
Lukas Wunner <lukas@wunner.de>, Gerhard Engleder <eg@keba.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
syzbot+9f57c1b2792029198fcf@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] serial: core: fix NULL pointer dereference in serial_core_unregister_port()
Date: Wed, 26 Aug 2026 10:06:26 +0200 [thread overview]
Message-ID: <178773158689.1384029.3121943722878545406@gmail.com> (raw)
In-Reply-To: <2026082645-stench-backpack-6e07@gregkh>
On Wed, Aug 26, 2026 at 09:53:34AM +0200, Greg Kroah-Hartman wrote:
> It's an invalid syzbot reproducer, if root tells the kernel to unbind
> from a device when it is being used, it gets to keep the pieces when
> things break :(
>
> Let me go polish off my "taint the kernel if bind/unbind runs" patch to
> keep this from happening...
Understood, thanks for looking at it so quickly. I'll drop the patch.
> Did you forget an Assisted-by: tag?
Yes. The patch was AI-assisted and should have included
Assisted-by: Claude:claude-opus-5
Assisted-by: Codex:gpt-5.6-sol
I worked from submitting-patches.rst for the tag order and did not read
coding-assistants.rst. My mistake, and it will be on anything I send in future.
Thanks,
Ruslan
next prev parent reply other threads:[~2026-08-26 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 7:32 Ruslan Valiyev
2026-08-26 7:53 ` Greg Kroah-Hartman
2026-08-26 8:06 ` Ruslan Valiyev [this message]
2026-08-26 8:20 ` Greg Kroah-Hartman
2026-08-26 8:13 ` Andy Shevchenko
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=178773158689.1384029.3121943722878545406@gmail.com \
--to=linuxoid@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=eg@keba.com \
--cc=gregkh@linuxfoundation.org \
--cc=hvilleneuve@dimonoff.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=stable@vger.kernel.org \
--cc=syzbot+9f57c1b2792029198fcf@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®