linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jens Axboe <axboe@kernel.dk>
Subject: [GIT PULL] file_remove_privs() fix for v6.0-rc3
Date: Tue, 23 Aug 2022 13:10:56 +0200	[thread overview]
Message-ID: <20220823111056.858797-1-brauner@kernel.org> (raw)

Hey Linus,

/* Summary */
As part of Stefan's and Jens' work to add async buffered write support to xfs
we refactored file_remove_privs() and added __file_remove_privs() to avoid
calling __remove_privs() when IOCB_NOWAIT is passed.

While debugging a recent performance regression report I found that during
review we missed that faf99b563558 ("fs: add __remove_file_privs() with flags
parameter") accidently changed behavior when dentry_needs_remove_privs()
returns zero. Before the commit it would still call inode_has_no_xattr()
setting the S_NOSEC bit and thereby avoiding even calling into
dentry_needs_remove_privs() the next time this function is called. After that
commit inode_has_no_xattr() would only be called if __remove_privs() had to be
called. Restore the old behavior. This is likely the cause of the performance
regression.

/* Testing */
All patches are based on v6.0-rc1 and have been sitting in linux-next. No build
failures or warnings were observed and fstests, selftests, and LTP have seen no
regressions.

/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with current
mainline.

The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:

  Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping.git tags/fs.fixes.v6.0-rc3

for you to fetch changes up to 41191cf6bf565f4139046d7be68ec30c290af92d:

  fs: __file_remove_privs(): restore call to inode_has_no_xattr() (2022-08-18 09:39:33 +0200)

Please consider pulling these changes from the signed fs.fixes.v6.0-rc3 tag.

Thanks!
Christian

----------------------------------------------------------------
fs.fixes.v6.0-rc3

----------------------------------------------------------------
Stefan Roesch (1):
      fs: __file_remove_privs(): restore call to inode_has_no_xattr()

 fs/inode.c | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

             reply	other threads:[~2022-08-23 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 11:10 Christian Brauner [this message]
2022-08-24  2:45 ` [GIT PULL] file_remove_privs() fix for v6.0-rc3 pr-tracker-bot
     [not found] <20220824015126.GA86725@inn2.lkp.intel.com>
2022-08-24  2:00 ` [fs] 41191cf6bf: aim7.jobs-per-min 20.1% improvement kernel test robot
2022-08-24  7:14   ` [GIT PULL] file_remove_privs() fix for v6.0-rc3 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=20220823111056.858797-1-brauner@kernel.org \
    --to=brauner@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).