Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cie9054e6d791e80a4@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: ACPI: Add support for ACPI RAS2 feature table
Date: Fri, 10 Jul 2026 13:03:31 -0700	[thread overview]
Message-ID: <6a515013.63a5fcd8.28bd53.0004.GAE@google.com> (raw)

syzbot ci has tested the following series

[v22] ACPI: Add support for ACPI RAS2 feature table
https://lore.kernel.org/all/20260709210750.424659-1-shijujose2008@gmail.com
* [PATCH v22 1/2] ACPI:RAS2: Add driver for the ACPI RAS2 feature table
* [PATCH v22 2/2] ras: mem: Add ACPI RAS2 memory driver

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/5040b478-7bdb-4326-a6b4-5685754ec2d4

***

kernel build error

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      1e692e85500fd3a971da0241f044f4572b2be8b6
arch:      amd64
compiler:  Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config:    https://ci.syzbot.org/builds/4aba36a3-6777-42f1-bcad-f10d6ceb7cdf/config

drivers/ras/acpi_ras2.c:68:2: error: call to undeclared function 'iowrite64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:92:20: error: call to undeclared function 'ioread64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:115:2: error: call to undeclared function 'iowrite64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:339:3: error: call to undeclared function 'iowrite64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
drivers/ras/acpi_ras2.c:447:2: error: call to undeclared function 'iowrite64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]

***

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 patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[akpm@linux-foundation.org ashok.raj@oss.qualcomm.com bp@alien8.de dave.hansen@linux.intel.com dferguson@amperecomputing.com duenwen@google.com erdemaktas@google.com gthelen@google.com james.morse@arm.com jiaqiyan@google.com jic23@kernel.org jon.grimm@amd.com jthoughton@google.com kangkang.shen@futurewei.com lenb@kernel.org linux-acpi@vger.kernel.org linux-doc@vger.kernel.org linux-edac@vger.kernel.org linux-mm@kvack.org linuxarm@huawei.com mchehab@kernel.org naoya.horiguchi@nec.com nifan.cxl@gmail.com pgonda@google.com prime.zeng@hisilicon.com rafael@kernel.org rientjes@google.com roberto.sassu@huawei.com rppt@kernel.org shijujose2008@gmail.com somasundaram.a@hpe.com tanxiaofei@huawei.com tony.luck@intel.com wanghuiqiang@huawei.com wbs@os.amperecomputing.com wschwartz@amperecomputing.com yazen.ghannam@amd.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-07-10 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 20:03 syzbot ci [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-12  7:09 [moderation/CI] Re: ACPI: Add support for ACPI RAS2 feature table syzbot ci
2026-03-12  9:16 ` Aleksandr Nogikh

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=6a515013.63a5fcd8.28bd53.0004.GAE@google.com \
    --to=syzbot+cie9054e6d791e80a4@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