linux-kernel - [PATCH 0/3] perf: builtin-record: Be more helpful when running up against mlock limits.

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-next>] [day] [month] [year] [list]

Message-Id: <1324301972-22740-1-git-send-email-nelhage@nelhage.com>
Date:	Mon, 19 Dec 2011 08:39:29 -0500
From:	Nelson Elhage <nelhage@...hage.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] perf: builtin-record: Be more helpful when running up against mlock limits.

With the current code, it's relatively easy to run up against the
perf_event_mlock_kb limit if you try to attach to a multithreaded
target with 'perf record -p', because perf will attempt to mmap 512k
per target thread, and the default mlock limit is (512k + 1 page),
total.

Current, this results in a completely inscrutable
  Fatal: failed to mmap with 22 (Invalid argument)

We should perhaps automatically detect a better choice of mmap_pages,
but in the meanwhile, it's easy to improve the error to give users
some guidance about what's going on, so that hopefully I can be the
last person to have to source-dive to figure out what's going on.

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