From: syzbot <syzbot+9f9a7f73fb079b2387a6@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, surajsonawane0215@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] kernel BUG in const_folio_flags (2)
Date: Sun, 24 Nov 2024 23:18:02 -0800 [thread overview]
Message-ID: <674424aa.050a0220.1cc393.006a.GAE@google.com> (raw)
In-Reply-To: <CAHiZj8hdRB=x0XBn-MT_kH+FTEL5Tu0_yMDfuB_RccSScuyE1Q@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
./include/linux/page-flags.h:309:25: error: implicit declaration of function 'folio_nr_pages'; did you mean 'folio_page'? [-Werror=implicit-function-declaration]
./include/linux/mm.h:2056:20: error: conflicting types for 'folio_nr_pages'; have 'long int(const struct folio *)'
Tested on:
commit: 9f16d5e6 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c4515f1b6a4e50b7
dashboard link: https://syzkaller.appspot.com/bug?extid=9f9a7f73fb079b2387a6
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=1718a5c0580000
next prev parent reply other threads:[~2024-11-25 7:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 7:31 [syzbot] [mm?] kernel BUG in const_folio_flags (2) syzbot
2024-11-25 6:56 ` Suraj Sonawane
2024-11-25 6:58 ` syzbot
2024-11-25 7:16 ` Suraj Sonawane
2024-11-25 7:18 ` syzbot [this message]
2024-11-25 7:37 ` Suraj Sonawane
2024-11-25 7:39 ` syzbot
2024-11-25 7:53 ` Suraj Sonawane
2024-11-25 7:55 ` syzbot
2024-11-25 7:57 ` Suraj Sonawane
2024-11-25 7:59 ` syzbot
2024-11-25 13:12 ` Suraj Sonawane
2024-11-25 13:43 ` syzbot
2024-11-28 10:52 ` David Hildenbrand
2024-11-28 11:42 ` Hillf Danton
2024-11-28 12:02 ` David Hildenbrand
2024-11-28 12:23 ` David Hildenbrand
2024-11-28 13:03 ` Hillf Danton
2024-11-28 13:37 ` syzbot
2024-11-28 12:57 ` David Hildenbrand
2024-11-28 13:18 ` 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=674424aa.050a0220.1cc393.006a.GAE@google.com \
--to=syzbot+9f9a7f73fb079b2387a6@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surajsonawane0215@gmail.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.