From: "Eric W. Biederman" <ebiederm@xmission.com>
To: xu xin <cgel.zte@gmail.com>
Cc: bsingharora@gmail.com, akpm@linux-foundation.org,
deng.changcheng@zte.com.cn, linux-kernel@vger.kernel.org,
balbir@linux.vnet.ibm.com, xu.xin16@zte.com.cn,
Linux Containers <containers@lists.linux.dev>
Subject: Re: [PATCH resend] kernel: Make taskstats available via genetlink per namespace
Date: Tue, 22 Feb 2022 18:00:42 -0600 [thread overview]
Message-ID: <87v8x678ph.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <20220221032202.1925507-1-xu.xin16@zte.com.cn> (xu xin's message of "Mon, 21 Feb 2022 03:22:02 +0000")
xu xin <cgel.zte@gmail.com> writes:
> Currently, the application getdelays cannot get taskstats in a net
> namespace. The returned error is just like the following:
> -sh-4.4# ps -ef | tail -5
> root 186 2 0 09:23 ? 00:00:00 [kworker/2:1H]
> root 187 2 0 09:23 ? 00:00:00 [kworker/0:2-eve]
> root 190 183 0 09:23 ? 00:00:00 -sh
> root 198 190 0 09:25 ? 00:00:00 ps -ef
> root 199 190 0 09:25 ? 00:00:00 tail -5
> -sh-4.4#
> -sh-4.4# ./getdelays -d -p 186 -v
> print delayacct stats ON
> debug on
> Error getting family id, errno 0
>
> As more and more applications are deployed in containers like Docker,
> it is necessary to support getdelays to be used in net namespace.
> Taskstats is safe for use per namespace as genetlink checks the
> capability of namespace message by netlink_ns_capable().
>
> Make taskstats available via genetlink per namespace.
Let me add a polite nack to this patch.
Taskstats is completely senseless in a network namespace. There is no
translation of identifiers into the context of the receiver of the
message.
As such taskstats can not be meaningfully used in a container.
To make this work requires updating the taskstats code to do something
sensible when in a pid namespace, as well as when in a network
namespace.
I would like to give a suggest on how to do something sensible but
I don't have any idea at this point. The code would have been converted
long ago on general principles if this was a straight forward thing to
do.
The taskstats interface only makes sense when you are within all of the
initial namespaces.
Eric
> Reported-by: Changcheng Deng <deng.changcheng@zte.com.cn>
> Signed-off-by: xu xin <xu.xin16@zte.com.cn>
> ---
> kernel/taskstats.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/taskstats.c b/kernel/taskstats.c
> index 2b4898b4752e..4d6bcaaf52a0 100644
> --- a/kernel/taskstats.c
> +++ b/kernel/taskstats.c
> @@ -664,6 +664,7 @@ static struct genl_family family __ro_after_init = {
> .module = THIS_MODULE,
> .ops = taskstats_ops,
> .n_ops = ARRAY_SIZE(taskstats_ops),
> + .netnsok = true,
> };
>
> /* Needed early in initialization */
next parent reply other threads:[~2022-02-23 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220217093945.1904085-1-xu.xin16@zte.com.cn>
[not found] ` <20220221032202.1925507-1-xu.xin16@zte.com.cn>
2022-02-23 0:00 ` Eric W. Biederman [this message]
2022-02-23 4:56 ` [PATCH resend] kernel: Make taskstats available via genetlink per namespace cgel.zte
2022-02-27 11:16 ` cgel.zte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8x678ph.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=cgel.zte@gmail.com \
--cc=containers@lists.linux.dev \
--cc=deng.changcheng@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=xu.xin16@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox