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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <5429D84B.7080902@redhat.com>
Date:	Mon, 29 Sep 2014 18:08:11 -0400
From:	David Jeffery <djeffery@...hat.com>
To:	Christoph Hellwig <hch@...radead.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Return short read or 0 at end of a raw device, not EIO

On 09/29/2014 03:05 PM, Christoph Hellwig wrote:
> 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?
> 

Regular files shouldn't be returning EIO and don't in my tests. The file
systems manage direct I/O EOF handling in their own block or direct_IO
callbacks.  Block devices do not and instead do the size checks up
front.  Raw devices were bypassing the block device check, so only the
raw driver should be having this issue.

David Jeffery
--
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/