linux-kernel - [raw v1 0/4] Replace __this_cpu ops with raw_cpu

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: <0000014194309038-3923fc42-2039-45da-b8fa-2df545112405-000000@email.amazonses.com>
Date:	Mon, 7 Oct 2013 18:31:53 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>
Subject: [raw v1 0/4] Replace __this_cpu ops with raw_cpu_ops where necessary

The kernel can detect __this_cpu ops in preemptible contexts after
the preemption check patchset that I posted last week.

Here is a selection of patches to fix false positives caused by
the additional checks. So far I have found no bug. Amazing.
Looks like there was some prior work done to shake these things out?

I ran an upstream kernel using Ubuntu 13.04 + the preempt checking +
the patches below on my desktop and with the following patches no
__this_cpu ops triggered messages. The kernel had the default Ubuntu
desktop configuration (+ CONFIG_PREEMPT + CONFIG_DEBUG_THIS_CPU_OPERATIONS).

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