From: syzbot <syzbot+cf4cf13056f85dec2c40@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dhowells@redhat.com, hughd@google.com,
kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
vbabka@suse.cz, william.kucharski@oracle.com,
willy@infradead.org
Subject: Re: [syzbot] kernel BUG in __filemap_get_folio
Date: Fri, 22 Apr 2022 12:34:11 -0700 [thread overview]
Message-ID: <00000000000096c5ef05dd434f4c@google.com> (raw)
In-Reply-To: <YmL0L7nhdJTMI9QU@casper.infradead.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+cf4cf13056f85dec2c40@syzkaller.appspotmail.com
Tested on:
commit: 91070385 XArray: Disallow sibling entries of nodes
git tree: git://git.infradead.org/users/willy/xarray.git main
kernel config: https://syzkaller.appspot.com/x/.config?x=78d87160570beee3
dashboard link: https://syzkaller.appspot.com/bug?extid=cf4cf13056f85dec2c40
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2022-04-22 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 15:54 [syzbot] kernel BUG in __filemap_get_folio syzbot
2022-04-21 20:21 ` Matthew Wilcox
2022-04-22 18:30 ` Matthew Wilcox
2022-04-22 19:34 ` syzbot [this message]
[not found] <20220422001413.2515-1-hdanton@sina.com>
2022-04-22 0:25 ` syzbot
[not found] <20220422023004.2640-1-hdanton@sina.com>
2022-04-22 2:40 ` syzbot
[not found] <20220422070412.2714-1-hdanton@sina.com>
2022-04-22 9:12 ` syzbot
[not found] <20220422121712.2791-1-hdanton@sina.com>
2022-04-22 12:27 ` syzbot
[not found] <20220422125227.2853-1-hdanton@sina.com>
2022-04-22 13:10 ` syzbot
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=00000000000096c5ef05dd434f4c@google.com \
--to=syzbot+cf4cf13056f85dec2c40@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.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 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.