linux-kernel - Re: [PATCH] mos7840: fix chars_in

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

Date:   Sat, 24 Sep 2016 18:00:24 +0300
From:   Stas Sergeev <stsp@...t.ru>
To:     Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc:     Caylan Van Larson <i@...lan.net>,
        Alan Cox <alan@...rguk.ukuu.org.uk>,
        Johan Hovold <johan@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mos7840: fix chars_in_buffer() return value

24.09.2016 16:57, Sergei Shtylyov пишет:
> Hello.
>
> On 9/24/2016 4:47 PM, Stas Sergeev wrote:
>
>> The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on
>> a correct behaviour of that.
>> mos7840 implements it wrongly: if you write just one char, TIOCOUTQ
>> will return 32.
>> This patch should fix it by accounting the number of chars actually
>> writCaylan Van Larson <i@...lan.net>ten.
>
>    ???
>
>> This patch, unfortunately, misses the Tesed-by tag.
>
>    Tested-by.
>
>> The reported didn't test it, and I don't have the hardware in question.
>
>    Reporter? 
:)
Thanks, will re-send with corrections.