From: Mehmet Fide <mehmet.fide@gmail.com>
To: Krystian Kaniewski <krystianmkaniewski@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com,
aichao@kylinos.cn, kees@kernel.org, linux-kernel@vger.kernel.org,
syzbot@lists.linux.dev, Neill Kapron <nkapron@google.com>,
mehmet.fide@screeningeagle.com
Subject: Re: [PATCH] usb: gadget: u_serial: pin ports while TTYs are installed
Date: Wed, 21 Oct 2026 08:17:34 +0200 [thread overview]
Message-ID: <20261021061734.3972101-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <6941beb7-8cae-4cc5-ba07-e1c8a8753fe1@mail.kernel.org>
Hi Krystian,
I sent a narrower fix for the same problem [1]. This patch also covers
the two holes Sashiko found in mine, so I will withdraw it.
Tested in QEMU with dummy_hcd on usb-next with KASAN and lockdep, and on
a Colibri VF50 on 7.2-rc1, with delays injected into gs_open() and
gs_close(). Without the patch, freeing the line during a close gives a
use-after-free, and a close after a failed open a NULL deref. With it
there are no reports, also over 40 add/remove cycles against
concurrent opens.
Tested-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
Two notes:
1. Since Johan's 8df07fe93573 ("tty: fix saved termios reset race"),
registration no longer frees the saved termios for u_serial, so that
reason in the commit message is out of date. Publishing the port
after registration is still right.
2. The NULL checks in gs_open() and gs_close() cannot trigger, since
gs_install() fails first. The gs_close() one is what Brian Ellis' v4
[2] adds, and this patch makes that one unnecessary.
[1] https://lore.kernel.org/linux-usb/20261019085855.3259716-1-mehmet.fide@gmail.com/
[2] https://lore.kernel.org/linux-usb/20261013-u_serial-gs-close-null-v4-1-9ea038501994@gotenna.com/
Thanks,
Mehmet
prev parent reply other threads:[~2026-10-21 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 15:54 syzbot
2026-10-21 6:17 ` Mehmet Fide [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=20261021061734.3972101-1-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=aichao@kylinos.cn \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=krystianmkaniewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mehmet.fide@screeningeagle.com \
--cc=nkapron@google.com \
--cc=syzbot@lists.linux.dev \
--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
all inboxes | Powered by JetHome®