From: Bob Peterson <rpeterso@redhat.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org
Subject: [vfs PATCH 0/2] Fix gfs2 setattr bug
Date: Wed, 28 Jul 2021 07:47:32 -0500 [thread overview]
Message-ID: <20210728124734.227375-1-rpeterso@redhat.com> (raw)
Hi Al,
Here is a set of two patches from Andreas Gruenbacher to fix a problem
that causes xfstests generic/079 to fail on gfs2. The first patch moves a
chunk of code from notify_change to its own function, may_setattr, so gfs2
can use it. The second patch makes gfs2 use it.
Bob Peterson
Andreas Gruenbacher (2):
fs: Move notify_change permission checks into may_setattr
gfs2: Switch to may_setattr in gfs2_setattr
fs/attr.c | 50 ++++++++++++++++++++++++++++------------------
fs/gfs2/inode.c | 4 ++--
include/linux/fs.h | 2 ++
3 files changed, 35 insertions(+), 21 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-28 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 12:47 Bob Peterson [this message]
2021-07-28 12:47 ` [vfs PATCH 1/2] fs: Move notify_change permission checks into may_setattr Bob Peterson
2021-07-28 12:47 ` [vfs PATCH 2/2] gfs2: Switch to may_setattr in gfs2_setattr Bob Peterson
2021-07-28 13:14 ` [vfs PATCH 0/2] Fix gfs2 setattr bug Christian Brauner
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=20210728124734.227375-1-rpeterso@redhat.com \
--to=rpeterso@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.