linux-kernel - Re: Ptrace documentation, draft #1

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTinO59MFbz679ZyvVR4U8KfwnbNYxQ@mail.gmail.com>
Date:	Wed, 18 May 2011 17:02:11 +0200
From:	Denys Vlasenko <vda.linux@...glemail.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Tejun Heo <tj@...nel.org>, jan.kratochvil@...hat.com,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, indan@....nu
Subject: Re: Ptrace documentation, draft #1

On Mon, May 16, 2011 at 6:53 PM, Oleg Nesterov <oleg@...hat.com> wrote:
>> I think resuming from signal delivery trap
>> should be the only place where @data means signo.
>
> Agreed, it would be more clean/simple/understandable.

I think ptrace API never promised that it will be possible
to "create new signal" by passing non-zero data - only
that the already pending signal can be passed, altered
or suppressed. If there *are* cases where "create new signal"
currently works, it's a quirk.

I changed doc to reflect this. If we tighten it up so that we can state
that all such attempts will be ignored, we can update docs.

-- 
vda
--
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/