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
| ||
|
Date: Fri, 15 Jul 2022 23:17:15 +0300 From: Vladimir Oltean <olteanv@...il.com> To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com> Cc: Russell King <rmk+kernel@...linux.org.uk>, Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>, Alexandre Belloni <alexandre.belloni@...tlin.com>, Alvin __ipraga <alsi@...g-olufsen.dk>, Claudiu Manoil <claudiu.manoil@....com>, Daniel Scally <djrscally@...il.com>, "David S. Miller" <davem@...emloft.net>, DENG Qingfang <dqfext@...il.com>, Eric Dumazet <edumazet@...gle.com>, Florian Fainelli <f.fainelli@...il.com>, George McCollister <george.mccollister@...il.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Hauke Mehrtens <hauke@...ke-m.de>, Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Jakub Kicinski <kuba@...nel.org>, Kurt Kanzenbach <kurt@...utronix.de>, Landen Chao <Landen.Chao@...iatek.com>, Linus Walleij <linus.walleij@...aro.org>, linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org, Matthias Brugger <matthias.bgg@...il.com>, netdev@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>, "Rafael J. Wysocki" <rafael@...nel.org>, Sakari Ailus <sakari.ailus@...ux.intel.com>, Sean Wang <sean.wang@...iatek.com>, UNGLinuxDriver@...rochip.com, Vivien Didelot <vivien.didelot@...il.com>, Woojung Huh <woojung.huh@...rochip.com>, Marek BehĂșn <kabel@...nel.org> Subject: Re: [PATCH net-next 2/6] software node: allow named software node to be created On Fri, Jul 15, 2022 at 10:57:55PM +0300, Andy Shevchenko wrote: > On Fri, Jul 15, 2022 at 05:01:32PM +0100, Russell King wrote: > > From: Vladimir Oltean <vladimir.oltean@....com> > > > > Allow a named software node to be created, which is needed for software > > nodes for a fixed-link specification for DSA. > > In general I have no objection, but what's worrying me is a possibility to > collide in namespace. With the current code the name is generated based on > unique IDs, how can we make this one more robust? Could you be more clear about the exact concern?
Powered by blists - more mailing lists