linux-kernel - [PATCH 0/3] preempt: Fix tracing crash

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: <1433432349-1021-1-git-send-email-fweisbec@gmail.com>
Date:	Thu,  4 Jun 2015 17:39:06 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: [PATCH 0/3] preempt: Fix tracing crash

This is a proposition to fix the function graph tracer crashes reported
by Fengguang Wu's 0-day testing.

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
	sched/core

HEAD: 723d604e2c185b94c6890c26dab9c72e4243711b

Thanks,
	Frederic
---

Frederic Weisbecker (3):
      sched: Make preempt_schedule_context() function-tracing safe
      preempt: Use preempt_schedule_context() as the official tracing preemption point
      preempt: Reorganize a bit the notrace declensions


 arch/x86/include/asm/preempt.h   |  8 +++-----
 arch/x86/kernel/i386_ksyms_32.c  |  4 +---
 arch/x86/kernel/x8664_ksyms_64.c |  4 +---
 arch/x86/lib/thunk_32.S          |  4 +---
 arch/x86/lib/thunk_64.S          |  4 +---
 include/asm-generic/preempt.h    |  7 ++-----
 include/linux/preempt.h          | 36 +++++++++++++++---------------------
 kernel/sched/core.c              | 19 ++++++++++++-------
 8 files changed, 36 insertions(+), 50 deletions(-)
--
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/