Re: [syzbot] [mm?] possible deadlock in __mmap_lock_do_trace_released

syzbot suspects this issue was fixed by commit: commit 7d6be67cfdd4a53cea7147313ca13c531e3a470f Author: Tetsuo Handa Date: Fri Jun 21 01:08:41 2024 + mm: mmap_lock: replace get_memcg_path_buf() with on-stack buffer bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12d488939

Re: [syzbot] [mm?] possible deadlock in __mmap_lock_do_trace_released

On Thu, 4 Jul 2024 22:12:45 +0200 Jesper Dangaard Brouer wrote: > > > > WARNING: possible recursive locking detected > > 6.10.0-rc2-syzkaller-00797-ga12978712d90 #0 Not tainted > > > > syz-executor646/5097 i

Re: [syzbot] [mm?] possible deadlock in __mmap_lock_do_trace_released

On 02/07/2024 20.54, syzbot wrote: Hello, syzbot found the following issue on: HEAD commit:a12978712d90 selftests/bpf: Move ARRAY_SIZE to bpf_misc.h git tree: bpf-next console+strace: https://syzkaller.appspot.com/x/log.txt?x=130457fa98 kernel config: https://syzkaller.appspot

[syzbot] [mm?] possible deadlock in __mmap_lock_do_trace_released

Hello, syzbot found the following issue on: HEAD commit:a12978712d90 selftests/bpf: Move ARRAY_SIZE to bpf_misc.h git tree: bpf-next console+strace: https://syzkaller.appspot.com/x/log.txt?x=130457fa98 kernel config: https://syzkaller.appspot.com/x/.config?x=736daf12bd72e034 dashbo