From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) (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 99C19533D6 for ; Sun, 30 Nov 2025 12:46:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.199 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764506812; cv=none; b=eZ4dAhQsKDye1oEMGpxvD21iwCznogHUTj8yINaTb7lhtAIwWPKpFY53U2hlKolpZM2cojR7ithQYrtgj+vzPar8AgxBzr0p5brTiF5NvxO4ddZ5OyBo1fjj1KN90fKOeVk0fIVP7llJLiHNkBpVg84dZhJhAaEWu/fhlsPMZes= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764506812; c=relaxed/simple; bh=7ktjHt+JXRQBOigqH3OFjq+Y79rLOQBxeeu2Zkl/EwI=; h=MIME-Version:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=ctiv75BcTXJDcKJQ/yHPvKixmYJdEtE+C7gziKoUblgQm4cKgGAfppB/veZLSlfZdSYhGvlyGyWUsjUa02b1ex6hxHAlBNUYVv6hU2mwJ2XHzMeNZexwk8sAyISWNzYUakGg39zRjMaH2QnP5poJgq8SQZC1IN9MiEZGXbHlb9M= 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.166.199 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-il1-f199.google.com with SMTP id e9e14a558f8ab-43478824a6fso23520905ab.3 for ; Sun, 30 Nov 2025 04:46:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764506810; x=1765111610; h=cc:to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=nwAi9ULLzr9FQ02aKHWkzEjt9pkLkyX6dF3A+NNVVZE=; b=DokexUd1iXdpMA6YoqEOquxGdbHGusXozVs/nurfbJlZa8JWPxyGkSD6FuqEL3HBPj gXv5YeON75/pxZrnX7y179i7hIGvHswkP3T8KtsqlQeU6pWaGG4x1XT0b8/EboKk6AOM 5W/+ygTZPMOFmW+e5ZIU4YrX2ztz5aen22PKlNM9PfmVmKMTzkHPusue/XDqRQwtdd52 xN4eXPpyk6yek7JlA1Zd4U3vKqY1zfkb3hsSPng/YF6RSJNRxQsVVWqtxIg/rOl2NH/i v2nVqr0R3WQzSi8L0mizCDMJnSsBvmFr3xl9P4ISCmhufHpdNqlolCvYqhvsIrUGFCTM yAMg== X-Gm-Message-State: AOJu0YyyVp95AqMLRHeM91e2lbk9cgyfCVeDe187e9zAhzsqwUFQnCUM 4EQFjN/ep9+3EqZIHX8BJ828FvYM9ONOVXdJjJnG2bOlSR7fDyfkgEaay3wzD0ZzIMkyW/NAeee Viqp1b9wmtDSsv5bjsnwxxBCyUQ7oel5tui6HEfcvDyXEtqtp+sABwcLbz4o= X-Google-Smtp-Source: AGHT+IG3dYD6Mg6lX16C8a3MKg583YABV5pCHRIOcPqfJOIJ5iqm51YBnSnaYu4OXUzPU0gF811xF99vRIQRBv8Pku7hTfeOtEJ/ Precedence: bulk X-Mailing-List: syzbot@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1c29:b0:435:9247:12c6 with SMTP id e9e14a558f8ab-435dd10fff6mr175004345ab.34.1764506809755; Sun, 30 Nov 2025 04:46:49 -0800 (PST) Date: Sun, 30 Nov 2025 04:46:49 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <692c3cb9.a70a0220.d98e3.0171.GAE@google.com> Subject: [moderation/CI] Re: mm/memblock: Fix reserve_mem allocation overlapping KHO scratch regions 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 [v1] mm/memblock: Fix reserve_mem allocation overlapping KHO scratch regions https://lore.kernel.org/all/20251130172939.574999-1-swarajgaikwad1925@gmail.com * [PATCH RFC] mm/memblock: Fix reserve_mem allocation overlapping KHO scratch regions and found the following issue: kernel build error Full report is available here: https://ci.syzbot.org/series/2063e5cf-1386-4258-a5f2-b62263550a7b *** kernel build error tree: mm-new URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git base: 8ad78d36c2877966b6a5507987ae072b5b8456c0 arch: amd64 compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 config: https://ci.syzbot.org/builds/89c1614d-75f5-4cd6-82fc-b13b1759edfa/config mm/memblock.c:2692:18: error: use of undeclared identifier 'kho_scratch_cnt' mm/memblock.c:2693:19: error: use of undeclared identifier 'kho_scratch' mm/memblock.c:2694:17: error: use of undeclared identifier 'kho_scratch' mm/memblock.c:2694:39: error: use of undeclared identifier 'kho_scratch' *** 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 david.hunter.linux@gmail.com linux-kernel@vger.kernel.org linux-mm@kvack.org rppt@kernel.org skhan@linuxfoundation.org swarajgaikwad1925@gmail.com] If the report looks fine to you, reply with: #syz upstream