From: Brian Foster <bfoster@redhat.com>
To: Alex Lyakas <alex@zadara.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: Tue, 2 Apr 2019 09:54:07 -0400 [thread overview]
Message-ID: <20190402135407.GG2899@bfoster> (raw)
In-Reply-To: <CAOcd+r0fc+ctiAX+RrhMdByCmf1yU=E=57wU_a0hm2becTTzKg@mail.gmail.com>
On Tue, Apr 02, 2019 at 04:33:38PM +0300, Alex Lyakas wrote:
> Hi Brian,
>
> On Tue, Apr 2, 2019 at 2:44 PM Brian Foster <bfoster@redhat.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().
> > >
> >
> > For future reference, you probably want to make sure the patch series is
> > threaded when it's posted to the list.
> I am not sure what you mean by this. I used "git-send-email" to send
> all the patches one-by-one. Perhaps you mean that I should have sent
> them in one "git-send-email" command?
>
Yeah, most likely. At least I don't do anything more than format a patch
series to a directory, update the cover letter and whatnot and then 'git
send-email ...' on the entire directory to achieve threading.
> > That aside, this looks like a
> > reasonable and straightforward backport to me:
> >
> > Acked-by: Brian Foster <bfoster@redhat.com>
> I assume that I can treat your "Acked-by" as "Reviewed-by" (Dave asked
> for this to pass a review).
>
Sure, either way is fine. I wasn't sure what tags are expected for the
stable trees (if any) and just wanted to indicate that I think the
backport looks fine.
Brian
> Thanks!
> Alex.
>
>
> >
> > > 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
> > >
> > > fs/xfs/libxfs/xfs_attr.c | 20 +++++++++++++++-----
> > > fs/xfs/libxfs/xfs_attr_leaf.c | 9 ++++++---
> > > fs/xfs/libxfs/xfs_attr_leaf.h | 3 ++-
> > > fs/xfs/libxfs/xfs_defer.c | 39 ++++++++++++++++++++++++++++++++++++---
> > > fs/xfs/libxfs/xfs_defer.h | 5 ++++-
> > > 5 files changed, 63 insertions(+), 13 deletions(-)
> > >
> > > --
> > > 1.9.1
> > >
next prev parent reply other threads:[~2019-04-02 13:54 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 [this message]
2019-04-03 14:08 ` Greg KH
2019-04-06 13:11 ` Alex Lyakas
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=20190402135407.GG2899@bfoster \
--to=bfoster@redhat.com \
--cc=alex@zadara.com \
--cc=darrick.wong@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.