linux-kernel - Re: [PATCH V5 1/3] mm/nobootmem: Fix unused variable

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1401210150220.29987@chino.kir.corp.google.com>
Date:	Tue, 21 Jan 2014 01:51:52 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Philipp Hachtmann <phacht@...ux.vnet.ibm.com>
cc:	akpm@...ux-foundation.org, hannes@...xchg.org, liuj97@...il.com,
	santosh.shilimkar@...com, grygorii.strashko@...com,
	iamjoonsoo.kim@....com, robin.m.holt@...il.com,
	tangchen@...fujitsu.com, yinghai@...nel.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V5 1/3] mm/nobootmem: Fix unused variable

On Tue, 21 Jan 2014, Philipp Hachtmann wrote:

> > Not sure why you don't just do a one line patch:
> > 
> > -	phys_addr_t size;
> > +	phys_addr_t size __maybe_unused;
> > to fix it.
> 
> Just because I did not know that __maybe_unused thing.
> 

-	phys_addr_t size;
+	phys_addr_t size = 0;

would have done the same thing.

The compiler generated code isn't going to change with either of these, so 
we're only talking about how the source code is structured.  If you and 
Andrew believe that adding block scope to something so trivial then that's 
your taste.  Looks ugly to me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/