Hi Paul and Jun,
Thank you for your reporting!
Now I can reproduce the issue quickly using openvpn.
So I would provide a fix soon (hopefully).
ozaki-r
On Tue, Sep 1, 2015 at 8:14 PM, Paul Goyette wrote:
> On Mon, 31 Aug 2015, Ryota Ozaki wrote:
>
>> Hi,
>>
>> I've committed a fix for rt_refc
Updating src tree:
P src/distrib/sets/lists/debug/shl.mi
P src/lib/libc/net/if_nametoindex.c
P src/lib/libc/stdlib/getopt_long.c
P src/libexec/lfs_cleanerd/cleaner.h
P src/libexec/lfs_cleanerd/lfs_cleanerd.c
P src/sbin/dump_lfs/lfs_inode.c
P src/sbin/fsck_lfs/dir.c
P src/sbin/fsck_lfs/fsck_vars.h
Sorry, should be fixed now.
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 2015.09.01.16.04.04.
An extract from the build.sh output follows:
/tmp/bracket/build/2015.09.01.16.04.04-i386/src/u
# compile config/mkmakefile.o
/usr/src/obj/tooldir.NetBSD-7.99.21-amd64/bin/x86_64--netbsd-gcc -O2
-std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wno-sign-compare -Wno-traditional
-Wa,--fatal-warnings -Wreturn-type -Wswi
tch -Wshadow -Wcast-qual -Wwrite-strings -
On Mon, 31 Aug 2015, Ryota Ozaki wrote:
Hi,
I've committed a fix for rt_refcnt. Could you try again
with -current? (though I'm not sure the fix is related to
the issue...)
The fix is not helping on my situation, either!
Here is the latest info, based on a kernel from today's sources...
(gdb