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: <162128521051.2358.9331634734737426572.git-patchwork-notify@kernel.org>
Date:   Mon, 17 May 2021 21:00:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Seth David Schoen <schoen@...alty.org>
Cc:     netdev@...r.kernel.org, gnu@...d.com, dave.taht@...il.com,
        davem@...emloft.net, yoshfuji@...ux-ipv6.org, dsahern@...nel.org
Subject: Re: [RESEND PATCH net-next 0/2] Treat IPv4 lowest address as ordinary
 unicast address

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Wed, 12 May 2021 21:36:25 -0700 you wrote:
> Treat the lowest address in a subnet (the address within the subnet
> which contains all 0 bits) as an ordinary unicast address instead
> of as a potential second broadcast address.  For example, in subnet
> 192.168.17.24/29, which contains 8 addresses, make address 192.168.17.24
> usable as a normal unicast address (while continuing to support
> 192.168.17.31 as a broadcast address).
> 
> [...]

Here is the summary with links:
  - [RESEND,net-next,1/2] ip: Treat IPv4 segment's lowest address as unicast
    https://git.kernel.org/netdev/net-next/c/94c821c74bf5
  - [RESEND,net-next,2/2] selftests: Lowest IPv4 address in a subnet is valid
    https://git.kernel.org/netdev/net-next/c/6101ca0384e3

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ