linux-kernel - [PATCH v2 0/2] bus: CCN/CCI: Fix use of smp_processor

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: <20171003171413.18592-1-marc.zyngier@arm.com>
Date:   Tue,  3 Oct 2017 18:14:11 +0100
From:   Marc Zyngier <marc.zyngier@....com>
To:     Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Suzuki K Poulose <suzuki.poulose@....com>,
        Pawel Moll <pawel.moll@....com>,
        Mark Rutland <mark.rutland@....com>
Cc:     linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] bus: CCN/CCI: Fix use of smp_processor_id()

I've just noticed that both the CCI and CCN drivers have a small
buglet in that they call smp_processor_id() from preemptible context,
which is frown upon (having just booted a 4.13 kernel with
DEBUG_PREEMPT on my Seattle, I was surprised to be greeted with a nice
backtrace...).

I've tested the CCN patch on the same Seatle box, but I've only
compile-tested the equivalent CCI patch (which is obviously correct --
famous last words...).

Thanks,

	M.

* From v1: Keep the current CPU refcount until we have registered the
  CPU notifiers, making sure we don't race against a surprise hotplug
  off.

Marc Zyngier (2):
  bus: arm-ccn: Fix use of smp_processor_id() in preemptible context
  bus: arm-cci: Fix use of smp_processor_id() in preemptible context

 drivers/bus/arm-cci.c | 7 +++++--
 drivers/bus/arm-ccn.c | 4 +++-
 2 files changed, 8 insertions(+), 3 deletions(-)

-- 
2.11.0