linux-kernel - Re: [PATCH] block, bfq: return nbytes and not zero from struct cftype .write() method

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:   Thu, 16 Aug 2018 13:11:49 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     "Maciej S. Szmigiero" <mail@...iej.szmigiero.name>,
        Paolo Valente <paolo.valente@...aro.org>
Cc:     linux-block@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Arianna Avanzini <avanzini.arianna@...il.com>
Subject: Re: [PATCH] block, bfq: return nbytes and not zero from struct cftype
 .write() method

On 8/15/18 3:56 PM, Maciej S. Szmigiero wrote:
> The value that struct cftype .write() method returns is then directly
> returned to userspace as the value returned by write() syscall, so it
> should be the number of bytes actually written (or consumed) and not zero.
> 
> Returning zero from write() syscall makes programs like /bin/echo or bash
> spin.

Applied, thanks.

Just a heads-up that gmail thinks your email is spam.

-- 
Jens Axboe