Re: [PATCH 0/3] kobject: support namespace aware udev

[Greg KH]

On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
> Currently when a uevent occurs, the event is replicated and sent to every
> listener on the kernel netlink socket, ignoring network namespaces boundaries,
> forwarding events to every listener in every network namespace.
> 
> With the expanded use of containers, it would be useful to be able to
> regulate this flow of events to specific containers.  By restricting
> the events to only the host network namespace, it allows for a userspace
> program to provide a system wide policy on which events are routed where.

Interesting, but why do you need a container to get a uevent at all?
What uevents do a container care about?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/