Re: diff: add tuning variables to config(8)

On Mon, 16 Jun 2014 11:35:07 -0600 Theo de Raadt wrote: >> > Followings are our kernel variables' default: >> > >> > - sb_max: 256K >> > - tcbhash_size: 128 >> > - udbhash_size: 128 >> > >> > These variables are sometime too small for busy server or gateway. >> > >> > I'd like to modify c

tcpdump: fix/improve bad checksum display

The way tcpdump displays bad checksums is annoyingly inconsistent. Here's an example where tcpdump is showing two packets: one with a bad IP checksum, and another with a bad TCP checksum (emphasis mine): Bad IP checksum 14:38:42.489639 192.168.30.1.20 > 192.168.30.70.80: S [tcp sum ok] 0:0(0) win

Re: increase netcat's buffer...

On Sat, Jun 14, 2014 at 10:55, Ted Unangst wrote: > On Fri, Jun 13, 2014 at 10:40, sven falempin wrote: Now soliciting diffs to change readwrite to a loop with two buffers that poll()s in all four directions. :) >>> Is using kqueue ok ? >>> >>> like : http://pastebin.com/F1

Re: sys/msdosfs: off by one

Tobias Stoeckmann wrote this message on Tue, Jun 17, 2014 at 00:05 +0200: > there is a potential off by one in function fillinusemap() leading to > possible out of boundary access (32 bytes after allocated area). > > pmp->pm_inusemap is allocated in msdosfs_vfsops.c like this: > > bmapsiz = (

Re: exec_elf.c: mistake ?

Reading through exec_elf.c, I just noticed the uninitialized bdiff variable myself, and remembered this thread. Tangentially, the code for worrying about zero-filling the last page is overzealous. We only need to zero-fill the page if memsz > filesz (accounting for alignment and page boundaries).

sys/msdosfs: off by one

Hi, there is a potential off by one in function fillinusemap() leading to possible out of boundary access (32 bytes after allocated area). pmp->pm_inusemap is allocated in msdosfs_vfsops.c like this: bmapsiz = (pmp->pm_maxcluster + N_INUSEBITS - 1) / N_INUSEBITS; pmp->pm_inusemap = mallo

Re: diff: add tuning variables to config(8)

> > Followings are our kernel variables' default: > > > > - sb_max: 256K > > - tcbhash_size: 128 > > - udbhash_size: 128 > > > > These variables are sometime too small for busy server or gateway. > > > > I'd like to modify config(8) to customize these variables without > > recompiling the

Re: diff: add tuning variables to config(8)

On Monday, June 16, 2014 18:55 CEST, Miod Vallat wrote: > > Followings are our kernel variables' default: > > > > - sb_max: 256K > > - tcbhash_size: 128 > > - udbhash_size: 128 > > > > These variables are sometime too small for busy server or gateway. > > > > I'd like to modify confi

Re: diff: add tuning variables to config(8)

> Followings are our kernel variables' default: > > - sb_max: 256K > - tcbhash_size: 128 > - udbhash_size: 128 > > These variables are sometime too small for busy server or gateway. > > I'd like to modify config(8) to customize these variables without > recompiling the kernel. If we go t

valid FAT32 for newfs and fsck

Hi, ran into this problem that NetBSD fixed a few months ago, which means that this diff is a "NetBSD merge": Our newfs_msdos creates an invalid FAT32 file system. The "first free cluster" of FSinfo points to cluster #2, which is used by the root directory. Next to that, fsck_msdos is a bit too

Re: diff: add tuning variables to config(8)

On Mon, 16 Jun 2014 21:28:55 +0900 (JST) YASUOKA Masahiko wrote: > Followings are our kernel variables' default: > > - sb_max: 256K > - tcbhash_size: 128 > - udbhash_size: 128 > > These variables are sometime too small for busy server or gateway. > > I'd like to modify config(8) to custom

diff: add tuning variables to config(8)

Followings are our kernel variables' default: - sb_max: 256K - tcbhash_size: 128 - udbhash_size: 128 These variables are sometime too small for busy server or gateway. I'd like to modify config(8) to customize these variables without recompiling the kernel. Comment or ok? Index: usr.sbi