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-next>] [day] [month] [year] [list]
Message-Id: <1450285686-844-1-git-send-email-daniel.thompson@linaro.org>
Date:	Wed, 16 Dec 2015 17:08:04 +0000
From:	Daniel Thompson <daniel.thompson@...aro.org>
To:	Russell King <linux@....linux.org.uk>
Cc:	Daniel Thompson <daniel.thompson@...aro.org>,
	Marc Zyngier <marc.zyngier@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jason Cooper <jason@...edaemon.net>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	patches@...aro.org, linaro-kernel@...ts.linaro.org
Subject: [PATCH 0/2] Fix NMI backtrace for Inforce IFC6410

After spotting some problems with the SysRq-L on Inforce IFC6410 I ran
some tests (see patch 2) and concluded that certain SGI IDs cannot be
used by Linux on these platforms because they have been reserved for use
by the secure world.

This patchset includes both a patch to resolve the problem on Inforce
IFC6410 and a patch to detect and report reserved SGI IDs during boot.
The patch (deliberately) keeps quiet on platforms where the kernel's
world is not subject to any restrictions.


Daniel Thompson (2):
  arm: Fix "NMI" backtrace for Inforce IFC6410
  irqchip/gic: Identify and report any reserved SGI IDs

 arch/arm/kernel/smp.c     |  3 ++-
 drivers/irqchip/irq-gic.c | 53 +++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 55 insertions(+), 1 deletion(-)

--
2.5.0

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ