netdev - Re: [patch net-next] net: add netnotifier event for upper device change

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: <20130526071039.GA1560@minipsycho.orion>
Date:	Sun, 26 May 2013 09:10:39 +0200
From:	Jiri Pirko <jiri@...nulli.us>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, edumazet@...gle.com,
	alexander.h.duyck@...el.com, xiyou.wangcong@...il.com
Subject: Re: [patch net-next] net: add netnotifier event for upper device
 change

Sun, May 26, 2013 at 08:14:13AM CEST, davem@...emloft.net wrote:
>From: Jiri Pirko <jiri@...nulli.us>
>Date: Sat, 25 May 2013 16:12:10 +0200
>
>> Now when upper device is changed, event is not propagated via RT Netlink
>> to userspace. Userspace might never now about the change. Fix this by
>> adding upper-device-change notifier event.
>> 
>> Signed-off-by: Jiri Pirko <jiri@...nulli.us>
>
>Looks good, applied, thanks Jiri.
>
>If someone is looking for a useful project, switching networking over to
>a more typed notifier system would be a worthwhile improvement.
>
>It's hard to right now to communicate what changed beyond "action X
>happened to this object, you have to check to see exactly how it
>changed"

Hmm. Do you have something particular in mind? My first thought was
passing some union instead of NETDEV_* numbers.

>
>This came up recently with the IFF_NOARP stuff.

Can you point me to the discussion?

Thanks

Jiri
--
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