From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Jann Horn <jannh@google.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Michal Hocko <mhocko@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
avagin@virtuozzo.com, kernel list <linux-kernel@vger.kernel.org>
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: <CAG48ez0bKkv1rM-NDMNJMVO94_T92VAe_ABbGud1aOh_7UxaOg@mail.gmail.com>
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.
prev parent reply other threads:[~2018-09-27 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 7:07 [linux-next] BUG triggered in ptraceme Cyrill Gorcunov
2018-09-19 7:10 ` Cyrill Gorcunov
2018-09-19 14:16 ` 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:
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=20180927154148.GQ15710@uranus \
--to=gorcunov@gmail.com \
--cc=avagin@virtuozzo.com \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=oleg@redhat.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 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).