From: Greg KH <gregkh@linuxfoundation.org>
To: zhangq95 <qiangzh.hust@gmail.com>
Cc: linux-kernel@vger.kernel.org, tj@kernel.org, lizefan@huawei.com,
hannes@cmpxchg.org, mingo@redhat.com, peterz@infradead.org,
cgroups@vger.kernel.org, riel@redhat.com, gs051095@gmail.com,
akpm@linux-foundation.org, oleg@redhat.com, tglx@linutronix.de,
keescook@chromium.org, longman@redhat.com, prsood@codeaurora.org,
guro@fb.com, davem@davemloft.net, mhocko@suse.com,
kirill.shutemov@linux.intel.com, marcos.souza.org@gmail.com,
hoeun.ryu@gmail.com, rostedt@goodmis.org, bigeasy@linutronix.de,
alexander.levin@verizon.com, paulmck@linux.vnet.ibm.com,
fweisbec@gmail.com
Subject: Re: [PATCH] Add a file named cgroup.procs_stat in cgroup
Date: Fri, 4 May 2018 10:31:47 -0700 [thread overview]
Message-ID: <20180504173147.GA4649@kroah.com> (raw)
In-Reply-To: <1525444100-4858-1-git-send-email-qiangzh.hust@gmail.com>
On Fri, May 04, 2018 at 10:28:20PM +0800, zhangq95 wrote:
> When I run "cat /proc/stat" in a container, container will access
> host's file directly which is a security risk.
Why is this a "security risk"? What can be learned there that is
somehow "bad"?
thanks,
greg k-h
next prev parent reply other threads:[~2018-05-04 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 14:28 [PATCH] Add a file named cgroup.procs_stat in cgroup zhangq95
2018-05-04 15:43 ` Peter Zijlstra
2018-05-04 17:31 ` Greg KH [this message]
2018-05-05 7:15 ` kbuild test robot
2018-05-05 7:15 ` kbuild test robot
2018-05-05 7:34 ` 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=20180504173147.GA4649@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=bigeasy@linutronix.de \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=gs051095@gmail.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hoeun.ryu@gmail.com \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=marcos.souza.org@gmail.com \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=prsood@codeaurora.org \
--cc=qiangzh.hust@gmail.com \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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