All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	John Ogness <john.ogness@linutronix.de>,
	Andy Lutomirski <luto@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Borislav Petkov <bp@alien8.de>, Brian Gerst <brgerst@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Linux API <linux-api@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Tycho Andersen <tycho.andersen@canonical.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH] fs/proc: report eip/esp in /prod/PID/stat for coredumping
Date: Fri, 15 Sep 2017 23:03:16 +0200	[thread overview]
Message-ID: <20170915210315.3vg4gdoofrfylepu@gmail.com> (raw)
In-Reply-To: <CA+55aFxgEySMkG=0iO_v9aje7nik6XR3mZYc=4jpNzr9oDqtKA@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> Ingo, I'm assuming I'll get this from the -tip tree, which is where I
> got the original commit that this fixes.
> 
> Thanks,
>                    Linus

Yeah, will do!

Thanks,

	Ingo

  reply	other threads:[~2017-09-15 21:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14  9:42 [PATCH] fs/proc: report eip/esp in /prod/PID/stat for coredumping John Ogness
2017-09-14  9:42 ` John Ogness
2017-09-14 14:51 ` Andy Lutomirski
     [not found] ` <87poatfwg6.fsf-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2017-09-14 15:37   ` Thomas Gleixner
2017-09-14 15:37     ` Thomas Gleixner
2017-09-15 19:08     ` Linus Torvalds
2017-09-15 19:08       ` Linus Torvalds
2017-09-15 21:03       ` Ingo Molnar [this message]
2017-09-15 21:09   ` [tip:core/urgent] fs/proc: Report " tip-bot for John Ogness
2017-09-15 21:09     ` tip-bot for John Ogness
2017-09-15 21:36   ` tip-bot for John Ogness
2017-09-15 21:36     ` tip-bot for John Ogness

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=20170915210315.3vg4gdoofrfylepu@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=john.ogness@linutronix.de \
    --cc=keescook@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=tycho.andersen@canonical.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.