From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: stable@vger.kernel.org, "Sasha Levin" <sashal@kernel.org>,
"Kees Cook" <kees@kernel.org>, "Hanno Böck" <hanno@hboeck.de>,
"Günther Noack" <gnoack3000@gmail.com>
Subject: Re: CONFIG_LEGACY_TIOCSTI support in stable branches
Date: Fri, 28 Jun 2024 16:16:26 +0200 [thread overview]
Message-ID: <2024062827-sympathy-suffrage-ddbf@gregkh> (raw)
In-Reply-To: <20240628114723.dnrkvdmiweteccrf@altlinux.org>
On Fri, Jun 28, 2024 at 02:47:23PM +0300, Vitaly Chikunov wrote:
> Sasha, Greg,
>
> Can you please backport CONFIG_LEGACY_TIOCSTI support into stable
> kernels?
That seems to be a new feature, not a bugfix, right? Is that applicable
to older kernels?
> This, perhaps, would include there mainline commits:
>
> 83efeeeb3d04b22aaed1df99bc70a48fe9d22c4d tty: Allow TIOCSTI to be disabled
> 5c30f3e4a6e67c88c979ad30554bf4ef9b24fbd0 tty: Move TIOCSTI toggle variable before kerndoc
> b2ea273a477cd6e83daedbfa1981cd1a7468f73a tty: Fix typo in LEGACY_TIOCSTI Kconfig description
> 690c8b804ad2eafbd35da5d3c95ad325ca7d5061 TIOCSTI: always enable for CAP_SYS_ADMIN
> 3f29d9ee323ae5cda59d144d1f8b0b10ea065be0 TIOCSTI: Document CAP_SYS_ADMIN behaviour in Kconfig
> 8d1b43f6a6df7bcea20982ad376a000d90906b42 tty: Restrict access to TIOCLINUX' copy-and-paste subcommands
Why not just use 6.6.y if you want this feature?
greg k-h
next prev parent reply other threads:[~2024-06-28 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 11:47 CONFIG_LEGACY_TIOCSTI support in stable branches Vitaly Chikunov
2024-06-28 14:16 ` Greg Kroah-Hartman [this message]
2024-06-28 14:33 ` Vitaly Chikunov
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=2024062827-sympathy-suffrage-ddbf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=gnoack3000@gmail.com \
--cc=hanno@hboeck.de \
--cc=kees@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vt@altlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.