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] [day] [month] [year] [list]
Date:	Fri, 11 Sep 2015 19:11:29 +0300
From:	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Johannes Berg <johannes@...solutions.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>, adrian.hunter@...el.com,
	Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
	Vince Weaver <vince@...ter.net>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	"H. Peter Anvin" <hpa@...or.com>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH v2 0/6] perf: Introduce extended syscall error reporting

Arnaldo Carvalho de Melo <acme@...nel.org> writes:

> Em Wed, Aug 26, 2015 at 07:56:47PM +0300, Alexander Shishkin escreveu:
>> So I hacked stuff a bit [1] to accomodate some of the above
>> ideas. The below diff shows how these ideas integrate with perf. The
>> rest is in my github tree.
>> 
>>  - this exterr implementation allows its users to add arbitrary
>>  information to the  call site structures and also pretty print them on
>>  the way out; in the example, perf stores perf_event_attr field name
>>  that is the source of trouble; it's a string rather than offsetof(),
>>  because half of our event attribute is a bit field;
>>  - the "way out" doesn't have to be syscall return path (although in the
>>  example it is);
>>  - userspace can fetch the extended error reports via prctl() like you
>>  suggested above;
>>  - error codes are still passed around in the [-EXT_ERRNO..-MAX_ERRNO]
>>  range until they are passed to userspace (which is where ext_err_code()
>>  converts them back to traditional errno.h values).
>
> Hey, can we see the builtin-record.c patch please?

Should be on the way to your inbox.

Cheers,
--
Alex
--
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