From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jeff Layton <jlayton@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, fstests@vger.kernel.org,
ebiederm@xmission.com
Subject: What's up with "locks: change POSIX lock ownership on execve when files_struct is displaced"?
Date: Sat, 19 May 2018 15:47:11 -0400 [thread overview]
Message-ID: <20180519194711.GA21362@thunk.org> (raw)
There is quite of noise currently with xfstests failures. In addition
to the fsync/EIO failures, there is also something going on with
dm-thin, etc. And then there's generic/484, which is failing for all
ext4 configs.
According to test script for generic/484, the test failure is fixed by
the patch:
locks: change POSIX lock ownership on execve when files_struct is displaced
>From what I can tell, the patch was last submitted on March 17th, with
comments from Eric Beiderman on April 2nd and 3rd --- but nothing
since then:
https://lists.gt.net/linux/kernel/2941364
Are you still hoping to land this patch for 4.17?
Thanks, regards,
- Ted
next reply other threads:[~2018-05-19 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 19:47 Theodore Y. Ts'o [this message]
2018-05-19 23:51 ` What's up with "locks: change POSIX lock ownership on execve when files_struct is displaced"? Jeff Layton
2018-05-20 1:13 ` Theodore Y. Ts'o
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=20180519194711.GA21362@thunk.org \
--to=tytso@mit.edu \
--cc=ebiederm@xmission.com \
--cc=fstests@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@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.