public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	GNU C Library <libc-alpha@sourceware.org>,
	Christoph Hellwig <hch@infradead.org>,
	Stephen Bates <sbates@raithlin.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@fb.com>,
	viro@zeniv.linux.org.uk
Subject: Re: RFC: pwritev2 regression test for invalid flags
Date: Thu, 15 Jun 2017 23:04:59 -0700	[thread overview]
Message-ID: <20170616060459.GA5472@infradead.org> (raw)
In-Reply-To: <43631a74-8934-6940-3eaa-e562e49c5cb2@intel.com>

On Thu, Jun 01, 2017 at 11:52:25AM -0600, Jon Derrick wrote:
> Can you apply the patch below to your kernel?

I've already sent this patch to Al twice (including a stable tag),
but it didn't seem to make it anywhere.

> diff --git a/fs/read_write.c b/fs/read_write.c
> index c4f88af..f77eb22 100644
> --- a/fs/read_write.c
> +++ b/fs/read_write.c
> @@ -1210,7 +1210,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)
---end quoted text---

  reply	other threads:[~2017-06-16  6:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 22:10 RFC: pwritev2 regression test for invalid flags Adhemerval Zanella
2017-06-01 17:52 ` Jon Derrick
2017-06-16  6:04   ` Christoph Hellwig [this message]
2017-06-16 13:01     ` Adhemerval Zanella

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=20170616060459.GA5472@infradead.org \
    --to=hch@infradead.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=jonathan.derrick@intel.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-block@vger.kernel.org \
    --cc=sbates@raithlin.com \
    --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