Re: wg(4): 'Address already in use' when wgrtable is changed

Hi, On Mon, 28 Mar 2022 12:12:39 +0900 Yuichiro NAITO wrote: > On 3/27/22 18:25, YASUOKA Masahiko wrote: >> Hi, >> On Wed, 9 Mar 2022 15:28:44 +0900 >> Yuichiro NAITO wrote: >>> I see 'Address already in use' message, >>> when I change wgrtable for a running wg interface. >>> It doesn't make

Re: wg(4): 'Address already in use' when wgrtable is changed

Hello, thanks for the comment. On 3/27/22 18:25, YASUOKA Masahiko wrote: Hi, On Wed, 9 Mar 2022 15:28:44 +0900 Yuichiro NAITO wrote: I see 'Address already in use' message, when I change wgrtable for a running wg interface. It doesn't make sense to me. It can be reproduced by the following

Re: Security support status of xnf(4) and xbf(4)

On Mon, Mar 28, 2022 at 04:12:29AM +0200, Marek Marczykowski-Górecki wrote: > On Mon, Mar 28, 2022 at 12:45:24PM +1100, Damien Miller wrote: > > On Fri, 25 Mar 2022, Demi Marie Obenour wrote: > > > > > Linux’s netfront and blkfront drivers recently had a security > > > vulnerability (XSA-396)

Re: Security support status of xnf(4) and xbf(4)

On Mon, Mar 28, 2022 at 12:45:24PM +1100, Damien Miller wrote: > On Fri, 25 Mar 2022, Demi Marie Obenour wrote: > > > Linux’s netfront and blkfront drivers recently had a security > > vulnerability (XSA-396) that allowed a malicious backend to potentially > > compromise them. In follow-up

Re: Security support status of xnf(4) and xbf(4)

On Fri, 25 Mar 2022, Demi Marie Obenour wrote: > Linux’s netfront and blkfront drivers recently had a security > vulnerability (XSA-396) that allowed a malicious backend to potentially > compromise them. In follow-up audits, I found that OpenBSD’s xnf(4) > currently trusts the backend domain. I

Re: [patch] CPU frequency scheduler change proposal

Am Mon, 21 Mar 2022 16:31:42 +0100 schrieb Matthias Schmidt : > Hi, > > * Solene Rapenne wrote: > > I'm proposing a very simple change to the automatic policy of the > > CPU frequency scheduler. > > > > Currently, every 100ms the scheduler is doing this: > > > > - when the CPU load exceeds the

ftp.1: fix editing mishap

It appears that in revision 1.85 of usr.bin/ftp/ftp.1 a sentence fragment was accidentally not removed. OK? Index: usr.bin/ftp/ftp.1 === RCS file: /cvs/src/usr.bin/ftp/ftp.1,v retrieving revision 1.122 diff -u -p -r1.122 ftp.1 ---

Re: vfs: do not export vnode_{hold,free}_list outside kern/vfs_subr.c

On Sun, 27 Mar 2022 15:05:00 +0200, Sebastien Marie wrote: > The following diff removes vnode_hold_list, vnode_free_list extern references > , > and `struct freelst` definition from sys/vnode.h > > `struct freelst` definition (TAILQ_HEAD) is moved where used, inside vfs_subr > .c. OK millert@

vfs: document (and correct) the protection required for manipulating v_numoutput

Hi, v_numoutput is a struct member of vnode which is used to keep track the number of writes in progress. in several function comments, it is marked as "Manipulates v_numoutput. Must be called at splbio()". So I added a "[B]" mark in the comment to properly document the need of IPL_BIO

vfs: do not export vnode_{hold,free}_list outside kern/vfs_subr.c

Hi, The following diff removes vnode_hold_list, vnode_free_list extern references, and `struct freelst` definition from sys/vnode.h `struct freelst` definition (TAILQ_HEAD) is moved where used, inside vfs_subr.c. Kernel (GENERIC.MP i386) still build (and run). No usage found via grep on whole

Re: wg(4): 'Address already in use' when wgrtable is changed

Hi, On Wed, 9 Mar 2022 15:28:44 +0900 Yuichiro NAITO wrote: > I see 'Address already in use' message, > when I change wgrtable for a running wg interface. > It doesn't make sense to me. > > It can be reproduced by the following command sequence. > > ``` > # route -T1 add default `cat