linux-kernel - Re: linux-next: build warning after merge of the final tree (driver-core tree related)

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: <20100913085155.6b73c9cc.randy.dunlap@oracle.com>
Date:	Mon, 13 Sep 2010 08:51:55 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Greg KH <greg@...ah.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Thomas Renninger <trenn@...e.de>,
	Jason Baron <jbaron@...hat.com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree
 (driver-core tree related)

On Mon, 6 Sep 2010 19:34:04 -0700 Greg KH wrote:

> On Tue, Sep 07, 2010 at 11:54:26AM +1000, Stephen Rothwell wrote:
> > Hi Greg,
> > 
> > After merging the final tree, today's linux-next build (powerpc
> > allnoconfig) produced this warning:
> > 
> > kernel/params.c: In function 'parse_args':
> > kernel/params.c:233: warning: the frame size of 1032 bytes is larger than 1024 bytes
> > 
> > Introduced by commit 32e6407e9361cd1aac39ff6b744cad48d1802a08 ("Dynamic
> > Debug: Introduce global fake module param module.ddebug") which added a
> > 1024 byte array to the stack ...
> 
> Wierd, why didn't this show up yesterday?  The patch was in that tree
> then, right?
> 
> Thomas, care to fix this up?


ping.  Is Thomas around??

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/