From: syzbot <syzbot+d1e3b1d92d25abf97943@syzkaller.appspotmail.com>
To: andriin@fb.com, ast@kernel.org, bpf@vger.kernel.org,
casey@schaufler-ca.com, christian.brauner@ubuntu.com,
daniel@iogearbox.net, dhowells@redhat.com, dvyukov@google.com,
jmorris@namei.org, kafai@fb.com, kpsingh@google.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
paul@paul-moore.com, selinux@vger.kernel.org,
songliubraving@fb.com, stephen.smalley.work@gmail.com,
syzkaller-bugs@googlegroups.com, tonymarislogistics@yandex.com,
viro@zeniv.linux.org.uk, yhs@fb.com
Subject: Re: [syzbot] general protection fault in legacy_parse_param
Date: Fri, 27 Aug 2021 19:11:18 -0700 [thread overview]
Message-ID: <0000000000008d2a0005ca951d94@google.com> (raw)
In-Reply-To: <0000000000004e5ec705c6318557@google.com>
syzbot has bisected this issue to:
commit 54261af473be4c5481f6196064445d2945f2bdab
Author: KP Singh <kpsingh@google.com>
Date: Thu Apr 30 15:52:40 2020 +0000
security: Fix the default value of fs_context_parse_param hook
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=160c5d75300000
start commit: 77dd11439b86 Merge tag 'drm-fixes-2021-08-27' of git://ano..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=150c5d75300000
console output: https://syzkaller.appspot.com/x/log.txt?x=110c5d75300000
kernel config: https://syzkaller.appspot.com/x/.config?x=2fd902af77ff1e56
dashboard link: https://syzkaller.appspot.com/bug?extid=d1e3b1d92d25abf97943
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126d084d300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16216eb1300000
Reported-by: syzbot+d1e3b1d92d25abf97943@syzkaller.appspotmail.com
Fixes: 54261af473be ("security: Fix the default value of fs_context_parse_param hook")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-08-28 2:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 5:41 [syzbot] general protection fault in legacy_parse_param syzbot
2021-07-03 5:51 ` Dmitry Vyukov
2021-07-03 22:16 ` Casey Schaufler
2021-07-04 14:14 ` Paul Moore
2021-07-05 5:52 ` Dmitry Vyukov
2021-07-06 12:50 ` Paul Moore
2021-08-27 15:30 ` Christian Brauner
2021-08-27 15:40 ` Casey Schaufler
2021-08-27 16:26 ` Christian Brauner
2021-08-27 14:49 ` syzbot
2021-08-28 2:11 ` syzbot [this message]
2021-08-30 12:23 ` Christian Brauner
2021-08-30 14:25 ` Casey Schaufler
2021-08-30 16:40 ` Casey Schaufler
2021-08-30 16:57 ` Christian Brauner
2021-08-30 17:41 ` Casey Schaufler
2021-08-31 7:38 ` Christian Brauner
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=0000000000008d2a0005ca951d94@google.com \
--to=syzbot+d1e3b1d92d25abf97943@syzkaller.appspotmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=christian.brauner@ubuntu.com \
--cc=daniel@iogearbox.net \
--cc=dhowells@redhat.com \
--cc=dvyukov@google.com \
--cc=jmorris@namei.org \
--cc=kafai@fb.com \
--cc=kpsingh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=stephen.smalley.work@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tonymarislogistics@yandex.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yhs@fb.com \
/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;
as well as URLs for NNTP newsgroup(s).