diff options
| author | Jann Horn <jannh@google.com> | 2024-07-23 17:03:56 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2024-07-24 10:53:14 +0200 |
| commit | f8138f2ad2f745b9a1c696a05b749eabe44337ea (patch) | |
| tree | 00acf4b34e5ae5bbdb0edb0134740a53e2ee736f /lib/test_fortify/write_overflow-memset.c | |
| parent | 8eac5358ad3bbc007156a0f9ea5637ee7ae421b5 (diff) | |
filelock: Fix fcntl/close race recovery compat path
When I wrote commit 3cad1bc01041 ("filelock: Remove locks reliably when
fcntl/close race is detected"), I missed that there are two copies of the
code I was patching: The normal version, and the version for 64-bit offsets
on 32-bit kernels.
Thanks to Greg KH for stumbling over this while doing the stable
backport...
Apply exactly the same fix to the compat path for 32-bit kernels.
Fixes: c293621bbf67 ("[PATCH] stale POSIX lock handling")
Cc: stable@kernel.org
Link: https://bugs.chromium.org/p/project-zero/issues/detail?id=2563
Signed-off-by: Jann Horn <jannh@google.com>
Link: https://lore.kernel.org/r/20240723-fs-lock-recover-compatfix-v1-1-148096719529@google.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'lib/test_fortify/write_overflow-memset.c')
0 files changed, 0 insertions, 0 deletions