Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cic8f24ead0b349367@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: x86/mm/pat: use pr_warn() for early W^X warnings
Date: Fri, 11 Sep 2026 06:17:44 -0700	[thread overview]
Message-ID: <6aa3ff78.6e6c5f9e.28f11f.0045.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] x86/mm/pat: use pr_warn() for early W^X warnings
https://lore.kernel.org/all/20260911-fixes-verify-rwx-v2-1-e2cde39b6693@kernel.org
* [PATCH v2] x86/mm/pat: use pr_warn() for early W^X warnings

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/28ec0797-ca6e-4150-9b75-cd4e2a6de68e

***

kernel build error

tree:      linux-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base:      ebaf7c9bbb1e16523d7036e7e1225ad2dfcc6482
arch:      amd64
compiler:  Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/ea743f94-aa34-4a2c-926f-acaefc7db8a0/config

arch/x86/mm/pat/set_memory.c:708:16: error: expected ')'

***

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.

To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[bp@alien8.de dave.hansen@linux.intel.com hpa@zytor.com ihor.solodrai@linux.dev linux-kernel@vger.kernel.org linux-mm@kvack.org luto@kernel.org mingo@redhat.com nathan@kernel.org peterz@infradead.org rppt@kernel.org tglx@kernel.org x86@kernel.org]

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-09-11 13:17 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=6aa3ff78.6e6c5f9e.28f11f.0045.GAE@google.com \
    --to=syzbot+cic8f24ead0b349367@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