From: Jon Derrick <jonathan.derrick@intel.com>
To: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] fs: pass on flags in compat_writev
Date: Thu, 1 Jun 2017 12:24:33 -0600 [thread overview]
Message-ID: <a48e3108-6fbb-1af4-92fd-1cd492a9ca4d@intel.com> (raw)
In-Reply-To: <20170616090824.5460-1-hch@lst.de>
Thanks for driving this
Acked-by Jon Derrick: <jonathan.derrick@intel.com>
On 06/16/2017 03:08 AM, Christoph Hellwig wrote:
> Fixes: 793b80ef ("vfs: pass a flags argument to vfs_readv/vfs_writev")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Cc: stable@vger.kernel.org
> ---
>
> I've been trying to get this in through Al multiple times, and now I've
> got a report that the glibc test suite hits this issue. Let's get it
> into 4.12-rc
>
> fs/read_write.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/read_write.c b/fs/read_write.c
> index 47c1d4484df9..19d4d88fa285 100644
> --- a/fs/read_write.c
> +++ b/fs/read_write.c
> @@ -1285,7 +1285,7 @@ static size_t compat_writev(struct file *file,
> if (!(file->f_mode & FMODE_CAN_WRITE))
> goto out;
>
> - ret = compat_do_readv_writev(WRITE, file, vec, vlen, pos, 0);
> + ret = compat_do_readv_writev(WRITE, file, vec, vlen, pos, flags);
>
> out:
> if (ret > 0)
>
next prev parent reply other threads:[~2017-06-01 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 9:08 [PATCH] fs: pass on flags in compat_writev Christoph Hellwig
2017-06-01 18:24 ` Jon Derrick [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-10 6:37 Christoph Hellwig
2017-05-27 8:14 ` Christoph Hellwig
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=a48e3108-6fbb-1af4-92fd-1cd492a9ca4d@intel.com \
--to=jonathan.derrick@intel.com \
--cc=adhemerval.zanella@linaro.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@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