diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2026-10-12 23:07:33 -0700 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-10-14 10:08:06 +0200 |
| commit | eb20a959760c21e3547cd811d0d9b0b29df98959 (patch) | |
| tree | 71d17d45ad4dc9977e39cb2735bafe5c8655ad51 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 3978b1f3109dfd5c648442bb040f9abd58608226 (diff) | |
| download | linux-eb20a959760c21e3547cd811d0d9b0b29df98959.tar.gz linux-eb20a959760c21e3547cd811d0d9b0b29df98959.zip | |
xfs: clear set[ug]id mode bits when zapping attr fork
LOLLM observes that zapping a file's attr fork could result in ACLs
being removed from the file. Because we have no idea what we're
deleting, we should clear the setuid and setgid bits in addition to the
access mode bits so that nobody can access the file.
Cc: stable@vger.kernel.org # v6.8
Fixes: e744cef2060559 ("xfs: zap broken inode forks")
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Assisted-by: LOLLM # finding obvious bugs
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions