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 194961E5714; Mon, 19 Oct 2026 08:39:00 +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=1792399142; cv=none; b=otImXDlVMYc9QcIeM8tfsyfuUgaxx5po2VMibiPsq7vap9NiUwzwjYFOMUZWLWsC7qErtyZE6rYPpzj27OsG+oXjGw7bHbtRvxcJTlxay/9G71WMNMO59sLrRELvgmlM0rqRwmpaWvUzO8KVS8D6ychNboUhGDv+eZ9Ym55NUfc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792399142; c=relaxed/simple; bh=gp7PRv3WjAiMJrp0DvXpRvTv3mwC8R3NiezXzUE7FxE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: Content-Type:MIME-Version; b=JQbw/J6dsNKV87kn7acz5irV2DmuZvTI6L4QNxLEKolVdscyjyTBzXe4qspLdS/uGsU0MfZo/UBg770q8rLHAoahTV4LgsqR2A4N4AArON4F/jGiJUpALinNVC5VtglnlxlOyBDkz4KHawWEvAeK5qLmd5qzB4+pgSHzAul08pQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=SgeeQBJA; 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="SgeeQBJA" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B81A81F000C4; Mon, 19 Oct 2026 08:38:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1792399140; bh=Z9zRtXHe/J1k/4/9wAeq1n+PwAt+ioXmV3zyjSNrjDw=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=SgeeQBJAhEL/RUosp9h+EW/ABgRi7/SGciqMzVHWcPmN5TD/KPYLHYiofOr0Jvflx j7S/CBLlezdgyjqpiQuGxVZpU7r6LePIuyZZkPHTFIsXjc8i3UOSLgkQUwhjidi5A+ YYiqWsYkG1UjkuYmuhCLEq/8b1NLzTCeVU1EmweKbLukPC2IVH0IhOT3YIYlXCoV7Y o7PolMxtcTd5lHZS5Zl2lIi6BRJHqZScelJiyxr+rsSGLuHGE7hVtKlGvB1LnTDZfR Lq2SFmcxFsUOqJ49cit4OdDDzjbw/biDAfLJUetHcXlBmhRbBfbKpDlnveAqTnlmVN Ah6XnEI870E7g== From: netdev-bot+sinfo@kernel.org To: lirongqing Cc: Jiri Pirko , Andrew Lunn , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Hangbin Liu , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] team: fix promisc/allmulti leak in team_port_add error path Date: Mon, 19 Oct 2026 08:38:59 +0000 Message-ID: <179239913930.3290.4555356210564894333@kernel.org> In-Reply-To: <20261019083122.1841-1-lirongqing@baidu.com> References: <20261019083122.1841-1-lirongqing@baidu.com> Auto-Submitted: auto-generated Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Precedence: bulk X-Mailing-List: netdev@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.