linux-kernel - Re: [PATCH] ptrace: make former thread ID available via PTRACE_GETEVENTMSG after PTRACE_EVENT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <BANLkTikFNs6ZyoRKo=_65JpqwJLd-E1UwQ@mail.gmail.com>
Date:	Tue, 28 Jun 2011 18:49:01 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Denys Vlasenko <vda.linux@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ptrace: make former thread ID available via
 PTRACE_GETEVENTMSG after PTRACE_EVENT_EXEC stop (v.2)

Hello,

On Tue, Jun 28, 2011 at 6:35 PM, Oleg Nesterov <oleg@...hat.com> wrote:
> I do not really understand your concerns. Yes, yes, yes, if we do not
> bind this feauture with PT_SEIZED, then the application has to take
> care _if_ it wants to use it without PT_SEIZED. So what? This is the
> problem of that application. This change can't break the application
> which do not want or do not know about this feature.

It's not really a technical concern, more about documentation
simplicity.  It's just simpler to be able to say "blah blah changes
when seized".

> a bit better, bit still not very nice. For what? I tend to agree with
> Denys, and I think we should listen to the user-space developer who
> actually uses ptrace.
>
> That said, I leave it to you and Denys, personally I am fine either way.

It's minor either way.  Let's go with the current patch then.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/