linux-kernel - Re: [PATCH 4/5] tracing: Delete timestamp

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: <CAJncD7S74FPuPvDw=vfmB8zb1LcWhr=evhCNzvHLz+pALu34Cw@mail.gmail.com>
Date:   Wed, 14 Dec 2022 16:43:55 +0800
From:   sunliming <kelulanainsley@...il.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     mingo@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/5] tracing: Delete timestamp_mode trace file

Got it.

Steven Rostedt <rostedt@...dmis.org> 于2022年10月18日周二 21:26写道：
>
> On Tue, 18 Oct 2022 20:00:55 +0800
> sunliming <sunliming@...inos.cn> wrote:
>
> > The timestamp_mode trace file is not necessary duo to the removing of
> > the absolute timestamp.
>
> This is user space exposed API. Which means we do not just simply "remove
> it". This file is the reason I kept the absolute timestamps around in the
> first place. Because user space may want them.
>
> How do you know that user space isn't using this? Is there something else
> you are planning on adding that makes taking the risk we might break user
> space worth while?
>
> -- Steve