public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3511625422f7aa637f0d@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?] general protection fault in do_migrate_pages
Date: Wed, 20 Nov 2024 11:29:02 -0800	[thread overview]
Message-ID: <673e387e.050a0220.363a1b.002c.GAE@google.com> (raw)
In-Reply-To: <b8002d24-9817-4913-8da6-c652e58a971c@redhat.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+3511625422f7aa637f0d@syzkaller.appspotmail.com
Tested-by: syzbot+3511625422f7aa637f0d@syzkaller.appspotmail.com

Tested on:

commit:         ece1262a mm/mempolicy: fix migrate_to_node() assuming ..
git tree:       https://github.com/davidhildenbrand/linux.git mempolicy_vma
console output: https://syzkaller.appspot.com/x/log.txt?x=1702bae8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f401cb14a38a8175
dashboard link: https://syzkaller.appspot.com/bug?extid=3511625422f7aa637f0d
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.


      reply	other threads:[~2024-11-20 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  0:00 [syzbot] [mm?] general protection fault in do_migrate_pages syzbot
2024-11-20 15:38 ` David Hildenbrand
2024-11-20 16:39   ` David Hildenbrand
2024-11-20 18:11     ` David Hildenbrand
2024-11-20 18:38       ` David Hildenbrand
2024-11-20 18:50 ` David Hildenbrand
2024-11-20 19:29   ` 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=673e387e.050a0220.363a1b.002c.GAE@google.com \
    --to=syzbot+3511625422f7aa637f0d@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