From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: stable <stable@vger.kernel.org>
Subject: Re: [4.4-stable] xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE
Date: Wed, 23 Jan 2019 08:42:09 +0100 [thread overview]
Message-ID: <20190123074208.GA8489@kroah.com> (raw)
In-Reply-To: <1548171118.3229.294.camel@codethink.co.uk>
On Tue, Jan 22, 2019 at 03:31:58PM +0000, Ben Hutchings wrote:
> Please pick:
>
> commit 7b38460dc8e4eafba06c78f8e37099d3b34d473c
> Author: Darrick J. Wong <darrick.wong@oracle.com>
> Date: Tue Apr 17 19:10:15 2018 -0700
>
> xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE
>
> for 4.4. It's already present in other stable branches, and I've
> verified that when applied on 4.4-stable it fixes the reproducer on
> Bugzilla.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-01-23 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:31 [4.4-stable] xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE Ben Hutchings
2019-01-23 7:42 ` Greg Kroah-Hartman [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=20190123074208.GA8489@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben.hutchings@codethink.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).