linux-kernel - Re: [PATCH v2 1/1] ftrace: do not update max buffer with no users

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: <alpine.DEB.1.10.0811130815080.7458@gandalf.stny.rr.com>
Date:	Thu, 13 Nov 2008 08:16:34 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Pekka Paalanen <pq@....fi>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH v2 1/1] ftrace: do not update max buffer with no users


On Thu, 13 Nov 2008, Steven Rostedt wrote:
> > > Reported-by: Pekka Paalanen <pq@....fi>
> > > Signed-off-by: Steven Rostedt <srostedt@...hat.com>
> > > ---
> > >  kernel/trace/trace.c |  171 ++++++++++++++++++++++++++------------------------
> > >  1 files changed, 88 insertions(+), 83 deletions(-)
> > 
> > This is _way_ too much churn for .28, we need a much simpler solution.
> 
> The line count is very misleading. The 83 insertions and deletions where 
> moved code or indentation:
> 

> 
> As you can easily see, the change only added the test for max_tr.buffer
> exists, and indented the rest.
> 
> The other parts you can easily see that they are not changed.
> But, we could separate out the moved code and ifdef protection for 29, 
> even though I feel nervous that some config might use them, and break at 
> runtime. This change will break the compile if it happens. Without the 
> change, we find out at runtime :-(

Also, if you are worried about line count, I could just leave the code in 
place, and add more ifdefs around them, and leave the consolidation of the 
code for 29.

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