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: <20120824083545.GA25599@gmail.com>
Date:	Fri, 24 Aug 2012 10:35:46 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	David Ahern <dsahern@...il.com>, Pekka Enberg <penberg@...nel.org>,
	Bernhard Rosenkraenzer <bernhard.rosenkranzer@...aro.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCHv2 1/1] perf: Port to Android


* Matthew Garrett <mjg59@...f.ucam.org> wrote:

> On Thu, Aug 23, 2012 at 03:32:50PM -0600, David Ahern wrote:
> 
> > Why not add support for the missing functions (on_exit, 
> > getsid, psignal and getline) to Bionic instead of perf?
> 
> Many vendors need to target existing Android platforms and 
> don't have the luxury of waiting for code to get through 
> Google review and then land on devices between 6 months in the 
> future and never. The embedded world is dysfunctional in a 
> whole bunch of ways.

and the compat changes don't look overly large, so I guess we 
could do something like this.

Would be nice to make it more robust in case Bionic does add 
these functions? Feature tests and such? perf offering weak 
symbols for some of these methods and the linker sorting it out?

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