linux-kernel - Re: [PATCH v2] locking: Fix copy/paste errors "ARCH_INLINE_*_UNLOCK

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: <20130517101824.GA5162@dyad.programming.kicks-ass.net>
Date:	Fri, 17 May 2013 12:18:24 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux390@...ibm.com, linux-s390@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] locking: Fix copy/paste errors
 "ARCH_INLINE_*_UNLOCK_BH"

On Fri, May 17, 2013 at 10:51:33AM +0200, Paul Bolle wrote:
> The Kconfig symbols ARCH_INLINE_READ_UNLOCK_IRQ,
> ARCH_INLINE_SPIN_UNLOCK_IRQ, and ARCH_INLINE_WRITE_UNLOCK_IRQ were added
> in v2.6.33, but have never actually been used. Ingo Molnar spotted that
> this is caused by three identical copy/paste erros. Eg, the Kconfig
> entry for
>          INLINE_READ_UNLOCK_IRQ
> 
> has an (optional) dependency on
>     ARCH_INLINE_READ_UNLOCK_BH
> 
> were it apparently should depend on
>     ARCH_INLINE_READ_UNLOCK_IRQ
> 
> instead. Likewise for the Kconfig entries for INLINE_SPIN_UNLOCK_IRQ and
> INLINE_WRITE_UNLOCK_IRQ. Fix these three errors.
> 
> Reported-by: Ingo Molnar <mingo@...nel.org>
> Signed-off-by: Paul Bolle <pebolle@...cali.nl>

Thanks!
--
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/