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]
Date:	Wed, 18 Jan 2012 10:39:44 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Oleg Nesterov <oleg@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...hat.com>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Seiji Aguchi <saguchi@...hat.com>,
	linux-kernel@...r.kernel.org,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Subject: Re: [GIT PULL] tracing: make signal tracepoints more useful


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Mon, Jan 16, 2012 at 7:10 AM, Oleg Nesterov <oleg@...hat.com> wrote:
> >
> > But do we really need to keep the old tracepoint? IOW, what 
> > if we simply rename it and add more info?
> 
> Quite frankly, unless somebody can point to something that 
> breaks, I'd rather just change the existing one.
> 
> Nobody outside of a few special cases uses tracepoints. 
> *nobody*.  The only apps I have ever seen that matters to 
> anybody ends up being latencytop and powertop. If those two 
> have been tested and don't care, I don't think we should care.

Correct. (There's also sysprof and perf - both should be fine.)

As i said in my very first mail:

> [...] Which apps/tools rely on the old tracepoint? If it's 
> exactly zero apps then we might be able to change it, but this 
> needs to be investigated.

I resisted Steve's "this ABI change is safe by design" notion 
which is somewhat of a disease. It is probably fine but not by 
definition.

Thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ