linux-kernel - Re: [PATCH RFC] Make call_srcu() available during very early boot

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: <20180814143451.0ee99bf8@gandalf.local.home>
Date:   Tue, 14 Aug 2018 14:34:51 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:     joel@...lfernandes.org, mathieu.desnoyers@...icios.com,
        peterz@...radead.org, tj@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] Make call_srcu() available during very early boot

On Tue, 14 Aug 2018 10:44:43 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:

> > > If I recall correctly, this subterfuge suppresses compiler complaints
> > > about initializing an unsigned long with a negative number.  :-/  
> > 
> > Did you try:
> > 
> > 	.srcu_gp_seq_needed = -1UL,
> > 
> > ?  
> 
> Works for my compiler, not sure what set of complaints pushed me in that
> direction.

I've used -1UL for unsigned long initializations for pretty much my
entire programming career. I've never had any issues with it.

-- Steve