linux-kernel - Re: [regression] ENOTTY returned for tty fds

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-next>] [day] [month] [year] [list]

Message-ID: <c74f1e3e-a376-42e3-86e0-a804f9a7da2c@yandex.ru>
Date: Wed, 24 Jul 2024 11:07:32 +0300
From: stsp <stsp2@...dex.ru>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-serial@...r.kernel.org, Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [regression] ENOTTY returned for tty fds

24.07.2024 09:51, Greg KH пишет:
> What caused this change/regression?

I have absolutely no idea.
I've found it by debugging userspace,
and wrote a test-case to make sure the
problem is not in user-space.


>    And does any real-world programs
> rely on this?

dosemu


>    What exactly are you trying to determine with this ioctl
> test?

Whether it is a PTS (Pseudo-Tty-Slave), or
a real comport with MSR signalling.


>    Is there a different way to determine that?
I am not aware of any "canonical" way
of determining this. Maybe you tell me. :)
So far the only fix I know, is to stop checking
errno. But you return ENOTTY for a tty-associated
fd (isatty(fd)==1), so I believe this is a
bug in a kernel.