public inbox for syzbot@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci85facbaec5ac98a8@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: Free contiguous order-0 pages efficiently
Date: Mon, 16 Mar 2026 08:16:42 -0700	[thread overview]
Message-ID: <69b81eda.050a0220.12d28.0163.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] mm: Free contiguous order-0 pages efficiently
https://lore.kernel.org/all/20260316113209.945853-1-usama.anjum@arm.com
* [PATCH v2 1/3] mm/page_alloc: Optimize free_contig_range()
* [PATCH v2 2/3] vmalloc: Optimize vfree
* [PATCH v2 3/3] mm/page_alloc: Optimize __free_contig_frozen_range()

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/3821b2d3-8f85-4386-ad92-522a3f20be8a

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      c5a81ff6071bcf42531426e6336b5cc424df6e3d
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/e21a9615-d268-47cb-9b35-9882a0513fed/config

mm/page_alloc.c:6810:11: error: call to '__compiletime_assert_1660' declared with 'error' attribute: min(order, ( __builtin_constant_p(nr_pages) ? ((nr_pages) < 2 ? 0 : 63 - __builtin_clzll(nr_pages)) : (sizeof(nr_pages) <= 4) ? __ilog2_u32(nr_pages) : __ilog2_u64(nr_pages) )) signedness error

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: syzbot@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

The email will later be sent to:
[akpm@linux-foundation.org bpf@vger.kernel.org david.hildenbrand@arm.com david@kernel.org dsterba@suse.com hannes@cmpxchg.org jackmanb@google.com liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org mhocko@suse.com rppt@kernel.org ryan.roberts@arm.com surenb@google.com terrelln@fb.com urezki@gmail.com usama.anjum@arm.com vbabka@kernel.org vishal.moola@gmail.com ziy@nvidia.com]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid


                 reply	other threads:[~2026-03-16 15:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=69b81eda.050a0220.12d28.0163.GAE@google.com \
    --to=syzbot+ci85facbaec5ac98a8@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-upstream-moderation@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