From: Hongyan Xu <getshell@seu.edu.cn>
To: gregkh@linuxfoundation.org, sashal@kernel.org, arnd@arndb.de
Cc: linusw@kernel.org, brgl@kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
jianhao.xu@seu.edu.cn, getshell@seu.edu.cn
Subject: [RFC PATCH 6.6.y 0/4] misc: ti-st: close transport removal races
Date: Fri, 24 Jul 2026 13:28:38 +0800 [thread overview]
Message-ID: <20260724052842.1052-1-getshell@seu.edu.cn> (raw)
The TI shared transport is published before probe completes and remains
published while remove tears its core down. The exported protocol entry
points can retain the raw core pointer across that teardown. An attached
N_TI_WL line discipline and its write-wakeup work provide another path to
the same freed core.
This series publishes only fully initialized transports, accounts users of
the published pointer, withdraws and drains that pointer on remove, and
synchronously closes an attached TTY before freeing the core.
This is an RFC for the 6.6 stable tree because the driver is still present
there but was removed from mainline by commit 78fe66360ed6 ("misc: ti-st:
st_kim: remove the driver"). There is consequently no current mainline
code location through which these fixes can first be merged.
The patches are based on linux-6.6.y commit da47cbc25466.
Hongyan Xu (4):
misc: ti-st: publish the transport only after probe succeeds
misc: ti-st: account published transport users
misc: ti-st: drain published users before transport removal
misc: ti-st: synchronize TTY teardown with transport removal
drivers/misc/ti-st/st_core.c | 59 +++++++++++++++++++++++---------
drivers/misc/ti-st/st_kim.c | 65 ++++++++++++++++++++++--------------
include/linux/ti_wilink_st.h | 8 +++++
3 files changed, 91 insertions(+), 41 deletions(-)
--
2.50.1.windows.1
next reply other threads:[~2026-07-24 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 5:28 Hongyan Xu [this message]
2026-07-24 5:28 ` [RFC PATCH 6.6.y 1/4] misc: ti-st: publish the transport only after probe succeeds Hongyan Xu
2026-07-24 5:28 ` [RFC PATCH 6.6.y 2/4] misc: ti-st: account published transport users Hongyan Xu
2026-07-24 5:28 ` [RFC PATCH 6.6.y 3/4] misc: ti-st: drain published users before transport removal Hongyan Xu
2026-07-24 5:28 ` [RFC PATCH 6.6.y 4/4] misc: ti-st: synchronize TTY teardown with " Hongyan Xu
2026-08-03 9:14 ` [RFC PATCH 6.6.y 0/4] misc: ti-st: close transport removal races Greg KH
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=20260724052842.1052-1-getshell@seu.edu.cn \
--to=getshell@seu.edu.cn \
--cc=arnd@arndb.de \
--cc=brgl@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jianhao.xu@seu.edu.cn \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®