From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 224D93D9020; Tue, 6 Oct 2026 22:44:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791326708; cv=none; b=UD24OYIgsWbaFOgqg+2EXbqeGBy/WC2d0jX7NUK+eVvJU/su1O3K5+7V+1qDEIoERhoLKSu3JJpt8GrCTZZ9AmfzyILiiax7g0cVatKg7Df61aQjj22RfLieiwqqY31qx+1/G7ZJeZ+2e2Cmrz+I1Y9TItCwCTCtM/GpKw28/q8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791326708; c=relaxed/simple; bh=gp7PRv3WjAiMJrp0DvXpRvTv3mwC8R3NiezXzUE7FxE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: Content-Type:MIME-Version; b=gwiMB154XmSTcswAz1c+nICH3T2gAYaT5K+BNYyDkM8BKegp8zdZk9wqaE75QcQOT69CJrikCNGUJ1gvBV2aSyL6eXpAjCfs0rJvEs9bF0x10nE01rzZv3B5h9P6lpyG7rI0IhTc8Hevk++45tUKW6YAUpASK6mYVXjXsLp+cIs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=JRt56TZf; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="JRt56TZf" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 38E161F0089D; Tue, 6 Oct 2026 22:44:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791326652; bh=Z9zRtXHe/J1k/4/9wAeq1n+PwAt+ioXmV3zyjSNrjDw=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=JRt56TZfdVGUHMpZ795hhhuxEPi16EJHzgB2pK6Czvmgpi23b2x/tWGb82KZBoz9v 6+9UgLzd+PwcrEDpsufFG95+YtlzmJZUwJYIabZ34LNPWYKUljMZ0URzBDnRFS6XB+ Qd+JB2cmPPsv3xSnOZvsYbGP0SAWidr+ChRWu1X/SAgyN8Ifx4LTszU9rGv7+zlpnj p8RrjExGitQ8o+RSMuLR43DtFVwbVobE/5uMyOJS1LPvbgREEGV20Ecop+TOK08Fgs v+GXlZS/q2Win9uUSSDnT0+Rln/y02/VAvoB4gfZAGoMGgUF8U/LrReUTFvUd0iTMA F2yBUWne3dRFQ== From: netdev-bot+sinfo@kernel.org To: Kyle Zeng Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com, outbounddisclosures@openai.com Subject: Re: [PATCH net] neighbour: stop using device addresses in hashes Date: Tue, 06 Oct 2026 22:44:11 +0000 Message-ID: <179132665174.2231598.17151881719703559262@kernel.org> In-Reply-To: <20261006224118.50200-1-kylebot@openai.com> References: <20261006224118.50200-1-kylebot@openai.com> Auto-Submitted: auto-generated Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Hi! This is an automated message. This series looks like a fix, but its commit messages seem to be missing some information: - How the issue was discovered, e.g. hit in production, hit during development, syzbot report, manual code inspection, LLM or static analysis tool scan. - Whether the issue was actually triggered, or is only theoretical (e.g. found by code inspection). If it was triggered please include the symptoms, like the stack trace or error messages. Please do not repost the series just to address the above. Instead, reply to this email with the missing information, so that reviewers can take it into account. If the series needs another revision for other reasons, please include the information in the commit messages then. The evaluation is done by an LLM so it may be wrong, if you think that is the case please reply and explain.