From: syzbot <syzbot+0772686ab2731ef3b722@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, mhiramat@kernel.org,
netdev@vger.kernel.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, takayas@chromium.org,
tj@kernel.org
Subject: Re: [syzbot] [kernfs?] possible deadlock in kernfs_path_from_node
Date: Sun, 13 Oct 2024 05:09:02 -0700 [thread overview]
Message-ID: <670bb85e.050a0220.3e960.003d.GAE@google.com> (raw)
In-Reply-To: <0000000000004b09b90621e1e9e9@google.com>
syzbot suspects this issue was fixed by commit:
commit b6273b55d88539c6a7127a697c61d3f89c5831fe
Author: Takaya Saeki <takayas@chromium.org>
Date: Tue Aug 13 10:03:12 2024 +0000
filemap: add trace events for get_pages, map_pages, and fault
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10f59087980000
start commit: 8a3f14bb1e94 libbpf: Workaround (another) -Wmaybe-uninitia..
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=eb19570bf3f0c14f
dashboard link: https://syzkaller.appspot.com/bug?extid=0772686ab2731ef3b722
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10aa1ffb980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b1abc7980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: filemap: add trace events for get_pages, map_pages, and fault
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-10-13 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 1:20 [syzbot] [kernfs?] possible deadlock in kernfs_path_from_node syzbot
2024-10-13 12:09 ` 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=670bb85e.050a0220.3e960.003d.GAE@google.com \
--to=syzbot+0772686ab2731ef3b722@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takayas@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.