From: syzbot <syzbot+8bb6fd945af4e0ad9299@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, apopple@nvidia.com, david@redhat.com,
donettom@linux.ibm.com, jane.chu@oracle.com,
jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
shaggy@kernel.org, shivankg@amd.com,
syzkaller-bugs@googlegroups.com, wangkefeng.wang@huawei.com,
willy@infradead.org, ziy@nvidia.com
Subject: Re: [syzbot] [mm?] WARNING in move_to_new_folio
Date: Wed, 30 Apr 2025 03:38:06 -0700 [thread overview]
Message-ID: <6811fd8e.050a0220.16fb2c.000c.GAE@google.com> (raw)
In-Reply-To: <20250430100150.279751-1-shivankg@amd.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+8bb6fd945af4e0ad9299@syzkaller.appspotmail.com
Tested-by: syzbot+8bb6fd945af4e0ad9299@syzkaller.appspotmail.com
Tested on:
commit: 69a58d52 Revert "x86/mm: Add 'mm' argument to unuse_te..
git tree: https://github.com/shivankgarg98/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=137a68d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f002bbe3fe2ccafa
dashboard link: https://syzkaller.appspot.com/bug?extid=8bb6fd945af4e0ad9299
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-04-30 10:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 10:01 [PATCH V5 0/2] JFS: Implement migrate_folio for jfs_metapage_aops Shivank Garg
2025-04-30 10:01 ` [PATCH V5 1/2] mm: Add folio_expected_ref_count() for reference count calculation Shivank Garg
2025-04-30 10:01 ` [PATCH V5 2/2] jfs: implement migrate_folio for jfs_metapage_aops Shivank Garg
2025-04-30 10:38 ` syzbot [this message]
2025-04-30 21:21 ` [PATCH V5 0/2] JFS: Implement " Andrew Morton
2025-05-01 12:37 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 5:12 Syz Test if issue still reproduce Shivank Garg
2025-04-30 7:30 ` [syzbot] [mm?] WARNING in move_to_new_folio syzbot
2025-04-30 7:58 ` Shivank Garg
2025-04-30 8:23 ` syzbot
2025-04-30 9:06 ` Shivank Garg
2025-04-30 9:43 ` syzbot
2025-04-22 11:40 [PATCH V4 0/2] JFS: Implement migrate_folio for jfs_metapage_aops Shivank Garg
2025-04-22 13:59 ` [syzbot] [mm?] WARNING in move_to_new_folio syzbot
2025-04-17 6:06 [PATCH V3 0/2] JFS: Implement migrate_folio for jfs_metapage_aops Shivank Garg
2025-04-17 8:47 ` [syzbot] [mm?] WARNING in move_to_new_folio syzbot
2025-04-17 9:06 ` Shivank Garg
[not found] <60d9e567-cc9a-43fb-a47e-e8aba30cc98e@amd.com>
2025-04-15 4:58 ` syzbot
2025-04-13 0:03 syzbot
2025-04-13 6:24 ` syzbot
2025-04-13 21:44 ` syzbot
2025-04-15 4:57 ` Shivank Garg
2025-04-15 5:24 ` syzbot
2025-04-15 5:40 ` Shivank Garg
2025-04-15 6:00 ` syzbot
2025-04-15 6:18 ` Shivank Garg
2025-04-15 7:00 ` 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=6811fd8e.050a0220.16fb2c.000c.GAE@google.com \
--to=syzbot+8bb6fd945af4e0ad9299@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=donettom@linux.ibm.com \
--cc=jane.chu@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shaggy@kernel.org \
--cc=shivankg@amd.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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.