linux-kernel - Re: [PATCH, RESEND] regulator: core: fix regulator_lock

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]

Date:	Tue, 01 Dec 2015 14:21:45 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Mark Brown <broonie@...nel.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Sascha Hauer <s.hauer@...gutronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Ingo Molnar <mingo@...nel.org>, tyler.baker@...aro.org,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH, RESEND] regulator: core: fix regulator_lock_supply regression

On Tuesday 01 December 2015 13:16:39 Mark Brown wrote:
> On Fri, Nov 27, 2015 at 02:46:41PM +0100, Arnd Bergmann wrote:
> > As noticed by Geert Uytterhoeven, my patch to avoid a harmless build warning
> > in regulator_lock_supply() was total crap and introduced a real bug:
> 
> I'm going to drop both this and the commit it's fixing for now as this
> is causing boot failures on several boards (none of which I have sadly)
> in -next:
> 
>   http://kernelci.org/boot/all/job/broonie-regulator/kernel/v4.4-rc3-17-ga6498dba8869/
> 
> which were bisected by Tyler to this:
> 
>   http://hastebin.com/noluripepa.sm
> 
> I'm not seeing anything obvious in the code at the minute having looked
> for several seconds, I'll have a proper look later today all being well.
> 

Ok, sorry about the double screwup and thanks for looking into it.

	Arnd
--
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/