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, 11 Jan 2019 14:32:35 -0500 (EST)
From:   Nicolas Pitre <nico@...xnic.net>
To:     Vito Caputo <vcaputo@...garu.com>
cc:     Dmitry Safonov <dima@...sta.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jslaby@...e.cz>,
        Mark Rutland <mark.rutland@....com>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        Tycho Andersen <tycho@...ho.ws>, Dave Mielke <dave@...lke.cc>,
        linux-kernel@...r.kernel.org
Subject: Re: commit 83d817f410 broke my ability to use Linux with a braille
 display

On Fri, 11 Jan 2019, Vito Caputo wrote:

> On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> > I use Linux with the help of a braille display and the brltty daemon. It 
> > turns out that the latest mainline kernel I can work with comes from 
> > commit 231f8fd0cc. Anything past that and I lose the ability to read the 
> > console barely a few seconds after the system has booted as brltty is 
> > thrown a wrench and the braille display becomes completely inoperable.
> > 
> > Things get somewhat better with commit c96cf923a9 as brltty is not 
> > longer incapacitated, but some programs would randomly crash. Even the 
> > very first login attempt won't work as I soon as I hit enter after my 
> > user name the password prompt is skipped over, just like if the enter 
> > key had been hit twice. Then lynx (the text web browser) would crash as 
> > soon as I switch the virtual console with LeftAlt+FN. Mind you, this 
> > isn't easy to perform bisection in those conditions.
> > 
> > And the worst commit i.e. 83d817f410 is marked for stable!  :-(
> 
> This all sounds familiar, and I suspect this is the fix:
> 
> https://lkml.org/lkml/2019/1/8/1379

Yep, I confirm this patch did solve all my issues.


Nicolas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ