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] [day] [month] [year] [list]
Message-ID: <a9e10c46-c418-4bb0-b366-0a31f35caa6d@redhat.com>
Date: Tue, 1 Apr 2025 12:36:28 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: shaozhengchao@....com, netdev@...r.kernel.org, davem@...emloft.net,
 dsahern@...nel.org, edumazet@...gle.com, kuba@...nel.org
Cc: horms@...nel.org
Subject: Re: [PATCH net-next] ipv4: remove unnecessary judgment in
 ip_route_output_key_hash_rcu

On 4/1/25 4:00 AM, shaozhengchao@....com wrote:
> From: Zhengchao Shao <shaozhengchao@....com>
> 
> In the ip_route_output_key_cash_rcu function, the input fl4 member saddr is
> first checked to be non-zero before entering multicast, broadcast and
> arbitrary IP address checks. However, the fact that the IP address is not
> 0 has already ruled out the possibility of any address, so remove
> unnecessary judgment.
> 
> Signed-off-by: Zhengchao Shao <shaozhengchao@....com>

## Form letter - net-next-closed

Linus already pulled net-next material v6.15 and therefore net-next is
closed for new drivers, features, code refactoring and optimizations. We
are currently accepting bug fixes only.

Please repost when net-next reopens after Apr 7th.

RFC patches sent for review only are obviously welcome at any time.

See:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ