mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jessica Frazelle <me@jessfraz.com>
Cc: Kees Cook <keescook@google.com>, Xing Gao <xgao01@email.wm.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	"kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: /proc/timer_list leaks the real pids of the associated processes
Date: Wed, 8 Feb 2017 10:47:23 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1702081045440.3536@nanos> (raw)
In-Reply-To: <CAEk6tEyzgCV5YWppu5OwxjFz6royvXmJM-Qs_mKTUSsqeR7wZw@mail.gmail.com>

On Tue, 7 Feb 2017, Jessica Frazelle wrote:

> So I used to use this "feature" as a hack to see if something was
> running in a k8s cluster or not because fluentd gives a lot of things
> away.

That file does not tell you at all whether something is running or not. It
merily tells you that there are timers queued.

> Runc basically decided to mask this file so it stopped happening
> though. But I think namespace aware is the right decision.

Unless you can come up with a real good argument why this is usefull beyond
debugging and crystal ball hackery, it's going to go away.

Thanks,

	tglx

  reply	other threads:[~2017-02-08  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJwLwmYQt2ae_Y-TDXhPGsX5im29ATwwKmg3FtUC=6HjrzH4HA@mail.gmail.com>
2017-02-03 23:44 ` Kees Cook
2017-02-07 22:48   ` Thomas Gleixner
2017-02-07 22:56     ` Jessica Frazelle
2017-02-08  9:47       ` Thomas Gleixner [this message]
2017-02-07 23:24     ` Kees Cook
2017-02-07 23:34       ` Kees Cook

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=alpine.DEB.2.20.1702081045440.3536@nanos \
    --to=tglx@linutronix.de \
    --cc=ebiederm@xmission.com \
    --cc=keescook@google.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@jessfraz.com \
    --cc=xgao01@email.wm.edu \
    /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
all inboxes | Powered by JetHome®