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, 31 Jan 2014 01:57:23 +0100 From: Tom Gundersen <teg@...m.no> To: Thomas Graf <tgraf@...g.ch> Cc: netdev <netdev@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, John Fastabend <john.r.fastabend@...el.com>, Nicolas Dichtel <nicolas.dichtel@...nd.com>, Vlad Yasevich <vyasevich@...il.com>, Marcel Holtmann <marcel@...tmann.org>, "David S. Miller" <davem@...emloft.net> Subject: Re: [PATCH] rtnetlink: return the newly created link in response to newlink Hi Thomas, Thanks for your reply. On Thu, Jan 30, 2014 at 3:27 PM, Thomas Graf <tgraf@...g.ch> wrote: > On 01/30/14 at 02:05pm, Tom Gundersen wrote: >> Userspace needs to reliably know the ifindex of the netdevs it creates, >> as we cannot rely on the ifname staying unchanged. >> >> Earlier, a simlpe NLMSG_ERROR would be returned, but this returns the >> corresponding RTM_NEWLINK on success instead. > > This breaks existing Netlink applications in user space. User space > apps are not prepared to receive both a RTM_NEWLINK reply _and_ > the ACK unless they have set NLM_F_ECHO in the original request. > > You can already reliably retrieve the ifindex by listening to > RTNLGRP_LINK messages and be notified about the link created > including all follow-up renames. Ok, we'll keep doing this instead. Cheers, Tom -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists