From: syzbot <syzbot+2f816ba9b71ca9a8e6b0@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andrii@kernel.org,
aneesh.kumar@linux.ibm.com, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com, kafai@fb.com,
kpsingh@kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, npiggin@gmail.com, peterz@infradead.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
toke@redhat.com, will@kernel.org, yhs@fb.com
Subject: Re: [syzbot] kernel BUG in __tlb_remove_page_size
Date: Fri, 06 Aug 2021 15:20:06 -0700 [thread overview]
Message-ID: <000000000000102b9305c8eb70da@google.com> (raw)
In-Reply-To: <000000000000b8a3e905c69535e3@google.com>
syzbot suspects this issue was fixed by commit:
commit af0efa050caa66e8f304c42c94c76cb6c480cb7e
Author: Toke Høiland-Jørgensen <toke@redhat.com>
Date: Tue Jul 6 12:23:55 2021 +0000
libbpf: Restore errno return for functions that were already returning it
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13b872fa300000
start commit: 3dbdb38e2869 Merge branch 'for-5.14' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a1fcf15a09815757
dashboard link: https://syzkaller.appspot.com/bug?extid=2f816ba9b71ca9a8e6b0
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=151ee572300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: libbpf: Restore errno return for functions that were already returning it
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-08-06 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 4:37 [syzbot] kernel BUG in __tlb_remove_page_size syzbot
2021-08-06 22:20 ` 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=000000000000102b9305c8eb70da@google.com \
--to=syzbot+2f816ba9b71ca9a8e6b0@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=toke@redhat.com \
--cc=will@kernel.org \
--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).