linux-kernel - Re: [PATCH] ftrace: handle archs that do not support irqs_disabled

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: <c62985530810240654o3e58a0abt12221507855be005@mail.gmail.com>
Date:	Fri, 24 Oct 2008 15:54:40 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Steven Rostedt" <rostedt@...dmis.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Alexey Dobriyan" <adobriyan@...il.com>,
	"Geert Uytterhoeven" <geert@...ux-m68k.org>,
	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [PATCH] ftrace: handle archs that do not support irqs_disabled_flags

2008/10/24 Steven Rostedt <rostedt@...dmis.org>:
> This patch adds a 'X' in the output to let the user know that the
> architecture they are running on does not support a way for the tracer
> to determine if interrupts were enabled or disabled. It also lets those
> same archs compile with tracing enabled.

That's almost exactly what I thought to repair the warning caused by those
FLAG_IRQS_NOSUPPORT archs :)

So we have now all the three patches that correct the warning reported
by Alexey in
Linux-next: http://lkml.org/lkml/2008/10/23/145
--
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/