From: David Ahern <dsahern@gmail.com>
To: Vasily Averin <vvs@virtuozzo.com>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: How to identify net namespace in kernel messages?
Date: Mon, 6 Nov 2017 09:21:32 +0900 [thread overview]
Message-ID: <83dd4cb9-1f99-02a1-39e8-68751e4ee9d5@gmail.com> (raw)
In-Reply-To: <a7e5f770-f88f-6e93-d054-d7ce879e5569@virtuozzo.com>
On 11/6/17 5:56 AM, Vasily Averin wrote:
> On 2017-11-05 15:48, David Miller wrote:
>> From: Vasily Averin <vvs@virtuozzo.com>
>>> I doubt that pointer to freed net have value for someone except
>>> developers, on the other hand it helps to speed up the problem
>>> investigation.
>>
>> Any kernel pointer printed has value to attackers.
>
> David, could you please advise how to identify net namespace in kernel messages?
>
> In OpenVz we got many requests from host admins, they need to understand
> which container triggered the message. In such cases we have added our custom
> Container Id, but mainline lacks it.
>
> I expected that mainline can use net pointer for such purposes,
> nfsd does it for example:
>
> NFSD: starting 90-second grace period (net ffff880e307fe240)
>
> Now you recommend do not use net pointer.
> However could you please advise some alternative?
>
Perf now exports the device and inode. see perf_ns_link_info and its use.
next prev parent reply other threads:[~2017-11-06 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 10:02 [PATCH 20/21] phonet: exit_net cleanup check added Vasily Averin
2017-11-05 10:17 ` Rémi Denis-Courmont
2017-11-05 10:52 ` Vasily Averin
2017-11-05 12:48 ` David Miller
2017-11-05 20:56 ` How to identify net namespace in kernel messages? Vasily Averin
2017-11-06 0:21 ` David Ahern [this message]
2017-11-05 13:16 ` [PATCH 20/21] phonet: exit_net cleanup check added kbuild test robot
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=83dd4cb9-1f99-02a1-39e8-68751e4ee9d5@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vvs@virtuozzo.com \
/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;
as well as URLs for NNTP newsgroup(s).