From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753423AbdL1MFs (ORCPT ); Thu, 28 Dec 2017 07:05:48 -0500 Received: from mail-wm0-f48.google.com ([74.125.82.48]:44078 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752196AbdL1MFp (ORCPT ); Thu, 28 Dec 2017 07:05:45 -0500 X-Google-Smtp-Source: ACJfBos1aDPwKYnzT1Y3UPiY80xGUrB09PWlEuQXNQcTmZA2kfu38aFvAPacFm+N2dQmZ9UDc/VEng== Date: Thu, 28 Dec 2017 14:05:39 +0200 From: Elad Wexler To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, zbr@ioremap.net Subject: [RFC] Supporting namespaces in the connector driver Message-ID: <20171228120539.GA13368@ewexler> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Hi, I have spent some time looking at the cn_proc monitor capabilities which use the connector driver for monitoring processes. Currently the cn_proc (and all other modules which are using the connector) only works on the main init_user_ns namespace. If I am working inside a docker container (as an example), I won't be able to monitor process creation, for example fork()/exec() etc ... Of course I will be able to monitor any process from the host namespace (init_user_ns) but I would like also to be able to monitor the processes that belong to the same docker container, (belong to the same namespace) I wonder if there is a plan to add pernet support for the connector? If you think it there is a good reason to add that? (I can provide a few patches that do that) I will be happy to work on to add a support for that, and actually I have started to do some modification to make it works. and still testing it. Thanks