linux-kernel - Re: + recordmcount-stfu.patch added to -mm tree

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]

Date:	Sat, 14 Nov 2009 00:33:42 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	lihong.hi@...il.com, LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: + recordmcount-stfu.patch added to -mm tree

On Fri, 2009-11-13 at 21:26 -0800, Andrew Morton wrote:

> Dunno, really.  How many people are running old objdump, and do we want
> to retard the rate at which the stragglers will upgrade?

I guess not, but by printing out a warning 1000000000000000000000000000
times per build, it may encourage them to upgrade ;-)

> 
> I tend to be a late adopter ;) (for legit reasons, really - to catch
> things like this) so I'd be OK carrying that patch locally.
> 
> 
> Emitting that warning 1000000000000000000000000000 times per build is a
> bit obnoxious.  Maybe find some way to restrict it to once per `make'?
> 

I was originally going to do that, but then realized that he given patch
was easier to implement. I guess I can make a temp file that gets
deleted at the start of the build, and created the first time the
warning appears. Then the existence of that file will prevent other
warnings.

I'll play with this on Monday (if I remember ;-)

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