futex: Fix inode life-time issue
As reported by Jann, ihold() does not in fact guarantee inode persistence. And instead of making it so, replace the usage of inode pointers with a per boot, machine wide, unique inode identifier. This sequence number is global, but shared (file backed) futexes are rare enough that this should not become a performance issue. Reported-by:Jann Horn <jannh@google.com> Suggested-by:
Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by:
Peter Zijlstra (Intel) <peterz@infradead.org>
Loading
-
mentioned in commit dbbf2b2d
-
mentioned in commit 9466987e
-
mentioned in commit 49931f59
-
mentioned in commit e5373007
-
mentioned in commit ee77d84f
-
mentioned in commit 55548661
-
mentioned in commit f76423bd
-
mentioned in commit 3c59578d
-
mentioned in commit 2d5d554b
-
mentioned in commit 602d63b1
-
mentioned in commit 83286cfe
-
mentioned in commit b5f4b86e
-
mentioned in commit a8151edb
-
mentioned in commit 0635f81b
-
mentioned in commit d76ec2a0
-
mentioned in commit 60209173
-
mentioned in commit 3f983f9e
-
mentioned in commit 54966037
-
mentioned in commit dc5268cd
Please sign in to comment