From: syzbot <syzbot+f8a023e0c6beabe2371a@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org
Subject: Re: [syzbot] [fs?] [trace?] BUG: unable to handle kernel paging request in tracefs_apply_options
Date: Mon, 12 Feb 2024 09:10:02 -0800 [thread overview]
Message-ID: <0000000000002f3fba0611325902@google.com> (raw)
In-Reply-To: <0000000000006bf22a060e117a8d@google.com>
syzbot suspects this issue was fixed by commit:
commit ad579864637af46447208254719943179b69d41a
Author: Steven Rostedt (Google) <rostedt@goodmis.org>
Date: Tue Jan 2 20:12:49 2024 +0000
tracefs: Check for dentry->d_inode exists in set_gid()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17659d24180000
start commit: 453f5db0619e Merge tag 'trace-v6.7-rc7' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f8e72bae38c079e4
dashboard link: https://syzkaller.appspot.com/bug?extid=f8a023e0c6beabe2371a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1414af31e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e52409e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: tracefs: Check for dentry->d_inode exists in set_gid()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-02-12 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 21:41 [syzbot] [fs?] [trace?] BUG: unable to handle kernel paging request in tracefs_apply_options syzbot
2024-01-03 21:59 ` Steven Rostedt
2024-01-04 13:44 ` Edward Adam Davis
2024-01-04 14:07 ` syzbot
2024-02-12 17:10 ` 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=0000000000002f3fba0611325902@google.com \
--to=syzbot+f8a023e0c6beabe2371a@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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