linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Avi Kivity <avi@scylladb.com>
Cc: Jan Kara <jack@suse.cz>,
	axboe@kernel.dk, linux-fsdevel@vger.kernel.org,
	Jeff Moyer <jmoyer@redhat.com>,
	stable@vger.kernel.org, Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: [PATCH] direct-io: Fix negative return from dio read beyond eof
Date: Wed, 27 Jan 2016 09:59:52 -0800	[thread overview]
Message-ID: <20160127175952.GA1733@kroah.com> (raw)
In-Reply-To: <56A9031B.1020503@scylladb.com>

On Wed, Jan 27, 2016 at 07:49:15PM +0200, Avi Kivity wrote:
> On 01/27/2016 07:46 PM, Greg KH wrote:
> >On Wed, Jan 27, 2016 at 07:16:32PM +0200, Avi Kivity wrote:
> >>>   These are in the queue, in good company :)
> >>>
> >>>I'll go dig these out as I guess people care about them more than
> >>>others...
> >>>
> >>>
> >>Much appreciated.
> >Note, they didn't build on 3.14
> 
> I think the regression was introduced post 14, let me check.

Not according to the stable tag in the commit :)

> >  so I had to revert both of them.
> 
> Both of what?  There was only one patch.  Or did you mean you drop this
> patch for 4.3.5?

There was a follow-on fix for this patch as well, commit
2d4594acbf6d8f75a27f3578476b6a27d8b13ebb.

thanks,

greg k-h

      parent reply	other threads:[~2016-01-27 17:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 20:25 [PATCH] direct-io: Fix negative return from dio read beyond eof Jan Kara
2015-11-30 13:10 ` Jan Kara
2015-11-30 17:16   ` Jens Axboe
2016-01-27 10:38 ` Avi Kivity
2016-01-27 17:13   ` Greg KH
2016-01-27 17:16     ` Avi Kivity
2016-01-27 17:45       ` Greg KH
2016-01-27 17:46       ` Greg KH
2016-01-27 17:49         ` Avi Kivity
2016-01-27 17:52           ` Avi Kivity
2016-01-27 17:59           ` Greg KH [this message]

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=20160127175952.GA1733@kroah.com \
    --to=greg@kroah.com \
    --cc=avi@scylladb.com \
    --cc=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --cc=jmoyer@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=swhiteho@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).