linux-kernel - Re: [PATCH 1/4] kernel: local_irq_{save,restore}

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: <20100604050347.GE31868@linux-sh.org>
Date:	Fri, 4 Jun 2010 14:03:47 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	David Miller <davem@...emloft.net>
Cc:	peterz@...radead.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, sparclinux@...r.kernel.org
Subject: Re: [PATCH 1/4] kernel: local_irq_{save,restore}_nmi()

On Fri, Apr 09, 2010 at 04:01:35PM -0700, David Miller wrote:
> 
> Provide local_irq_{save,restore}_nmi() which will allow us to help
> architectures that implement NMIs using IRQ priorities like SPARC64
> does.
> 
> Sparc uses IRQ prio 15 for NMIs and implements local_irq_disable() as
> disable <= 14. However if you do that while inside an NMI you re-
> enable the NMI priority again, causing all kinds of fun.
> 
> A more solid implementation would first check the disable level and
> never lower it, however that is more costly and would slow down the
> rest of the kernel for no particular reason.
> 
> Therefore introduce local_irq_save_nmi() which can implement this
> slower but more solid scheme and dis-allow local_irq_save() from NMI
> context.
> 
> Suggested-by: David Miller <davem@...emloft.net>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> Signed-off-by: David S. Miller <davem@...emloft.net>

Are there any updates for this patch series? I would like to make use of
this on SH as well, but it seems these haven't hit upstream yet.
--
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/