linux-kernel - Re: perf error codes

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]

Message-ID: <alpine.DEB.2.00.1107120959450.24091@cl320.eecs.utk.edu>
Date:	Tue, 12 Jul 2011 10:03:51 -0400 (EDT)
From:	Vince Weaver <vweaver1@...s.utk.edu>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	Stephane Eranian <eranian@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, paulus <paulus@...ba.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: perf error codes

On Tue, 12 Jul 2011, Peter Zijlstra wrote:

> Linus recently expressed dislike of our -ENOSPC usage for indicating the
> pmu is 'full'. Do either of your projects (libpfm, libpapi resp.) rely
> on this particular error code for this condition?

PAPI doesn't have any code that relies on ENOSPC.

I have to agree with Linus, when I was working on some validation tests 
and had the buffer size wrong it was very confusing when strerror() told
me the problem was "No space left of device" when none of my disks were 
full.  It took me a while (and some grepping of the kernel source) to 
figure out what was going on.

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