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: <1495814982.29207.35.camel@perches.com>
Date:   Fri, 26 May 2017 09:09:42 -0700
From:   Joe Perches <joe@...ches.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Christoph Hellwig <hch@....de>,
        Dimitri Sivanich <sivanich@....com>,
        Mike Travis <mike.travis@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] kernel: mark all struct k_clock instances const

On Fri, 2017-05-26 at 12:32 +0200, Thomas Gleixner wrote:
> On Fri, 26 May 2017, Joe Perches wrote:
> > On Fri, 2017-05-26 at 12:03 +0300, Christoph Hellwig wrote:
> > > And initialize the array statically at compile time.   Originally
> > > based on changes in the Grsecurity patch set, but redone for mainline
> > > to be slightly cleaner, and take the SGI mmtimer removal into account,
> > > which allows for a completely static initialization.
> > 
> > Maybe add k_clock to scripts/const_structs.checkpatch
> Care to send a proper patch with changelog?

After Christoph's patch is in -next so I can reference
the proper commit SHA1.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ