[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19c68f93-017d-cda1-632f-039ca3ca0158@kernel.dk>
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
Powered by blists - more mailing lists