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: <20231020120436.7fbed61c@kernel.org>
Date: Fri, 20 Oct 2023 12:04:36 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, johannes.berg@...el.com, mpe@...erman.id.au, j@...fi
Subject: Re: [PATCH net-next 4/6] net: trust the bitmap in
 __dev_alloc_name()

On Fri, 20 Oct 2023 12:38:31 +0200 Jiri Pirko wrote:
> >+	if (i == max_netdevices)
> >+		return -ENFILE;  
> 
> Hmm, aren't you changeing functionality here? I mean, prior to this
> patch, the i of value "max_netdevices" was happily used, wan't it?
> In theory it may break things allowing n-1 netdevices of a name instead
> of n.

Good point, I should add that to the commit message.
But we don't care, right? Nobody is asking to increase
the limit, feel like chances that someone will care 
about 32k vs 32k - 1 devices are extremely low.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ