From: syzbot <syzbot+9f9a7f73fb079b2387a6@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, david@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] kernel BUG in const_folio_flags (2)
Date: Thu, 28 Nov 2024 05:18:02 -0800 [thread overview]
Message-ID: <67486d8a.050a0220.253251.0085.GAE@google.com> (raw)
In-Reply-To: <57f0859b-4c30-4c72-9796-e8e6f836e509@redhat.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+9f9a7f73fb079b2387a6@syzkaller.appspotmail.com
Tested-by: syzbot+9f9a7f73fb079b2387a6@syzkaller.appspotmail.com
Tested on:
commit: fc0a5b9f mm/filemap: don't call folio_test_locked() wi..
git tree: https://github.com/davidhildenbrand/linux.git filemap_test_locked
console output: https://syzkaller.appspot.com/x/log.txt?x=132f200f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3a5fdacfe3dee51
dashboard link: https://syzkaller.appspot.com/bug?extid=9f9a7f73fb079b2387a6
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2024-11-28 13:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 7:31 [syzbot] [mm?] kernel BUG in const_folio_flags (2) syzbot
2024-11-25 6:56 ` Suraj Sonawane
2024-11-25 6:58 ` syzbot
2024-11-25 7:16 ` Suraj Sonawane
2024-11-25 7:18 ` syzbot
2024-11-25 7:37 ` Suraj Sonawane
2024-11-25 7:39 ` syzbot
2024-11-25 7:53 ` Suraj Sonawane
2024-11-25 7:55 ` syzbot
2024-11-25 7:57 ` Suraj Sonawane
2024-11-25 7:59 ` syzbot
2024-11-25 13:12 ` Suraj Sonawane
2024-11-25 13:43 ` syzbot
2024-11-28 10:52 ` David Hildenbrand
2024-11-28 11:42 ` Hillf Danton
2024-11-28 12:02 ` David Hildenbrand
2024-11-28 12:23 ` David Hildenbrand
2024-11-28 13:03 ` Hillf Danton
2024-11-28 13:37 ` syzbot
2024-11-28 12:57 ` David Hildenbrand
2024-11-28 13:18 ` 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=67486d8a.050a0220.253251.0085.GAE@google.com \
--to=syzbot+9f9a7f73fb079b2387a6@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.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