From: syzbot <syzbot+534ee3d24c37c411f37f@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, brauner@kernel.org,
gregkh@linuxfoundation.org, kafai@fb.com,
linux-kernel@vger.kernel.org, lk@c--e.de, martin.lau@linux.dev,
peterx@redhat.com, shy828301@gmail.com,
syzkaller-bugs@googlegroups.com, tj@kernel.org,
yosryahmed@google.com, zokeefe@google.com
Subject: Re: [syzbot] general protection fault in kernfs_get_inode
Date: Wed, 16 Nov 2022 23:26:23 -0800 [thread overview]
Message-ID: <0000000000009ed19b05eda581e7@google.com> (raw)
In-Reply-To: <000000000000385cbf05ea3f1862@google.com>
syzbot suspects this issue was fixed by commit:
commit c6a7f445a2727a66fe68a7097f42698d8b31ea2c
Author: Yang Shi <shy828301@gmail.com>
Date: Wed Jul 6 23:59:20 2022 +0000
mm: khugepaged: don't carry huge page to the next loop for !CONFIG_NUMA
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=179cadcd880000
start commit: 55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=534ee3d24c37c411f37f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150adc52880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149d9584880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm: khugepaged: don't carry huge page to the next loop for !CONFIG_NUMA
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-11-17 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000385cbf05ea3f1862@google.com>
[not found] ` <00000000000028a44005ea40352b@google.com>
[not found] ` <Y0CbtVwW6+QIYJdQ@slm.duckdns.org>
[not found] ` <Y0HBlJ4AoZba93Uf@cae.in-ulm.de>
[not found] ` <20221009084039.cw6meqbvy4362lsa@wittgenstein>
[not found] ` <Y0LITEA/22Z7YVSa@cae.in-ulm.de>
2022-10-09 18:42 ` [PATCH] cgroup: Fix crash with CLONE_INTO_CGROUP and v1 cgroups Yosry Ahmed
2022-10-10 18:38 ` Martin KaFai Lau
2022-11-17 7:26 ` 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=0000000000009ed19b05eda581e7@google.com \
--to=syzbot+534ee3d24c37c411f37f@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@c--e.de \
--cc=martin.lau@linux.dev \
--cc=peterx@redhat.com \
--cc=shy828301@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=yosryahmed@google.com \
--cc=zokeefe@google.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