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
| ||
|
Message-ID: <de35cbb1-e02e-5777-b80b-738e4c695bdb@rasmusvillemoes.dk> Date: Thu, 15 Dec 2022 13:09:21 +0100 From: Rasmus Villemoes <linux@...musvillemoes.dk> To: Pavel Machek <pavel@....cz>, Sasha Levin <sashal@...nel.org> Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org, Jacob Keller <jacob.e.keller@...el.com>, "David S . Miller" <davem@...emloft.net>, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org Subject: Re: [PATCH AUTOSEL 4.9 2/2] net: loopback: use NET_NAME_PREDICTABLE for name_assign_type On 15/12/2022 11.59, Pavel Machek wrote: > Hi! > >> From: Rasmus Villemoes <linux@...musvillemoes.dk> >> >> [ Upstream commit 31d929de5a112ee1b977a89c57de74710894bbbf ] >> >> When the name_assign_type attribute was introduced (commit >> 685343fc3ba6, "net: add name_assign_type netdev attribute"), the >> loopback device was explicitly mentioned as one which would make use >> of NET_NAME_PREDICTABLE: >> >> The name_assign_type attribute gives hints where the interface name of a >> given net-device comes from. These values are currently defined: >> ... >> NET_NAME_PREDICTABLE: >> The ifname has been assigned by the kernel in a predictable way >> that is guaranteed to avoid reuse and always be the same for a >> given device. Examples include statically created devices like >> the loopback device [...] >> >> Switch to that so that reading /sys/class/net/lo/name_assign_type >> produces something sensible instead of returning -EINVAL. > > This was already part of the previous autosel: Yup, but it was punted for a week: https://lore.kernel.org/lkml/Y5AO7TrYsdeVqyI6@sashalap/
Powered by blists - more mailing lists