summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorMiklos Szeredi <mszeredi@redhat.com>2026-03-16 14:10:00 +0100
committerMiklos Szeredi <mszeredi@redhat.com>2026-03-24 15:26:32 +0100
commit204aa22a686bfee48daca7db620c1e017615f2ff (patch)
tree7755fcc4e6c5f9cc8fa5167dcc684440a340b32c /tools/perf/scripts/python/stackcollapse.py
parent5a6baf204610589f8a5b5a1cd69d1fe661d9d3cd (diff)
fuse: abort on fatal signal during sync init
When sync init is used and the server exits for some reason (error, crash) while processing FUSE_INIT, the filesystem creation will hang. The reason is that while all other threads will exit, the mounting thread (or process) will keep the device fd open, which will prevent an abort from happening. This is a regression from the async mount case, where the mount was done first, and the FUSE_INIT processing afterwards, in which case there's no such recursive syscall keeping the fd open. Fixes: dfb84c330794 ("fuse: allow synchronous FUSE_INIT") Cc: stable@vger.kernel.org # v6.18 Reviewed-by: Joanne Koong <joannelkoong@gmail.com> Reviewed-by: Bernd Schubert <bernd@bsbernd.com> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions