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: <CAErzpms1mGeBw364qsX1YV_4=4sPhMhTRsWsjHZmH8Ro5xWoyQ@mail.gmail.com>
Date: Wed, 9 Oct 2024 22:01:51 +0800
From: Donglin Peng <dolinux.peng@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: mhiramat@...nel.org, mark.rutland@....com, mathieu.desnoyers@...icios.com, 
	linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v2 RESEND] function_graph: Support recording and printing
 the function return address

On Wed, Oct 9, 2024 at 9:37 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Wed,  9 Oct 2024 11:03:40 +0800
> Donglin Peng <dolinux.peng@...il.com> wrote:
>
> > From: Donglin Peng <pengdonglin@...omi.com>
> >
> > When using function_graph tracer to analyze the flow of kernel function
> > execution, it is often necessary to quickly locate the exact line of code
> > where the call occurs. While this may be easy at times, it can be more
> > time-consuming when some functions are inlined or the flow is too long.
> >
> > This feature aims to simplify the process by recording the return address
> > of traced funcions and printing it when outputing trace logs.
> >
> > To enhance human readability, the prefix 'ret=' is used for the kernel return
> > value, while '<-' serves as the prefix for the return address in trace logs to
> > make it look more like the function tracer.
> >
> > A new trace option named 'funcgraph-retaddr' has been introduced, and the
> > existing option 'sym-addr' can be used to control the format of the return
> > address.
> >
>
> Is there a reason for the resend? I already have it in my for-next branch.

I'm sorry and I did not notice it.

>
> -- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ