diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2024-04-14 11:41:51 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2024-04-14 11:41:51 -0700 |
commit | 72374d71c31596c7442ac0db9a9327d0e062e941 (patch) | |
tree | 4f93f3d1a5c60159590a38b377ad521f4c06590b /fs/btrfs | |
parent | 27fd80851dc1e47b2facaa11b5b52c7dbc6b0718 (diff) | |
parent | 16b52bbee4823b01ab7fe3919373c981a38f3797 (diff) | |
download | linux-stable-72374d71c31596c7442ac0db9a9327d0e062e941.tar.gz linux-stable-72374d71c31596c7442ac0db9a9327d0e062e941.tar.bz2 linux-stable-72374d71c31596c7442ac0db9a9327d0e062e941.zip |
Merge tag 'pull-sysfs-annotation-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
Pull sysfs fix from Al Viro:
"Get rid of lockdep false positives around sysfs/overlayfs
syzbot has uncovered a class of lockdep false positives for setups
with sysfs being one of the backing layers in overlayfs. The root
cause is that of->mutex allocated when opening a sysfs file read-only
(which overlayfs might do) is confused with of->mutex of a file opened
writable (held in write to sysfs file, which overlayfs won't do).
Assigning them separate lockdep classes fixes that bunch and it's
obviously safe"
* tag 'pull-sysfs-annotation-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
kernfs: annotate different lockdep class for of->mutex of writable files
Diffstat (limited to 'fs/btrfs')
0 files changed, 0 insertions, 0 deletions