Re: [linux-next] BUG triggered in ptraceme

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jann Horn <jannh@xxxxxxxxxx>
Subject: Re: [linux-next] BUG triggered in ptraceme
From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
Date: Thu, 27 Sep 2018 18:41:48 +0300
Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, Michal Hocko <mhocko@xxxxxxxxxx>, Oleg Nesterov <oleg@xxxxxxxxxx>, avagin@xxxxxxxxxxxxx, kernel list <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <CAG48ez0bKkv1rM-NDMNJMVO94_T92VAe_ABbGud1aOh_7UxaOg@mail.gmail.com>
User-agent: Mutt/1.10.1 (2018-07-13)

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.

References:
- Re: [linux-next] BUG triggered in ptraceme
  - From: Jann Horn
- Re: [linux-next] BUG triggered in ptraceme
  - From: Cyrill Gorcunov
- Re: [linux-next] BUG triggered in ptraceme
  - From: Jann Horn

Prev by Date: Re: [linux-next] BUG triggered in ptraceme
Next by Date: Re: [PATCH v7 3/6] seccomp: add a way to get a listener fd from ptrace
Previous by thread: Re: [linux-next] BUG triggered in ptraceme
Next by thread: [fuse] When do writes to fuse fd block?
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux