linux-kernel - Re: linux-next: build failure after merge of the final tree (akpm 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20130304092244.GB17223@quack.suse.cz>
Date:	Mon, 4 Mar 2013 10:22:44 +0100
From:	Jan Kara <jack@...e.cz>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jan Kara <jack@...e.cz>
Subject: Re: linux-next: build failure after merge of the final tree (akpm
 tree related)

On Mon 04-03-13 14:28:21, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the final tree, today's linux-next build (arm defconfig)
> failed like this:
> 
> kernel/built-in.o: In function `console_unlock':
> cpu_pm.c:(.text+0x4418): undefined reference to `__bad_udelay'
> 
> Caused by commit 4df7323a125f ("printk: avoid softlockups in
> console_unlock()") which added
> 
> 	ndelay(max_interrupt_disabled_duration() / 2);
> 
> to console_unlock() which can be a 2.5 second delay ... and the maximum
> delayed allowed by udelay (at least in this build) is 2ms.
  Bah, one always learns. Didn't know there's some max limit on ndelay().
I'll replace that with a while loop or something like that. Thanks for
report!

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/