linux-kernel - perf: aux buffer and mmaping PROT

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

Message-ID: <alpine.DEB.2.20.1506041625210.30580@vincent-weaver-1.umelst.maine.edu>
Date:	Thu, 4 Jun 2015 16:29:15 -0400 (EDT)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Stephane Eranian <eranian@...gle.com>
Subject: perf: aux buffer and mmaping PROT_WRITE

So I came across this issue when improving mmap() support in the 
perf_fuzzer.

For AUX buffers, you can specify PROT_WRITE when allocating the buffer 
using mmap(), and it will return a buffer just fine, but if you actually 
try to write anything you get an instant SIGBUS.

Is this expected behavior?  It seems like we should fail the initial 
allocation if we ask for a writable buffer but it is not writable.

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/