From: Christoph Hellwig <hch@infradead.org>
To: David Jeffery <djeffery@redhat.com>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Return short read or 0 at end of a raw device, not EIO
Date: Fri, 31 Oct 2014 01:57:22 -0700 [thread overview]
Message-ID: <20141031085722.GA17398@infradead.org> (raw)
In-Reply-To: <20140929142110.GA12562@fury.redhat.com>
Could someone please pick up this regression fix?
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.
>
> The raw driver needs the same end of device handling as was added for normal
> block devices. Using blkdev_read_iter, which has the needed size checks,
> prevents the EIO conditions at the end of the device.
>
> Signed-off-by: David Jeffery <djeffery@redhat.com>
> ---
>
> drivers/char/raw.c | 2 +-
> fs/block_dev.c | 3 ++-
> include/linux/fs.h | 1 +
> 3 files changed, 4 insertions(+), 2 deletions(-)
>
>
> diff --git a/drivers/char/raw.c b/drivers/char/raw.c
> index 0102dc7..a24891b 100644
> --- a/drivers/char/raw.c
> +++ b/drivers/char/raw.c
> @@ -285,7 +285,7 @@ static long raw_ctl_compat_ioctl(struct file *file, unsigned int cmd,
>
> static const struct file_operations raw_fops = {
> .read = new_sync_read,
> - .read_iter = generic_file_read_iter,
> + .read_iter = blkdev_read_iter,
> .write = new_sync_write,
> .write_iter = blkdev_write_iter,
> .fsync = blkdev_fsync,
> diff --git a/fs/block_dev.c b/fs/block_dev.c
> index 6d72746..12aa041 100644
> --- a/fs/block_dev.c
> +++ b/fs/block_dev.c
> @@ -1591,7 +1591,7 @@ ssize_t blkdev_write_iter(struct kiocb *iocb, struct iov_iter *from)
> }
> EXPORT_SYMBOL_GPL(blkdev_write_iter);
>
> -static ssize_t blkdev_read_iter(struct kiocb *iocb, struct iov_iter *to)
> +ssize_t blkdev_read_iter(struct kiocb *iocb, struct iov_iter *to)
> {
> struct file *file = iocb->ki_filp;
> struct inode *bd_inode = file->f_mapping->host;
> @@ -1605,6 +1605,7 @@ static ssize_t blkdev_read_iter(struct kiocb *iocb, struct iov_iter *to)
> iov_iter_truncate(to, size);
> return generic_file_read_iter(iocb, to);
> }
> +EXPORT_SYMBOL_GPL(blkdev_read_iter);
>
> /*
> * Try to release a page associated with block device when the system
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 9418772..0c20168 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -2455,6 +2455,7 @@ extern ssize_t new_sync_read(struct file *filp, char __user *buf, size_t len, lo
> extern ssize_t new_sync_write(struct file *filp, const char __user *buf, size_t len, loff_t *ppos);
>
> /* fs/block_dev.c */
> +extern ssize_t blkdev_read_iter(struct kiocb *iocb, struct iov_iter *to);
> extern ssize_t blkdev_write_iter(struct kiocb *iocb, struct iov_iter *from);
> extern int blkdev_fsync(struct file *filp, loff_t start, loff_t end,
> int datasync);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
---end quoted text---
next prev parent reply other threads:[~2014-10-31 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 14:21 [PATCH] Return short read or 0 at end of a raw device, not EIO David Jeffery
2014-09-29 16:46 ` Jeff Moyer
2014-09-29 19:05 ` Christoph Hellwig
2014-09-29 22:08 ` David Jeffery
2014-09-30 15:28 ` Christoph Hellwig
2014-09-30 16:37 ` David Jeffery
2014-10-10 17:17 ` Jeff Moyer
2014-10-11 10:17 ` Christoph Hellwig
2014-10-31 8:57 ` Christoph Hellwig [this message]
2014-10-31 10:35 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141031085722.GA17398@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=djeffery@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox