linux-kernel - Re: [PATCH] vc_screen: don't clobber return value in vcs

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]

Date:   Fri, 3 Mar 2023 23:25:00 +0000
From:   Thomas Weißschuh <linux@...ssschuh.net>
To:     Storm Dragon <stormdragon2976@...il.com>
Cc:     George Kennedy <george.kennedy@...cle.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jirislaby@...nel.org>,
        linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH] vc_screen: don't clobber return value in vcs_read

On Fri, Mar 03, 2023 at 04:46:21PM -0500, Storm Dragon wrote:
> On Fri, Mar 03, 2023 at 09:12:50PM +0000, Thomas Weißschuh wrote:
> > Sorry for the long delay, but this should be fixed in the current round
> > of stable kernels. Can you try the following:
> > 
> > pacman -U https://mirrors.edge.kernel.org/archlinux/testing/os/x86_64/linux-6.2.2.arch1-1-x86_64.pkg.tar.zst
> > 
> > Thomas
> 
> I have installed the package above. My screen reader is behaving much
> better now. Interestingly, however, trying to cat the /dev/vcs device
> still shows the following:
>
> cat: /dev/vcs: No such device or address
> 
> cat: /dev/vcsa: No such device or address
> 
> cat: /dev/vcsa1: No such device or address
> 
> Is this expected behavior?

No it isn't. 

Is this reliably reproducible? I doesn't happen on my side.
Maybe you can provide more detailed reproduction steps.

Just to be sure; did you reboot into the new kernel?

Does this mean the screenreader now works correctly or is it still
broken somehow?

Thomas