diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2022-08-23 19:17:26 -0700 | 
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-08-23 19:17:26 -0700 | 
| commit | 062d26ad0b36829c0142e5b96a694f3cdb6eaa43 (patch) | |
| tree | 34a9ca266fd12ebec79d9c0027e607a8782a5d83 /scripts/gdb/linux/utils.py | |
| parent | df0219d11b6f04251d38e345db4f9780cb32e2e2 (diff) | |
| parent | 41191cf6bf565f4139046d7be68ec30c290af92d (diff) | |
Merge tag 'fs.fixes.v6.0-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping
Pull file_remove_privs() fix from Christian Brauner:
 "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 commit 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"
* tag 'fs.fixes.v6.0-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping:
  fs: __file_remove_privs(): restore call to inode_has_no_xattr()
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions
