summaryrefslogtreecommitdiffstats
path: root/fs/fscache
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-03-15 12:55:52 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2020-03-15 12:55:52 -0700
commit34d5a4b336e7e4c247d532a841d05367357197f8 (patch)
treec07c789d1a075d460c4effad4acddb1f4fdfee9f /fs/fscache
parentec181b7f30bdae2fbbba1c0dd76aeaad89c7963e (diff)
parent8d67743653dce5a0e7aa500fcccb237cde7ad88e (diff)
downloadlinux-34d5a4b336e7e4c247d532a841d05367357197f8.tar.gz
linux-34d5a4b336e7e4c247d532a841d05367357197f8.tar.bz2
linux-34d5a4b336e7e4c247d532a841d05367357197f8.zip
Merge tag 'locking-urgent-2020-03-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull futex fix from Thomas Gleixner: "Fix for yet another subtle futex issue. The futex code used ihold() to prevent inodes from vanishing, but ihold() does not guarantee inode persistence. Replace the inode pointer with a per boot, machine wide, unique inode identifier. The second commit fixes the breakage of the hash mechanism which causes a 100% performance regression" * tag 'locking-urgent-2020-03-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: futex: Unbreak futex hashing futex: Fix inode life-time issue
Diffstat (limited to 'fs/fscache')
0 files changed, 0 insertions, 0 deletions