linux-kernel - Re: [patch 08/26] posix-timers: Move posix-timer internals to core

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]

Date:   Wed, 31 May 2017 08:37:13 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        John Stultz <john.stultz@...aro.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...nel.org>
Subject: Re: [patch 08/26] posix-timers: Move posix-timer internals to core

On Tue, May 30, 2017 at 11:15:41PM +0200, Thomas Gleixner wrote:
> None of these declarations is required outside of kernel/time. Move them to
> an internal header.

It seems like struct k_clock itself could be marked private as well.

And with a small exported helper for /the /proc/timers implementation
struct k_itimer could be marked private, too.