From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f200.google.com (mail-oi1-f200.google.com [209.85.167.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EE8AE41A920 for ; Wed, 5 Aug 2026 10:02:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.200 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785924169; cv=none; b=a2Hwdvg0Hau/mo+xXEwfDr1BCrhVVQLmmBJwnPsWknL72/ox1ZQjSL1p/JErQ5qHVmbPn2tXUcSQGlmiUdYD6Z+AmtL2T0LRzwZm+Fk+ZxyLe/X55QiqkOSgqCVfcgaNrqs9e23LNTrMe4m8mDjuupoI4jyNoxni8aYZtXs+ulQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785924169; c=relaxed/simple; bh=HQNFOSRxPKTlW4UztY1BIBRMx1JnMqGpOnv0T1Riz0c=; h=MIME-Version:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=YWNmtDWNbjjmDDqBwss5+EbTzWiiNtwAxNcvcyMPpJMbcApurnfkDkdOsrKKivn5DxIYlAyAZ+085D5Ui/h7z1HgI2VWxLXp/S8DKSSy0o9vOFt7IuZeLIM/anB9Qr3gFNx21RRp1ycDRxjIdl//09X5cn0T3ZuoUCBX22KVQYM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.200 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi1-f200.google.com with SMTP id 5614622812f47-4ab4f652f9bso510889b6e.0 for ; Wed, 05 Aug 2026 03:02:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785924167; x=1786528967; h=content-type:cc:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=wu5WgtB2Bv0xaju/JD8cYbF/oHyXY28vzdmqQpOVP9s=; b=SIybsgE49HkzzbJUjOHzSO4rS69I682Ae6Zl7+wOWrYdEULnPZIqm/8/Wbe0WZoTHo cdeoo3RJ8w8KRYvxeFBFFCzUGoDa6iVKGZNekPvOk8BVObW+r4NoqX/HLlTEdKYIfMiE Imp+/bS81DWl/HNgaAf7wCQ7R0XJr+rvwqcDp28MKEnppK+LhjeDgOni1cJf9ajaEIAi vxZ3yB+3yvtrFlsVIWmSEFyxO+w5JKD9QtVFY2l2E2O+EpA9AxDpPSD6MOHfRQ7Vc4nt aQmJsVebL1j1UvIfeMX1KcDFo7WyotJQVcCTxNI+0VfB1yIypbWchaaZG9pBPPBDi7yZ 0y5w== X-Gm-Message-State: AOJu0Yx+t3IjkbxHne6Kg0nqMxdOCoCGhi8CdwRSD8bh4KgGnqrJPq1v ZSofEVZOHLIDgPpQyIa9m+hB4bRNF1jc7Nyvxw/zFwD48usIXLVqqUTeBKMlHU+2H8dtP9gYljf 8S9mC9pqL9+ZAYAj6Jm/K+ceAYLEkzpfamE64G+j+8BAybs4gIN9kdqlqn+8= Precedence: bulk X-Mailing-List: syzbot@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:2083:b0:6aa:da04:b56f with SMTP id 006d021491bc7-6ae96c10163mr3005655eaf.3.1785924166765; Wed, 05 Aug 2026 03:02:46 -0700 (PDT) Date: Wed, 05 Aug 2026 03:02:46 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a730a46.13623e66.bdc14.0057.GAE@google.com> Subject: [moderation/CI] Re: mm/memory-failure: fix concurrent access issue in min_order_for_split() From: syzbot ci To: syzkaller-upstream-moderation@googlegroups.com Cc: syzbot@lists.linux.dev Content-Type: text/plain; charset="UTF-8" syzbot ci has tested the following series [v3] mm/memory-failure: fix concurrent access issue in min_order_for_split() https://lore.kernel.org/all/20260805084224.2597547-1-dayou5941@163.com * [PATCH v3] 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/b0ec4d6e-6671-4b25-860d-98cf480bdd8f *** 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/a6869e1a-07af-443d-ba6a-48775cf67ba1/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