linux-kernel - Re: [PATCH 7/9] perf sched replay: Fix the EMFILE error caused by the limitation of the maximum open files

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]

Message-ID: <55240A96.3070100@gmail.com>
Date:	Tue, 07 Apr 2015 10:49:26 -0600
From:	David Ahern <dsahern@...il.com>
To:	Yunlong Song <yunlong.song@...wei.com>, a.p.zijlstra@...llo.nl,
	paulus@...ba.org, mingo@...hat.com, acme@...nel.org
CC:	linux-kernel@...r.kernel.org, wangnan0@...wei.com
Subject: Re: [PATCH 7/9] perf sched replay: Fix the EMFILE error caused by
 the limitation of the maximum open files

On 3/31/15 7:46 AM, Yunlong Song wrote:
> ---
>   tools/perf/builtin-sched.c | 31 ++++++++++++++++++++++++++-----
>   1 file changed, 26 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/builtin-sched.c b/tools/perf/builtin-sched.c
> index 3261300..5ab58c6 100644
> --- a/tools/perf/builtin-sched.c
> +++ b/tools/perf/builtin-sched.c

...

> @@ -1700,6 +1720,7 @@ int cmd_sched(int argc, const char **argv, const char *prefix __maybe_unused)
>   		    "be more verbose (show symbol address, etc)"),
>   	OPT_BOOLEAN('D', "dump-raw-trace", &dump_trace,
>   		    "dump raw trace in ASCII"),
> +	OPT_BOOLEAN('f', "force", &sched.force, "don't complain, do it"),
>   	OPT_END()
>   	};
>   	const struct option sched_options[] = {
>

Please update the documenation with this new option, 
tools/perf/Documentation/perf-sched.txt
--
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/