lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250709090311.GP452973@horms.kernel.org>
Date: Wed, 9 Jul 2025 10:03:11 +0100
From: Simon Horman <horms@...nel.org>
To: Matt Johnston <matt@...econstruct.com.au>
Cc: Jeremy Kerr <jk@...econstruct.com.au>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 1/8] net: mctp: mctp_test_route_extaddr_input
 cleanup

On Wed, Jul 09, 2025 at 04:31:02PM +0800, Matt Johnston wrote:
> The sock was not being released. Other than leaking, the stale socket
> will conflict with subsequent bind() calls in unrelated MCTP tests.
> 
> Fixes: 11b67f6f22d6 ("net: mctp: test: Add extaddr routing output test")

Hi Matt,

What I assume is that commit seems to have a different hash in net-next.

Fixes: 46ee16462fed ("net: mctp: test: Add extaddr routing output test")

> Signed-off-by: Matt Johnston <matt@...econstruct.com.au>
> 
> ---
> Added in v3. The problem was introduced in current net-next so
> this patch isn't needed in the stable tree.

Ack, thanks for noting that.

...

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ