From: Alex Lyakas <alex@zadara.com>
To: Greg KH <greg@kroah.com>
Cc: linux-xfs@vger.kernel.org, stable@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
hch@lst.de, Shyam Kaushik <shyam@zadara.com>
Subject: Re: [STABLE PATCH 0/2] Fix in-memory metadata corruption at xfs_attr3_leaf_write_verify()
Date: Sat, 6 Apr 2019 16:11:53 +0300 [thread overview]
Message-ID: <CAOcd+r23YiLOZWoWVkuF3U4EJGiEOFM-1MgZiBgMJA4apavH8w@mail.gmail.com> (raw)
In-Reply-To: <20190403140822.GH8633@kroah.com>
Hi Greg,
The relevant commits in the Linus's tree are:
b7b2846fe26f2c0d7f317c874a13d3ecf22670ff
xfs: add the ability to join a held buffer to a defer_ops
6e643cd094de3bd0f97edcc1db0089afa24d909f
xfs: hold xfs_buf locked between shortform->leaf conversion and the
addition of an attribute
They were pulled by Linus in commit:
fca0e39b2bd2fcfea2027845df28757943d9f561
Merge tag 'xfs-4.15-fixes-8' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Thanks,
Alex.
On Wed, Apr 3, 2019 at 5:08 PM Greg KH <greg@kroah.com> wrote:
>
> On Sun, Mar 31, 2019 at 05:24:33PM +0300, Alex Lyakas wrote:
> > This is a partial backport of original Darrick's series "xfs: logging fixes" to kernel 4.14.
> > It fixes the in-memory metadata corruption error, which happens
> > when a partially initialized attribute buffer is attemped to be written to disk.
> > This issue is reproducible with kernel 4.14, when adding a 1-sec sleep in xfs_attr_set(),
> > between the call to xfs_attr_shortform_to_leaf() and the call to xfs_attr_leaf_addname().
> >
> > Darrick J. Wong (2):
> > xfs: add the ability to join a held buffer to a defer_ops
> > xfs: hold xfs_buf locked between shortform->leaf conversion and the
> > addition of an attribute
>
> What are the git commit ids of these patches in Linus's tree?
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2019-04-06 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 14:24 [STABLE PATCH 0/2] Fix in-memory metadata corruption at xfs_attr3_leaf_write_verify() Alex Lyakas
2019-04-02 11:44 ` Brian Foster
2019-04-02 13:33 ` Alex Lyakas
2019-04-02 13:54 ` Brian Foster
2019-04-03 14:08 ` Greg KH
2019-04-06 13:11 ` Alex Lyakas [this message]
2019-04-24 16:46 ` 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=CAOcd+r23YiLOZWoWVkuF3U4EJGiEOFM-1MgZiBgMJA4apavH8w@mail.gmail.com \
--to=alex@zadara.com \
--cc=darrick.wong@oracle.com \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=shyam@zadara.com \
--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).