From: syzbot <syzbot+18a1619cceea30ed45af@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bhe@redhat.com,
dmitry.kasatkin@gmail.com, jmorris@namei.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, mike.kravetz@oracle.com,
richard.weiyang@linux.alibaba.com, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
zohar@linux.ibm.com
Subject: Re: possible deadlock in process_measurement (2)
Date: Sat, 02 Jan 2021 15:08:07 -0800 [thread overview]
Message-ID: <0000000000000b157705b7f2eefd@google.com> (raw)
In-Reply-To: <000000000000880dcc0598bcfac9@google.com>
syzbot suspects this issue was fixed by commit:
commit 15a8d68e9dc23dc9def4bd7e9563db60f4f86580
Author: Wei Yang <richard.weiyang@linux.alibaba.com>
Date: Tue Oct 13 23:56:33 2020 +0000
mm/hugetlb: a page from buddy is not on any list
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13612350d00000
start commit: 1590a2e1 Merge tag 'acpi-5.8-rc3' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bf3aec367b9ab569
dashboard link: https://syzkaller.appspot.com/bug?extid=18a1619cceea30ed45af
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c79dbb100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169bba3d100000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm/hugetlb: a page from buddy is not on any list
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-01-02 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 18:45 possible deadlock in process_measurement (2) syzbot
2020-06-28 3:31 ` syzbot
2021-01-02 23:08 ` syzbot [this message]
2021-01-05 12:43 ` Dmitry Vyukov
-- strict thread matches above, loose matches on Subject: below --
2023-06-06 9:22 Miklos Szeredi
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=0000000000000b157705b7f2eefd@google.com \
--to=syzbot+18a1619cceea30ed45af@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=richard.weiyang@linux.alibaba.com \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=zohar@linux.ibm.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 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.