Linux-mm Archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+9319a4268a640e26b72b@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, cgroups@vger.kernel.org,
	hannes@cmpxchg.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, mhocko@kernel.org,  muchun.song@linux.dev,
	roman.gushchin@linux.dev, shakeel.butt@linux.dev,
	 syzkaller-bugs@googlegroups.com, yosryahmed@google.com,
	yuzhao@google.com
Subject: Re: [syzbot] [mm?] [cgroups?] WARNING in __mod_memcg_lruvec_state
Date: Mon, 06 May 2024 09:13:03 -0700	[thread overview]
Message-ID: <0000000000001623740617cb58a7@google.com> (raw)
In-Reply-To: <ZjjlLcjHuQoV-7gh@google.com>

Hello,

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

mm/rmap.c:1444:25: error: incompatible pointer types passing 'struct folio *' to parameter of type 'struct pglist_data *' [-Werror,-Wincompatible-pointer-types]


Tested on:

commit:         2b84edef Add linux-next specific files for 20240506
git tree:       linux-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=b499929e4aaba1af
dashboard link: https://syzkaller.appspot.com/bug?extid=9319a4268a640e26b72b
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1655a590980000



      parent reply	other threads:[~2024-05-06 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  8:03 [syzbot] [cgroups?] [mm?] WARNING in __mod_memcg_lruvec_state syzbot
2024-04-04  1:07 ` Andrew Morton
2024-04-04 23:36   ` Yosry Ahmed
2024-04-05  1:44     ` Yu Zhao
2024-04-05  4:47       ` Yosry Ahmed
2024-04-14  4:43         ` Shakeel Butt
2024-05-06 13:03 ` [syzbot] [mm?] [cgroups?] " syzbot
2024-05-06 14:11   ` Yosry Ahmed
2024-05-06 15:59     ` Shakeel Butt
2024-05-06 16:12       ` Yosry Ahmed
2024-05-06 16:13     ` 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=0000000000001623740617cb58a7@google.com \
    --to=syzbot+9319a4268a640e26b72b@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yosryahmed@google.com \
    --cc=yuzhao@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).