From: syzbot <syzbot+bf2c35fa302ebe3c7471@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de,
dave.hansen@linux.intel.com, david@redhat.com, hpa@zytor.com,
jgg@ziepe.ca, leitao@debian.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mingo@redhat.com, peterx@redhat.com,
rppt@kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [syzbot] [mm?] WARNING in copy_huge_pmd
Date: Thu, 26 Sep 2024 21:20:02 -0700 [thread overview]
Message-ID: <66f63272.050a0220.38ace9.0009.GAE@google.com> (raw)
In-Reply-To: <ad1e7e02-26f2-43db-b18f-ab995cd4f982@redhat.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+bf2c35fa302ebe3c7471@syzkaller.appspotmail.com
Tested-by: syzbot+bf2c35fa302ebe3c7471@syzkaller.appspotmail.com
Tested on:
commit: 08768b86 mm/huge_memory: check pmd_special() only afte..
git tree: https://github.com/davidhildenbrand/linux.git copy_huge_pmd_pfn
console output: https://syzkaller.appspot.com/x/log.txt?x=1087aaa9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc30a30374b0753
dashboard link: https://syzkaller.appspot.com/bug?extid=bf2c35fa302ebe3c7471
compiler: Debian clang version 15.0.6, 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-09-27 4:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 12:18 syzbot
2024-09-24 14:45 ` David Hildenbrand
2024-09-25 16:59 ` Peter Xu
2024-09-26 10:48 ` David Hildenbrand
2024-09-26 13:39 ` Peter Xu
2024-09-26 15:25 ` David Hildenbrand
2024-09-26 15:45 ` David Hildenbrand
2024-09-27 4: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=66f63272.050a0220.38ace9.0009.GAE@google.com \
--to=syzbot+bf2c35fa302ebe3c7471@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=jgg@ziepe.ca \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox