diff options
| author | Jann Horn <jannh@google.com> | 2024-12-04 19:26:20 +0300 |
|---|---|---|
| committer | Vivek Kasireddy <vivek.kasireddy@intel.com> | 2024-12-12 03:47:40 +0300 |
| commit | 0a16e24e34f28210f68195259456c73462518597 (patch) | |
| tree | 1308ba7c58170240a0965928890c5da399fd1831 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 9cb189a882738c1d28b349d4e7c6a1ef9b3d8f87 (diff) | |
| download | linux-0a16e24e34f28210f68195259456c73462518597.tar.xz | |
udmabuf: also check for F_SEAL_FUTURE_WRITE
When F_SEAL_FUTURE_WRITE was introduced, it was overlooked that udmabuf
must reject memfds with this flag, just like ones with F_SEAL_WRITE.
Fix it by adding F_SEAL_FUTURE_WRITE to SEALS_DENIED.
Fixes: ab3948f58ff8 ("mm/memfd: add an F_SEAL_FUTURE_WRITE seal to memfd")
Cc: stable@vger.kernel.org
Acked-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
Signed-off-by: Jann Horn <jannh@google.com>
Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Signed-off-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20241204-udmabuf-fixes-v2-2-23887289de1c@google.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions