linux-kernel - Re: [PATCH] Return short read or 0 at end of a raw device, not EIO

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140929190509.GA2767@infradead.org>
Date:	Mon, 29 Sep 2014 12:05:09 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	David Jeffery <djeffery@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Return short read or 0 at end of a raw device, not EIO

On Mon, Sep 29, 2014 at 10:21:10AM -0400, David Jeffery wrote:
> Changes to the basic direct I/O code have broken the raw driver when reading
> to the end of a raw device.  Instead of returning a short read for a read that
> extends partially beyond the device's end or 0 when at the end of the device,
> these reads now return EIO.

Seems like this should be changed in the generic code, or is there some
reason why it would return EIO only for devices, but not for regular
files in this case?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/