linux-kernel - Re: [patch 11/11] sparc/irqs: Do not trace arch_local_{*,irq

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1309870146.26417.168.camel@gandalf.stny.rr.com>
Date:	Tue, 05 Jul 2011 08:49:06 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	David Miller <davem@...emloft.net>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [patch 11/11] sparc/irqs: Do not trace arch_local_{*,irq_*}
 functions

On Fri, 2011-07-01 at 21:11 -0700, David Miller wrote:
> From: Steven Rostedt <rostedt@...dmis.org>
> Date: Fri, 01 Jul 2011 23:04:46 -0400
> 
> > From: Steven Rostedt <srostedt@...hat.com>
> > 
> > Do not trace arch_local_save_flags(), arch_local_irq_*() and friends.
> > Although they are marked inline, gcc may still make a function out of
> > them and add it to the pool of functions that are traced by the function
> > tracer. This can cause undesirable results (kernel panic, triple faults,
> > etc).
> > 
> > Add the notrace notation to prevent them from ever being traced.
> > 
> > Cc: "David S. Miller" <davem@...emloft.net>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> 
> Acked-by: David S. Miller <davem@...emloft.net>

Thanks David!

Could you pull the patch into your tree. It's not dependent on any other
patch, so I feel more comfortable that it goes through yours than the
tracing tree.

Thanks,

-- Steve


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