summaryrefslogtreecommitdiff
path: root/drivers/parisc
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-08-29 21:59:37 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2023-08-29 21:59:37 +0300
commit468e28d4ac72869ed6c7cd7c7632008597949bd3 (patch)
tree313e91c62d910771feafdde4bcfbc09135f6742b /drivers/parisc
parentbd6c11bc43c496cddfc6cf603b5d45365606dbd5 (diff)
parentdc3216b1416056b04712e53431f6e9aefdc83177 (diff)
downloadlinux-468e28d4ac72869ed6c7cd7c7632008597949bd3.tar.xz
Merge tag 'v6.6-vfs.super.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
Pull superblock fixes from Christian Brauner: "Two follow-up fixes for the super work this cycle: - Move a misplaced lockep assertion before we potentially free the object containing the lock. - Ensure that filesystems which match superblocks in sget{_fc}() based on sb->s_fs_info are guaranteed to see a valid sb->s_fs_info as long as a superblock still appears on the filesystem type's superblock list. What we want as a proper solution for next cycle is to split sb->free_sb() out of sb->kill_sb() so that we can simply call kill_super_notify() after sb->kill_sb() but before sb->free_sb(). Currently, this is lumped together in sb->kill_sb()" * tag 'v6.6-vfs.super.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs: super: ensure valid info super: move lockdep assert
Diffstat (limited to 'drivers/parisc')
0 files changed, 0 insertions, 0 deletions