From: syzbot ci <syzbot+cib99b951dec2336a5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/memory-failure: fix concurrent access issue in min_order_for_split()
Date: Wed, 05 Aug 2026 01:32:41 -0700 [thread overview]
Message-ID: <6a72f529.13623e66.bdc14.0056.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] mm/memory-failure: fix concurrent access issue in min_order_for_split()
https://lore.kernel.org/all/20260805072625.2437636-1-dayou5941@163.com
* [PATCH v2] mm/memory-failure: fix concurrent access issue in min_order_for_split()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/840418d2-f62b-4ce1-a5c9-a3efc9275fca
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: e47602c51d20a93fa1711ed896dc9480de4374d9
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/9bcfa5db-a65f-4a0a-adeb-25cfc52714d9/config
mm/memory-failure.c:2517:13: error: cannot assign to variable 'new_order' with const-qualified type 'const int'
mm/memory-failure.c:2873:13: error: cannot assign to variable 'new_order' with const-qualified type 'const int'
***
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 david@kernel.org dayou5941@163.com linux-mm@kvack.org liyouhong@kylinos.cn ljs@kernel.org sashiko-bot@kernel.org stable@vger.kernel.org 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
next reply other threads:[~2026-08-05 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 8:32 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-05 10:02 [moderation/CI] Re: mm/memory-failure: fix concurrent access issue in min_order_for_split() syzbot ci
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=6a72f529.13623e66.bdc14.0056.GAE@google.com \
--to=syzbot+cib99b951dec2336a5@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 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.