Hi!
Why doesn't the following code get rejected by pax mprotect?
#include
#include
int main() {
int * a;
a = mmap(NULL, BUFSIZ, PROT_READ | PROT_WRITE | PROT_EXEC, MAP_ANON,
-1, 2);
if (a == MAP_FAILED)
printf("mmap failed\n");
return 0;
}
Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/debug/mi
P src/distrib/sets/lists/modules/mi
P src/distrib/sets/lists/tests/mi
P src/etc/mtree/NetBSD.dist.tests
P src/external/mit/xorg/server/drivers/xf86-video-glint/Makefile
P src/sys/arch/amd64/amd64/locore.S
P
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
dev/audio/t_pad:pad_output
net/npf/t_npf:npf_table
The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2016.12.09.13.06.02 martin src/sys/dev/audio.c,v 1.271
2016.12.09.13.06.41 roy src/sys/kern/kern_module.c,v 1.118
2016.12.09.13.16.22 christos
Mindaugas Rasiukevicius writes:
> I agree that this is not really intuitive and the documentation did
> not clarify this either.
Yes, the documentation should be changed to state that when you
explicitly specify tcp and stateful, you get the s/safr set. Most
importantly, the
On Fri, Dec 09, 2016 at 09:57:50AM +0200, Andreas Gustafsson wrote:
> Yesterday morning, the NetBSD Test Fixture wrote:
> > This is an automatically generated notice of a NetBSD-current/i386
> > build failure.
> > --- audio.o ---
> > cc1: all warnings being treated as errors
> > ***