archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <>
To: Jann Horn <>
Cc: Al Viro <>,, Michal Hocko <>,
	Oleg Nesterov <>,, kernel list <>
Subject: Re: [linux-next] BUG triggered in ptraceme
Date: Thu, 27 Sep 2018 18:41:48 +0300	[thread overview]
Message-ID: <20180927154148.GQ15710@uranus> (raw)
In-Reply-To: <>

On Thu, Sep 27, 2018 at 05:35:10PM +0200, Jann Horn wrote:
> >
> > Lets wait for fs people opinions.
> No reply yet - I guess I should just fix up the traceme case for now.
Yes please.

      reply	other threads:[~2018-09-27 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180919070737.GB17524@uranus.lan>
     [not found] ` <20180919071056.GC17524@uranus.lan>
2018-09-19 14:16   ` [linux-next] BUG triggered in ptraceme Jann Horn
2018-09-19 16:13     ` Cyrill Gorcunov
2018-09-27 15:35       ` Jann Horn
2018-09-27 15:41         ` Cyrill Gorcunov [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180927154148.GQ15710@uranus \ \ \ \ \ \ \ \ \

* 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).