From: "Thomas Weißschuh" <linux@weissschuh.net>
To: stable@vger.kernel.org
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Ondrej Mosnacek <omosnace@redhat.com>,
Iurii Zaikin <yzaikin@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Storm Dragon <stormdragon2976@gmail.com>
Subject: Request to backport "sysctl: fix proc_dobool() usability" to stable kernels
Date: Sun, 5 Mar 2023 02:18:11 +0000 [thread overview]
Message-ID: <9563010d-a5cf-49e2-8c51-f2e66f064997@t-8ch.de> (raw)
In-Reply-To: <20230210145823.756906-1-omosnace@redhat.com>
Hi -stable team,
please backport the commit f1aa2eb5ea05 ("sysctl: fix proc_dobool() usability")
to the stable kernels containing commit 83efeeeb3d04 ("tty: Allow TIOCSTI to be disabled").
(Which seems only to be the 6.2 branch only at the moment)
Without this backport the sysctl dev.net.legacy_tiocsti to enable
ioctl(TIOCSTI) is not functional. So on kernels that don't enable
CONFIG_LEGACY_TIOCSTI, ioctl(TIOCSTI) is not usable at all.
This ioctl is used for the copy-and-paste functionality of the
screenreader "fenrir".
( https://github.com/chrys87/fenrir )
Reported-by: Storm Dragon <stormdragon2976@gmail.com>
Link: https://lore.kernel.org/lkml/ZAOi9hDBTYqoAZuI@hotmail.com/
next prev parent reply other threads:[~2023-03-05 2:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 14:58 [PATCH] sysctl: fix proc_dobool() usability Ondrej Mosnacek
2023-02-20 12:52 ` Ondrej Mosnacek
2023-02-21 17:34 ` Kees Cook
2023-02-21 21:36 ` Luis Chamberlain
2023-02-22 7:52 ` Ondrej Mosnacek
2023-03-05 2:18 ` Thomas Weißschuh [this message]
2023-03-05 2:51 ` Request to backport "sysctl: fix proc_dobool() usability" to stable kernels Storm Dragon
2023-03-05 3:06 ` Thomas Weißschuh
2023-03-06 17:47 ` Storm Dragon
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=9563010d-a5cf-49e2-8c51-f2e66f064997@t-8ch.de \
--to=linux@weissschuh.net \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=omosnace@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stormdragon2976@gmail.com \
--cc=yzaikin@google.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