linux-kernel - Re: [PATCH v2 2/2] perf: Add error message for EMFILE

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: <4F274679.4010402@gmail.com>
Date:	Tue, 31 Jan 2012 10:40:09 +0900
From:	Namhyung Kim <namhyung@...il.com>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
CC:	Namhyung Kim <namhyung.kim@....com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org, David Ahern <dsahern@...il.com>
Subject: Re: [PATCH v2 2/2] perf: Add error message for EMFILE

2012-01-31 10:30 AM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 31, 2012 at 10:15:16AM +0900, Namhyung Kim escreveu:
>> When a user tries to open so many event on multiple tasks/cpus,
>> perf_event_open syscall may fail with EMFILE. Provide an advice
>> for that case.
>
> I'll apply this one, but can you investigate a way to share this error
> handling accross the tools?
>
> A helper routine that doesn't call exit, but returns failure that will
> then cause the tool to decide if it exits or what (TUI ones could
> continue and the user could then select some other operation that would
> work, etc).
>
> It should standardize on ui__warning(), that already takes into account
> if the UI is --stdio or --tui (in the future a GUI too), etc.
>
> Thanks a lot!
>
> - Arnaldo
>

Yep, I'll take a look at it.

Thanks,
Namhyung

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