linux-kernel - Re: [PATCH 4/7] termios: consolidate values for VDISCARD in INIT_C

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wgLzPq42K8w8M6u__p8fu-FbN6VwvhE3Vvu9n_Pb0kwUQ@mail.gmail.com>
Date:   Sat, 20 Aug 2022 11:01:26 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 4/7] termios: consolidate values for VDISCARD in INIT_C_CC

On Fri, Aug 19, 2022 at 8:37 PM Al Viro <viro@...iv.linux.org.uk> wrote:
>
> However, util-linux still resets it to ^O on any architecture,
> ^O is the historical value, kernel ignores it anyway and finally,
> Linus said "Just change everybody to do the same, nobody cares
> about VDISCARD".

Heh. Grepping for DISCARD_CHAR() shows that there literally doesn't
seem to be any user.

I  guess some user space program could care what the initial value is,
but it seems very unlikely.

                Linus