From: syzbot <syzbot+6ff90931779bcdfc840c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axelrasmussen@google.com,
cgroups@vger.kernel.org, hannes@cmpxchg.org, hawk@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-trace-kernel@vger.kernel.org, lizefan.x@bytedance.com,
longman@redhat.com, mathieu.desnoyers@efficios.com,
mhiramat@kernel.org, netdev@vger.kernel.org,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: Re: [syzbot] [mm?] possible deadlock in __mmap_lock_do_trace_start_locking
Date: Tue, 27 Aug 2024 20:31:02 -0700 [thread overview]
Message-ID: <000000000000c69eb60620b5fc4b@google.com> (raw)
In-Reply-To: <00000000000041df050616f6ba4e@google.com>
syzbot suspects this issue was fixed by commit:
commit 7d6be67cfdd4a53cea7147313ca13c531e3a470f
Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Fri Jun 21 01:08:41 2024 +0000
mm: mmap_lock: replace get_memcg_path_buf() with on-stack buffer
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1412f697980000
start commit: 36534d3c5453 tcp: use signed arithmetic in tcp_rtx_probe0_..
git tree: bpf
kernel config: https://syzkaller.appspot.com/x/.config?x=333ebe38d43c42e2
dashboard link: https://syzkaller.appspot.com/bug?extid=6ff90931779bcdfc840c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1585acfa980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17bdb7ee980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm: mmap_lock: replace get_memcg_path_buf() with on-stack buffer
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-08-28 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 2:33 syzbot
2024-06-16 5:54 ` syzbot
2024-06-16 14:05 ` syzbot
2024-06-16 16:05 ` Waiman Long
2024-08-28 3:31 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000c69eb60620b5fc4b@google.com \
--to=syzbot+6ff90931779bcdfc840c@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hawk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox