linux-kernel - Re: [RFC PATCH v2] Tracepoint: add exec tracepoint

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: <201111041208.38163.pedro@codesourcery.com>
Date:	Fri, 4 Nov 2011 12:08:37 +0000
From:	Pedro Alves <pedro@...esourcery.com>
To:	David Smith <dsmith@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RFC PATCH v2] Tracepoint: add exec tracepoint

On Thursday 03 November 2011 15:59:48, David Smith wrote:
> +                               if (depth == 0) {
> +                                       trace_sched_process_exec(current, bprm);
>                                         ptrace_event(PTRACE_EVENT_EXEC,
>                                                         old_pid);
> +                               }

Won't tracepoints be interested in the old pid as well?  Or does bprm
carry that info?  That was only recently added to the ptrace event,
which probably postdates your original patch.

-- 
Pedro Alves
--
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/