linux-kernel - Re: [PATCH] kernel: mark all struct k

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: <20170523070450.GA17926@lst.de>
Date:   Tue, 23 May 2017 09:04:50 +0200
From:   Christoph Hellwig <hch@....de>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel: mark all struct k_clock instances const

On Tue, May 23, 2017 at 09:01:14AM +0200, Thomas Gleixner wrote:
> > We can require the driver to be built into the kernel, which seems pretty
> > reasonable for a timer.  It's only selectable on IA64 anyway.
> 
> That still requires that we "register" the clock as it's SN2 specific and
> we don't want to end up with a non initialized clock ....

I'd much rather have a call to mmtimer_init from the core clock
code than having to conditionally export the array..

But maybe we can actually drop the mmtimer now - IA64-based Altix
systems haven't been built for a while and anyone requiring its
special clock will run a distro of sorts anyway.