Re: fix snmpd reporting of IP-MIB::ipForwarding.0

On Wed, Oct 07, 2015 at 10:39:17PM +0100, Stuart Henderson wrote: > IP-MIB::ipForwarding.0 should return one of these values: > > ipForwarding OBJECT-TYPE > SYNTAX INTEGER { > forwarding(1),-- acting as a router > notForwarding(2) -- NOT acting

Re: Bulkget & snmpd

On 2015/10/08 01:02, Stuart Henderson wrote: > > $ snmpbulkget -Cn2 -Cr4 -v2c -c public 127.0.0.1 SNMPv2-MIB::sysDescr > > IP-MIB::ipForwarding IF-MIB::ifName IF-MIB::ifInOctets > > SNMPv2-MIB::sysDescr.0 = STRING: some host description > > IP-MIB::ipForwarding.0 = INTEGER: notForwarding(2) > >

Re: unlock bge(4)

On 05/10/15(Mon) 12:42, Jonathan Matthew wrote: > This brings bge(4) up to about where em(4) is. It involves a few different > changes, notably: > - per-ring refill timeouts, to ensure we don't try to refill a ring from the > timeout and an interrupt at the same time > - removing the list of tx

link state change madness

Recent NFS-related rtisvalid(9) regressions turns out to be related to the use of DOWN RTF_CLONED route entries. Such entries are DOWN because they are cloned from a DOWN RTF_CLONING entry. While investigating this race I figured out that we have different code paths messing with link-state

tame signify

Without mucking about in the internals, here are some toplevel tame calls. Index: signify.c === RCS file: /cvs/src/usr.bin/signify/signify.c,v retrieving revision 1.100 diff -u -p -r1.100 signify.c --- signify.c 16 Jan 2015

Re: tame signify

Ted Unangst wrote: > Without mucking about in the internals, here are some toplevel tame calls. check return values. ok, ok. in the fairly common verify case of piping msgfile to - (as in patching), we can cut things down a bit more as well. Index: signify.c

ip6_output bcopy->memcpy

Hello - This diff converts some malloc/bcopy to malloc/memcpy. netinet6 didn't get the bcopy->memcpy overhaul like netinet did. Index: netinet6/ip6_output.c === RCS file: /cvs/src/sys/netinet6/ip6_output.c,v retrieving revision

fix ksh histfile owner

ksh does a little dance to try and gift history files to their original owner if it's somehow running as a different user. this of course only works as root, and is probably a terrible idea. ksh should simply refuse to open a history file that's owned by somebody else. Index: history.c

Re: unlocking em - unable to fill any rx descriptors

On Thu, Oct 08, 2015 at 01:20 +0200, Hrvoje Popovski wrote: > Hi all, > > i have fairly simple setup with receiver connected to em2 and sender > connected to em3. Both em are Intel I350. Setup is without pf with these > sysctls: > > kern.pool_debug=1 >net.inet.ip.forwarding=1 >

Re: fix ksh histfile owner

> ksh does a little dance to try and gift history files to their original owner > if it's somehow running as a different user. this of course only works as > root, and is probably a terrible idea. When I found this with tame, I got worried about the implications of how ksh is opening the file in

mg(1) onlywind() line number anomaly

If you open mg with only the *scratch* buffer loaded (no file names given on command line), and press enter 5 times, take a note of the line number in the status bar then open theo mode (M-x theo). Then move back to the *scratch* buffer via switch-to-buffer (C-x b). You'll notice the line number

vattr_null() doesn't initialize va_filerev

Filesystem implementations depend on vattr_null() to initialize the fields in struct vattr, which is true for all the fields except va_filerev. It therefore is not set to VNOVAL as expected by the file system, but contains whatever was there on the stack. This causes VOP_GETATTR() on cd9660 and

[patch] regress test fix: libc/db

Implement max file size constant in libc/db/dbtest regression test. Some /bin files read for testing are larger than SIZE_MAX causing tests to fail. Also change error for file too large from E2BIG to EFBIG. Feedback is very appreciated. Index: dbtest.c

[patch] regress test fix: systrace/id

Attached is a patch for the systrace/id regress test: Updated the id.policy used to allow the new pledge syscall This is my first time working with the regress tests. I want to make sure I'm on the right track so any tips are appreciated. Is there interest in additional regress test work? I have

Re: Unlocking ix(4) a bit further

> Date: Wed, 30 Sep 2015 14:30:11 +0200 (CEST) > From: Mark Kettenis > > Since people seemed to like my diff for em(4), here is one for ix(4). > In addition to unlocking the rx completion path, this one also uses > intr_barrier() and removes the rx mutex that claudio@

Re: unlocking em - unable to fill any rx descriptors

> Date: Thu, 8 Oct 2015 18:12:26 +0200 > From: Mike Belopuhov > > Is it possible that em_reset_hw is called a bit too early > while we don't have full control of the driver? I don't think that's a problem. > Also it appears to me that while we're mi_switch'ing in the >