From: Storm Dragon <stormdragon2976@gmail.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: stable@vger.kernel.org, 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
Subject: Re: Request to backport "sysctl: fix proc_dobool() usability" to stable kernels
Date: Mon, 6 Mar 2023 12:47:32 -0500 [thread overview]
Message-ID: <ZAYnNEimr6WwoWEl@mjollnir> (raw)
In-Reply-To: <09ee7747-3038-4d6c-b063-f0349fa52b6e@t-8ch.de>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Sun, Mar 05, 2023 at 03:06:12AM +0000, Thomas Weißschuh wrote:
>Maybe it would also make sense to open a ticket to ArchLinux to enable
>CONFIG_LEGACY_TIOCSTI again, as per the kernel default.
>
>In accordance with the options help text:
>
>"Say 'Y here only if you have confirmed that yout system's userspace
>depends on this functionality to continue operating normally"
>
>Could you create such a ticket if think it's necessary?
The ticket has been created. The link is:
https://bugs.archlinux.org/task/77745
Thanks,
Storm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-03-06 17:48 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 ` Request to backport "sysctl: fix proc_dobool() usability" to stable kernels Thomas Weißschuh
2023-03-05 2:51 ` Storm Dragon
2023-03-05 3:06 ` Thomas Weißschuh
2023-03-06 17:47 ` Storm Dragon [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=ZAYnNEimr6WwoWEl@mjollnir \
--to=stormdragon2976@gmail.com \
--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=linux@weissschuh.net \
--cc=mcgrof@kernel.org \
--cc=omosnace@redhat.com \
--cc=stable@vger.kernel.org \
--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 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.