All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+35a4414f6e247f515443@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] WARNING in follow_pte
Date: Wed, 03 Jul 2024 18:49:02 -0700	[thread overview]
Message-ID: <000000000000c29a51061c6226ec@google.com> (raw)
In-Reply-To: <20240704013031.977091-1-lizhi.xu@windriver.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

arch/x86/mm/pat/memtype.c:957:27: error: 'struct vm_area_struct' has no member named 'mm'
arch/x86/mm/pat/memtype.c:962:29: error: 'struct vm_area_struct' has no member named 'mm'


Tested on:

commit:         73461051 Merge tag 'erofs-for-6.10-rc7-fixes' of git:/..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=de2d4dc103148cd6
dashboard link: https://syzkaller.appspot.com/bug?extid=35a4414f6e247f515443
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=152339d1980000


       reply	other threads:[~2024-07-04  1:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240704013031.977091-1-lizhi.xu@windriver.com>
2024-07-04  1:49 ` syzbot [this message]
     [not found] <CAMc0M--0X+RmTskfeiz4vzVsPXze0Wv8TYoDVEw0ra+CwGCRMg@mail.gmail.com>
2024-07-11  4:42 ` [syzbot] [kernel?] WARNING in follow_pte syzbot
     [not found] <20240704024831.1805587-1-lizhi.xu@windriver.com>
2024-07-04  3:26 ` syzbot
     [not found] <20240704015732.1230654-1-lizhi.xu@windriver.com>
2024-07-04  2:28 ` syzbot
2024-07-03 18:22 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=000000000000c29a51061c6226ec@google.com \
    --to=syzbot+35a4414f6e247f515443@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --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 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.