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: Re: What's up with "locks: change POSIX lock ownership on execve when files_struct is displaced"?
Date: Sat, 19 May 2018 21:13:56 -0400 [thread overview]
Message-ID: <20180520011356.GD23448@thunk.org> (raw)
In-Reply-To: <4cb7ba897fd4b5641be680cd599e74dd0c8e41bf.camel@kernel.org>
On Sat, May 19, 2018 at 07:51:15PM -0400, Jeff Layton wrote:
>
> No, it's not suitable for inclusion. After I sent the above patch, I
> realized that it would break some important filesystems (like NFS).
>
> Eric sounded like he had the best approach to fix it, but it's non-
> trivial and somewhat outside the bounds of the locking code. I haven't
> had time to attempt a patch for it so far.
Thanks, I'll suppress generic/484 for my ext4 testing for now.
- Ted
prev parent reply other threads:[~2018-05-20 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 19:47 What's up with "locks: change POSIX lock ownership on execve when files_struct is displaced"? Theodore Y. Ts'o
2018-05-19 23:51 ` Jeff Layton
2018-05-20 1:13 ` Theodore Y. Ts'o [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=20180520011356.GD23448@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.