linux-kernel - Re: [PATCH] tracing/ftrace: use preempt_enable_no_resched_notrace in ring_buffer_time

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: <c62985530812161348g672dd67fm18d256b6ff4334d6@mail.gmail.com>
Date:	Tue, 16 Dec 2008 22:48:01 +0100
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Steven Rostedt" <rostedt@...dmis.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing/ftrace: use preempt_enable_no_resched_notrace in ring_buffer_time_stamp()

2008/12/16 Steven Rostedt <rostedt@...dmis.org>:
>
>
> On Tue, 16 Dec 2008, Fr?d?ric Weisbecker wrote:
>>
>> The hard reboots I've seen are related to x86-64 while
>> disabling/reenabling a CPU through /sys/device/system/cpu
>> No tracer was enabled at these times (the problem still remains with
>> latest updates on -tip for half an hour).
>
> Do you have STACK_TRACER enabled?
>
> -- Steve
>

Yes. Do you think the origin comes from the fact that ftrace is
running with stack tracer?
--
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/