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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <YwEniFuQ7+dqXc5m@ZenIV>
Date:   Sat, 20 Aug 2022 19:27:20 +0100
From:   Al Viro <viro@...iv.linux.org.uk>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
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 Sat, Aug 20, 2022 at 11:01:26AM -0700, Linus Torvalds wrote:
> 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.

	Quite, especially since those programs would have to run before
getty gets a chance to reset the sucker to ^O...