From: Dave Chinner <david@fromorbit.com>
To: gregkh@linuxfoundation.org
Cc: dchinner@redhat.com, bfoster@redhat.com, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "xfs: xfs_iozero can return positive errno" has been added to the 3.14-stable tree
Date: Wed, 3 Jun 2015 11:35:23 +1000 [thread overview]
Message-ID: <20150603013523.GE9143@dastard> (raw)
In-Reply-To: <1433293975206201@kroah.com>
On Wed, Jun 03, 2015 at 10:12:55AM +0900, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> xfs: xfs_iozero can return positive errno
>
> to the 3.14-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> xfs-xfs_iozero-can-return-positive-errno.patch
> and it can be found in the queue-3.14 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
No, it shouldn't be applied to 3.14, because:
> From cddc116228cb9d51d3224d23ba3e61fbbc3ec3d2 Mon Sep 17 00:00:00 2001
> From: Dave Chinner <dchinner@redhat.com>
> Date: Fri, 29 May 2015 07:40:32 +1000
> Subject: xfs: xfs_iozero can return positive errno
>
> From: Dave Chinner <dchinner@redhat.com>
>
> commit cddc116228cb9d51d3224d23ba3e61fbbc3ec3d2 upstream.
>
> It was missed when we converted everything in XFs to use negative error
> numbers, so fix it now. Bug introduced in 3.17 by commit 2451337 ("xfs: global
^^^^^^^^^^^^^^^^^^^^^^
The upstream commit also had an indication of what stable kernels it
needed to be applied to. i.e:
cc: <stable@vger.kernel.org> # 3.17, 3.18, 3.19, 4.0
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2015-06-03 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 1:12 Patch "xfs: xfs_iozero can return positive errno" has been added to the 3.14-stable tree gregkh
2015-06-03 1:35 ` Dave Chinner [this message]
2015-06-03 1:51 ` Greg KH
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=20150603013523.GE9143@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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