daily CVS update output

2017-04-21 Thread NetBSD source update 

Updating src tree:
P src/bin/ln/ln.c
P src/distrib/sets/mkvars.mk
P src/doc/3RDPARTY
P src/external/bsd/pkg_install/sbin/Makefile.inc
P src/lib/libc/sys/_lwp_create.2
P src/lib/libedit/filecomplete.c
P src/lib/libedit/filecomplete.h
P src/lib/libedit/readline.c
P src/sbin/fsck_ext2fs/pass1.c
P src/share/man/man7/symlink.7
P src/sys/arch/arm/nvidia/files.tegra
P src/sys/arch/arm/nvidia/tegra_mc.c
P src/sys/arch/arm/nvidia/tegra_reg.h
P src/sys/arch/arm/nvidia/tegra_var.h
P src/sys/arch/evbarm/conf/TEGRA
P src/sys/arch/evbarm/ifpga/ifpga_pci.c
P src/sys/arch/evbarm/tegra/tegra_machdep.c
P src/sys/arch/evbarm/tegra/tegra_start.S
P src/sys/compat/linux/common/linux_sched.c
P src/sys/compat/netbsd32/netbsd32_lwp.c
P src/sys/dev/fdt/fdt_subr.c
P src/sys/dev/fdt/fdtvar.h
P src/sys/dev/fdt/fixedclock.c
P src/sys/dev/pci/pci_subr.c
P src/sys/dev/pci/pcireg.h
P src/sys/dev/usb/uipad.c
P src/sys/kern/exec_elf.c
P src/sys/kern/kern_exec.c
P src/sys/kern/kern_fork.c
P src/sys/kern/kern_kthread.c
P src/sys/kern/kern_lwp.c
P src/sys/kern/kern_sig.c
P src/sys/kern/sys_aio.c
P src/sys/kern/sys_lwp.c
P src/sys/netipsec/ipsec.c
P src/sys/netipsec/keysock.c
P src/sys/rump/librump/rumpkern/threads.c
P src/sys/sys/lwp.h
P src/sys/sys/signal.h
P src/usr.bin/make/str.c
P src/usr.bin/make/unit-tests/modmatch.exp
P src/usr.bin/make/unit-tests/modmatch.mk
P src/usr.bin/unzip/Makefile
P src/usr.sbin/makemandb/Makefile

Updating xsrc tree:


Killing core files:


Updating tar files:
src/top-level: collecting... replacing... done
src/bin: collecting... replacing... done
src/common: collecting... replacing... done
src/compat: collecting... replacing... done
src/crypto: collecting... replacing... done
src/dist: collecting... replacing... done
src/distrib: collecting... replacing... done
src/doc: collecting... replacing... done
src/etc: collecting... replacing... done
src/external: collecting... replacing... done
src/extsrc: collecting... replacing... done
src/games: collecting... replacing... done
src/gnu: collecting...pax: Unable to access src/gnu (No such file or directory)
pax: WARNING! These file names were not selected:
src/gnu
 done
src/include: collecting... replacing... done
src/lib: collecting... replacing... done
src/libexec: collecting... replacing... done
src/regress: collecting... replacing... done
src/rescue: collecting... replacing... done
src/sbin: collecting... replacing... done
src/share: collecting... replacing... done
src/sys: collecting... replacing... done
src/tests: collecting... replacing... done
src/tools: collecting... replacing... done
src/usr.bin: collecting... replacing... done
src/usr.sbin: collecting... replacing... done
src/config: collecting... replacing... done
src: collecting... replacing... done
xsrc/top-level: collecting... replacing... done
xsrc/external: collecting... replacing... done
xsrc/local: collecting... replacing... done
xsrc: collecting... replacing... done

Running the SUP scanner:
SUP Scan for current starting at Sat Apr 22 03:07:32 2017
SUP Scan for current completed at Sat Apr 22 03:07:48 2017
SUP Scan for mirror starting at Sat Apr 22 03:07:48 2017
SUP Scan for mirror completed at Sat Apr 22 03:10:27 2017



Updating release-6 src tree (netbsd-6):

Updating release-6 xsrc tree (netbsd-6):


Updating release-6 tar files:
src/top-level: collecting... replacing... done
src/bin: collecting... replacing... done
src/common: collecting... replacing... done
src/compat: collecting... replacing... done
src/crypto: collecting... replacing... done
src/dist: collecting... replacing... done
src/distrib: collecting... replacing... done
src/doc: collecting... replacing... done
src/etc: collecting... replacing... done
src/external: collecting... replacing... done
src/extsrc: collecting... replacing... done
src/games: collecting... replacing... done
src/gnu: collecting... replacing... done
src/include: collecting... replacing... done
src/lib: collecting... replacing... done
src/libexec: collecting... replacing... done
src/regress: collecting... replacing... done
src/rescue: collecting... replacing... done
src/sbin: collecting... replacing... done
src/share: collecting... replacing... done
src/sys: collecting... replacing... done
src/tests: collecting... replacing... done
src/tools: collecting... replacing... done
src/usr.bin: collecting... replacing... done
src/usr.sbin: collecting... replacing... done
src/config: collecting... replacing... done
src/x11: collecting... replacing... done
xsrc/top-level: collecting... replacing... done
xsrc/external: collecting... replacing... done
xsrc/local: collecting... replacing... done
xsrc/xfree: collecting... replacing... done

Running the SUP scanner:
SUP Scan for release-6 starting at Sat Apr 22 03:15:38 2017
SUP Scan for release-6 completed at Sat Apr 22 03:15:48 2017



Updating release-7 src tree (netbsd-7):
P bin/sh/expand.c
P doc/3RDPARTY
U doc/CHANGES-7.2
P external/bsd/bind/dist/CHANGES
P external/bsd/bind/dist/COPYRIGHT
P external/bsd/bind/dist/README
P

Automated report: NetBSD-current/i386 build failure

2017-04-21 Thread NetBSD Test Fixture 
This is an automatically generated notice of a NetBSD-current/i386
build failure.

The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2017.04.21.23.49.17.

An extract from the build.sh output follows:

unzip.c:(.text.startup+0xb14): undefined reference to 
`archive_read_data_skip'
unzip.c:(.text.startup+0xb24): undefined reference to `archive_error_string'
unzip.c:(.text.startup+0xbb2): undefined reference to `archive_entry_mode'
unzip.c:(.text.startup+0xc49): undefined reference to 
`archive_read_data_skip'
unzip.c:(.text.startup+0xcf6): undefined reference to 
`archive_entry_hardlink'
collect2: error: ld returned 1 exit status
*** [unzip] Error code 1
nbmake[7]: stopped in 
/tmp/bracket/build/2017.04.21.23.49.17-i386/src/usr.bin/unzip
1 error

The following commits were made between the last successful build and
the failed build:

2017.04.21.23.06.18 christos src/usr.bin/unzip/Makefile,v 1.3
2017.04.21.23.07.45 christos src/usr.sbin/makemandb/Makefile,v 1.7
2017.04.21.23.35.01 jmcneill src/sys/dev/fdt/fdt_subr.c,v 1.8
2017.04.21.23.35.01 jmcneill src/sys/dev/fdt/fdtvar.h,v 1.10
2017.04.21.23.35.29 jmcneill src/sys/arch/arm/nvidia/files.tegra,v 1.31
2017.04.21.23.36.57 jmcneill src/sys/arch/evbarm/conf/TEGRA,v 1.15
2017.04.21.23.36.58 jmcneill src/sys/arch/evbarm/tegra/tegra_machdep.c,v 
1.40
2017.04.21.23.36.58 jmcneill src/sys/arch/evbarm/tegra/tegra_start.S,v 1.10
2017.04.21.23.49.17 christos src/usr.bin/unzip/Makefile,v 1.4

Log files can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2017.04.html#2017.04.21.23.49.17

Re: npf lock issue?

2017-04-21 Thread Anthony Mallet 
On Friday 21 Apr 2017, at 22:15, Mindaugas Rasiukevicius wrote:
| > #11 0x804b3075 in panic (
| > fmt=fmt@entry=0x806b6790 "uvm_km_check_empty: va %p
| > has pa 0x%llx") at /usr/src/sys/kern/subr_prf.c:258
| > #12 0x8044ed05 in uvm_km_check_empty (
| > map=map@entry=0x8081c780 ,
| > start=, end=18446744071572586496) at
| > /usr/src/sys/uvm/uvm_km.c:563
| > #13 0x8045268f in uvm_map (
| > map=map@entry=0x8081c780 ,
| > startp=startp@entry=0xfe80cc383918, size=size@entry=65536,
| > uobj=, uoffset=uoffset@entry=-1,
| > align=, flags=,
| > flags@entry=5927) at /usr/src/sys/uvm/uvm_map.c:1096
| > #14 0x8044ee4f in uvm_km_alloc (
| > map=0x8081c780 ,
| > size=size@entry=65536, align=align@entry=4096,
| > flags=flags@entry=49) at /usr/src/sys/uvm/uvm_km.c:621
| > #15 0x80240a4d in alloc_chunk (size=65536)
| > at
| > /usr/src/sys/external/bsd/sljit/dist/sljit_src/sljitExecAllocator.c:110
| > #16 sljit_malloc_exec (size=)
| > at
| > /usr/src/sys/external/bsd/sljit/dist/sljit_src/sljitExecAllocator.c:221
| > 221 header = (struct block_header*)alloc_chunk(chunk_size);
| >
| > Does this ring a bell to anyone?
|
| This looks like a bug in sljit rather than NPF per se.  The panic
| message suggests some kind of KVA leak.  I suspect it might be a
| result of e.g. a free_chunk() call with an incorrect size in the
| sljitExecAllocator.c code.

Yes. npf does not seem to be involed at all. I kept the same message
subject for consistency but I guess a new thread should be started.

Actually, sljit does not seem involed either. After my post, I noticed
that anything that tries to uvm_km_alloc() from module_map has the
same failure. On the failing machine, options MODULAR is used but I
have no modules. So npf happens to be the first piece of code
allocating memory from module_map (sljit actually). But, for instance,
a modload(1) right after boot also fails in exactly the same way.

The page that uvm_km_check_empty() finds already mapped is the very
first one of module_map. I checked the latest commits in uvm since
January without noticing anything suspect (and I don't have
UVM_HOTPLUG defined either). But my knowledge of uvm is
nearly zero ... so I did not really progress on this.

Re: Packages crashing on -current

2017-04-21 Thread Michael 
Hello,

On Fri, 21 Apr 2017 16:34:33 +
co...@sdf.org wrote:

> Hi,
> 
> mprotect (and ASLR) are security measures that not all pkgsrc packages
> can survive, so some packages had NOT_PAX_MPROTECT_SAFE set for some
> binaries, to disable it.
> 
> However the condition for using NOT_PAX_MPROTECT_SAFE was incorrectly
> only done for NetBSD/amd64.
> 
> The outcome should've been things like (only on -current, stable is
> unaffected as it doesn't have pax mprotect enabled):
> - Firefox crashes
> - Libreoffice segfaults during build
> etc.

Midori ( and likely everything else using webkit ) has a similar problem
- it doesn't crash, but javascript doesn't work until all the mprotect
stuff is disabled.

have fun
Michael

Re: npf lock issue?

2017-04-21 Thread Mindaugas Rasiukevicius 
Anthony Mallet  | Trying to upgrade from 7.99.44 to today's -current, I have a panic
> | right away when starting npf. The boot with npf disabled is fine (see
> | note below), then when manually running `npfctl reload` the machine
> | reboots right aways with absolutely no diagnostic. This is an issue
> | that I experiencing consistently since something like last January or
> | so.
> 
> I got a useful backtrace, it's actually failing in sljit:
> 
> #11 0x804b3075 in panic (
> fmt=fmt@entry=0x806b6790 "uvm_km_check_empty: va %p has pa 
> 0x%llx")
> at /usr/src/sys/kern/subr_prf.c:258
> #12 0x8044ed05 in uvm_km_check_empty (
> map=map@entry=0x8081c780 , 
> start=, end=18446744071572586496)
> at /usr/src/sys/uvm/uvm_km.c:563
> #13 0x8045268f in uvm_map (
> map=map@entry=0x8081c780 , 
> startp=startp@entry=0xfe80cc383918, size=size@entry=65536, 
> uobj=, uoffset=uoffset@entry=-1, align=, 
> flags=, flags@entry=5927) at 
> /usr/src/sys/uvm/uvm_map.c:1096
> #14 0x8044ee4f in uvm_km_alloc (
> map=0x8081c780 , size=size@entry=65536, 
> align=align@entry=4096, flags=flags@entry=49)
> at /usr/src/sys/uvm/uvm_km.c:621
> #15 0x80240a4d in alloc_chunk (size=65536)
> at /usr/src/sys/external/bsd/sljit/dist/sljit_src/sljitExecAllocator.c:110
> #16 sljit_malloc_exec (size=)
> at /usr/src/sys/external/bsd/sljit/dist/sljit_src/sljitExecAllocator.c:221
> 221 header = (struct block_header*)alloc_chunk(chunk_size);
> 
> Does this ring a bell to anyone?

This looks like a bug in sljit rather than NPF per se.  The panic message
suggests some kind of KVA leak.  I suspect it might be a result of e.g. a
free_chunk() call with an incorrect size in the sljitExecAllocator.c code.

Alex -- do you want to have a look into this?

-- 
Mindaugas

Automated report: NetBSD-current/i386 build failure

2017-04-21 Thread NetBSD Test Fixture 
This is an automatically generated notice of a NetBSD-current/i386
build failure.

The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2017.04.21.19.18.05.

An extract from the build.sh output follows:


/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/lfs_cleanerd

/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/ldconfig

/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/pdisk

/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/ping6

/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/scp

/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/ssh

/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/slogin

/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/i486--netbsdelf-install 
-U -M /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG -D 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir -h sha256 -N 
/tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc -l h -r -o root -g wheel -m 
555 /tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/cat 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/rescue/ldd
--- afterinstall ---
makedb ===> share/man
infodir-meta ===> external/gpl2/texinfo/bin/install-info
--- infodir-meta ---
echo "./usr/share/info/dir type=file mode=0644 uname=root gname=wheel"  | 
/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/nbcat -l >> 
/tmp/bracket/build/2017.04.21.19.18.05-i386/destdir/METALOG
do-obsolete ===> .
--- do-obsolete ---
install-obsolete-lists ===> etc
--- install-obsolete-lists ---
mkdir -p /tmp/bracket/build/2017.04.21.19.18.05-i386/obj/etc/obsolete.dir
(cd /tmp/bracket/build/2017.04.21.19.18.05-i386/src/distrib/sets &&  
AWK=/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/nbawk 
MAKE=/tmp/bracket/build/2017.04.21.19.18.05-i386/tools/bin/nbmake /bin/sh 
./makeobsolete -t 
/tmp/bracket/build/2017.04.21.19.18.05-i386/obj/etc/obsolete.dir)
export: i386pae-xen: bad variable name
*** [install-obsolete-lists] Error code 2
nbmake[4]: stopped in /tmp/bracket/build/2017.04.21.19.18.05-i386/src/etc
1 error

The following commits were made between the last successful build and
the failed build:

2017.04.21.14.46.31 szptvlfn src/bin/ln/ln.c,v 1.38
2017.04.21.15.04.10 christos src/lib/libc/sys/_lwp_create.2,v 1.6
2017.04.21.15.06.37 christos

wd* at umass? owners wanted for testing

2017-04-21 Thread Jaromír Doleček 
Hi,

as part of work on jdolecek-ncq branch, I've made some mechanical
changes to adjust the umass_isdata.c driver code to still hopefully
work. I don't have the hardware though, so I'd like to have a real
confirmation from somebody who does, before the branch would be
merged.

If you have the hardware which is attached as wd* at umass?, can you
please try to boot the kernel from the branch, check if it actually
works and let me know the results?

Thank you.

Jaromir

Packages crashing on -current

2017-04-21 Thread coypu 
Hi,

mprotect (and ASLR) are security measures that not all pkgsrc packages
can survive, so some packages had NOT_PAX_MPROTECT_SAFE set for some
binaries, to disable it.

However the condition for using NOT_PAX_MPROTECT_SAFE was incorrectly
only done for NetBSD/amd64.

The outcome should've been things like (only on -current, stable is
unaffected as it doesn't have pax mprotect enabled):
- Firefox crashes
- Libreoffice segfaults during build
etc.

You can test if mprotect is disabled e.g. for firefox using file:
> file /usr/pkg/lib/firefox/firefox
/usr/pkg/lib/firefox/firefox: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked, interpreter /usr/libexec/ld.elf_so, for NetBSD 
7.99.65, PaX: -mprotect, 
BuildID[sha1]=577897fd2966e904de0c47df56c5af86b3d9312b, stripped

Noteworthy part: PaX: -mprotect

Newly built packages will disable it on a per-file basis (now not only
on amd64), but unfortunately there are many files to adjust.
If you just want it fixed now, a quick workaround is disabling mprotect
globally:
  # sysctl -w security.pax.mprotect.enabled=0

You can disable it on a per-file basis, which is what all new packages
will do now, using:
  # paxctl +m /path/to/binary

Automated report: NetBSD-current/i386 build success

2017-04-21 Thread NetBSD Test Fixture 
The NetBSD-current/i386 build is working again.

The following commits were made between the last failed build and the
successful build:

2017.04.21.11.49.31 kre src/sys/dev/pci/pci_subr.c,v 1.178

Log files can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2017.04.html#2017.04.21.11.49.31

Automated report: NetBSD-current/i386 build failure

2017-04-21 Thread NetBSD Test Fixture 
This is an automatically generated notice of a NetBSD-current/i386
build failure.

The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2017.04.21.09.01.52.

An extract from the build.sh output follows:

--- pci_subr.pico ---

/tmp/bracket/build/2017.04.21.09.01.52-i386/src/sys//dev/pci/pci_subr.c:2315:2: 
error: expected '}' before '{' token
  { PCI_CAP_FPB,  "Flattening Portal Bridge", NULL }
  ^
--- pci_subr.o ---

/tmp/bracket/build/2017.04.21.09.01.52-i386/src/sys//dev/pci/pci_subr.c:2315:2: 
error: expected '}' before '{' token
  { PCI_CAP_FPB,  "Flattening Portal Bridge", NULL }
  ^
--- pci_drvname.o ---
/tmp/bracket/build/2017.04.21.09.01.52-i386/tools/bin/nbctfconvert -g -L 
VERSION pci_drvname.o
--- pci_subr.po ---
*** [pci_subr.po] Error code 1
nbmake[7]: stopped in 
/tmp/bracket/build/2017.04.21.09.01.52-i386/src/lib/libpci
--- pci_drvname.o ---

The following commits were made between the last successful build and
the failed build:

2017.04.21.09.01.52 msaitoh src/sys/dev/pci/pci_subr.c,v 1.177
2017.04.21.09.01.52 msaitoh src/sys/dev/pci/pcireg.h,v 1.128

Log files can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2017.04.html#2017.04.21.09.01.52