From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753762AbbIISYN (ORCPT ); Wed, 9 Sep 2015 14:24:13 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:59998 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753392AbbIISYL (ORCPT ); Wed, 9 Sep 2015 14:24:11 -0400 Date: Tue, 8 Sep 2015 20:54:00 -0700 From: Greg KH To: "Michael J. Coss" Cc: davem@davemloft.net, linux-kernel@vger.kernel.org, containers@lists.linuxcontainers.org, serge.hallyn@ubuntu.com, stgraber@ubuntu.com Subject: Re: [PATCH 0/3] kobject: support namespace aware udev Message-ID: <20150909035400.GA5153@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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