linux-kernel - Re: Interface for enabling context tracking

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: <3ce02a98-0ac2-4d34-b6f7-ba85088399d7@cs.wisc.edu>
Date: Thu, 17 Apr 2025 14:10:53 -0500
From: Junxuan Liao <ljx@...wisc.edu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Frederic Weisbecker <frederic@...nel.org>,
        "Paul E. McKenney" <paulmck@...nel.org>, linux-kernel@...r.kernel.org,
        linux-trace-kernel@...r.kernel.org,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: Interface for enabling context tracking


On 4/10/25 2:05 PM, Steven Rostedt wrote:
> I think the best thing to do is to add trace events in all areas that enter
> and exit the kernel normally (where noinstr is turned off). There's already
> one for page faults on entry. It's been on my todo list to add one for page
> fault exit (as I do care for how long they last.
> 
> I believe the irq vectors also have entry and exits trace events.
> 
> What else is missing?
> 
> -- Steve

Just found out that the exit tracepoints for syscalls aren't always
exactly preceding the exit to userspace. The kernel can still spend
quite some time in task_work_run after the tracepoints are triggered.
Has that bothered you before?

--
Junxuan