From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Cc: stable@vger.kernel.org, bfoster@redhat.com,
darrick.wong@oracle.com, ben.hutchings@codethink.co.uk
Subject: Re: Please apply this XFS patch on 4.4
Date: Sat, 26 May 2018 15:23:47 +0200 [thread overview]
Message-ID: <20180526132347.GC16378@kroah.com> (raw)
In-Reply-To: <008901d3f3f2$1d6e00e0$584a02a0$@toshiba.co.jp>
On Fri, May 25, 2018 at 03:32:12PM +0900, Daniel Sangorrin wrote:
> Subject of the patch: xfs: remove racy hasattr check from attr ops
> Commit ID: 5a93790d4e2df73e30c965ec6e49be82fc3ccfce
> Why: It didn't pass LTP getxattr04 test, which is "a regression test for the race between getting an existing xattr and setting/removing a large xattr. This bug leads to that getxattr() fails to get an existing xattr and returns ENOATTR in xfs filesystem."
>
> LTP test getxattr04 was FAILing with this error message:
> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
> tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
> tst_test.c:982: INFO: Timeout per run is 0h 05m 00s
> getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute
>
> After patching 4.4.y and running the test again (on x86_64) it PASSes:
> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
> tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
> tst_test.c:982: INFO: Timeout per run is 0h 05m 00s
> getxattr04.c:82: PASS: getxattr() succeeded to get an existing attribute
>
> What kernel version: 4.4.y (Note: 4.9.y already has it applied)
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2018-05-26 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 6:32 Please apply this XFS patch on 4.4 Daniel Sangorrin
2018-05-26 13:23 ` 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=20180526132347.GC16378@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=bfoster@redhat.com \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=darrick.wong@oracle.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.