summaryrefslogtreecommitdiff
path: root/%3fh%3dv2.6.23-rc2&id%3d8d67743653dce5a0e7aa500fcccb237cde7ad88e?h=v2.6.23-rc...
diff options
context:
space:
mode:
authorPeter Zijlstra <peterz@infradead.org>2020-03-04 11:28:31 +0100
committerPeter Zijlstra <peterz@infradead.org>2020-03-06 11:06:15 +0100
commit8019ad13ef7f64be44d4f892af9c840179009254 (patch)
tree889b754b07fa844410d6782bc1b4473007a9bc99 /%3fh%3dv2.6.23-rc2&id%3d8d67743653dce5a0e7aa500fcccb237cde7ad88e?h=v2.6.23-rc2&id=8019ad13ef7f64be44d4f892af9c840179009254
parent98d54f81e36ba3bf92172791eba5ca5bd813989b (diff)
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>
Diffstat (limited to '%3fh%3dv2.6.23-rc2&id%3d8d67743653dce5a0e7aa500fcccb237cde7ad88e?h=v2.6.23-rc2&id=8019ad13ef7f64be44d4f892af9c840179009254')
0 files changed, 0 insertions, 0 deletions