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: <20140130142740.GC2185@casper.infradead.org> Date: Thu, 30 Jan 2014 14:27:40 +0000 From: Thomas Graf <tgraf@...g.ch> To: Tom Gundersen <teg@...m.no> Cc: netdev@...r.kernel.org, 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 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists