Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Martijn van Duren
On Tue, 2022-11-22 at 11:25 +0100, Claudio Jeker wrote: > On Tue, Nov 22, 2022 at 09:25:08AM +, Stuart Henderson wrote: > > Need to query (and set $if, which might be used in route commands etc) I > > think. > > > > I would prefer if people took a step back from configuring interfaces by > M

Re: mbufs growing in 7.2

2022-11-22 Thread Greg Steuck
The watched kettle never boiled. No more crashes in over two weeks (instead of two in the first week). I tried a loop of alternating iperf3 tcp and udp to no ill effect. I still see the growth in the metrics I reported, yet the system remained stable. I applied the patch below and am still collect

Re: Get rid of UVM_VNODE_CANPERSIST

2022-11-22 Thread Mark Kettenis
> Date: Tue, 22 Nov 2022 17:47:44 + > From: Miod Vallat > > > Here is a diff. Maybe bluhm@ can try this on the macppc machine that > > triggered the original "vref used where vget required" problem? > > On a similar machine it panics after a few hours with: > > panic: uvn_flush: PGO_SYNCIO

Re: Get rid of UVM_VNODE_CANPERSIST

2022-11-22 Thread Alexander Bluhm
On Tue, Nov 22, 2022 at 05:47:44PM +, Miod Vallat wrote: > > Here is a diff. Maybe bluhm@ can try this on the macppc machine that > > triggered the original "vref used where vget required" problem? > > On a similar machine it panics after a few hours with: > > panic: uvn_flush: PGO_SYNCIO re

Re: Get rid of UVM_VNODE_CANPERSIST

2022-11-22 Thread Miod Vallat
> Here is a diff. Maybe bluhm@ can try this on the macppc machine that > triggered the original "vref used where vget required" problem? On a similar machine it panics after a few hours with: panic: uvn_flush: PGO_SYNCIO return 'try again' error (impossible) The trace (transcribed by hand) is u

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Andrew Hewus Fresh
On Tue, Nov 22, 2022 at 03:37:20PM +, Klemens Nanni wrote: > On Tue, Nov 22, 2022 at 08:09:11AM -0700, Theo de Raadt wrote: > > Florian Obser wrote: > > > ifconfig(8) already knows about these (see -C option). Which made me > > > think, it might be easier to just ask ifconfig(8). > > > > > >

Re: install.sub: fix softraid disks not being created before md_installboot()

2022-11-22 Thread ssnf
> Deliver steps to reproduce, installation logs, machine information, > version details, ANYTHING technical. Version: OpenBSD 7.2 release Arch:i386 Image: install72.iso Machine: Thinkpad 380XD 32MB 233MHz Pentium MMX Steps: - Boot install CDROM - (S)hell - cd

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Klemens Nanni
On Tue, Nov 22, 2022 at 08:09:11AM -0700, Theo de Raadt wrote: > Florian Obser wrote: > > > On 2022-11-22 18:06 +10, David Gwynne wrote: > > > > > > There are a few things to keep in mind if we're going to use lladdrs like > > > this. > > > > > > vlan interfaces start with their lladdr as 00:00

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Theo de Raadt
Florian Obser wrote: > On 2022-11-22 18:06 +10, David Gwynne wrote: > > > > There are a few things to keep in mind if we're going to use lladdrs like > > this. > > > > vlan interfaces start with their lladdr as 00:00:00:00:00:00 and then > > assume the lladdr of the parent interface when that

Re: interface hooks to pf(4) should be using PF_LOCK()/PF_UNLOCK()

2022-11-22 Thread Klemens Nanni
On Sun, Nov 06, 2022 at 07:12:31PM +0100, Alexandr Nedvedicky wrote: > Hello, > > diff below is the first step to make pfioctl() _without_ NET_LOCK(). > Currently pf_if.c seems to be the only blocker which prevents us > from removing all NET_LOCK()/NET_UNLOCK() calls we have in pf(4). > > diff be

Re: Get rid of UVM_VNODE_CANPERSIST

2022-11-22 Thread Mark Kettenis
> Date: Tue, 22 Nov 2022 15:08:30 +0100 > From: Martin Pieuchot > > On 18/11/22(Fri) 21:33, Mark Kettenis wrote: > > > Date: Thu, 17 Nov 2022 20:23:37 +0100 > > > From: Mark Kettenis > > > > > > > From: Jeremie Courreges-Anglas > > > > Date: Thu, 17 Nov 2022 18:00:21 +0100 > > > > > > > > On

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Vitaliy Makkoveev
On Tue, Nov 22, 2022 at 06:28:31AM -0700, Theo de Raadt wrote: > Vitaliy Makkoveev wrote: > > > On Tue, Nov 22, 2022 at 11:25:55AM +0100, Claudio Jeker wrote: > > > On Tue, Nov 22, 2022 at 09:25:08AM +, Stuart Henderson wrote: > > > > Need to query (and set $if, which might be used in route c

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Theo de Raadt
Vitaliy Makkoveev wrote: > As dlg@ pointed, we have collisions with clonable devices, which inherit > lladdr or could generate already existing lladdr. We need to handle > this, for example exclude clobable devices from hostname.lladdr logic. Noone is proposing deleting the existing support for

Re: Get rid of UVM_VNODE_CANPERSIST

2022-11-22 Thread Martin Pieuchot
On 18/11/22(Fri) 21:33, Mark Kettenis wrote: > > Date: Thu, 17 Nov 2022 20:23:37 +0100 > > From: Mark Kettenis > > > > > From: Jeremie Courreges-Anglas > > > Date: Thu, 17 Nov 2022 18:00:21 +0100 > > > > > > On Tue, Nov 15 2022, Martin Pieuchot wrote: > > > > UVM vnode objects include a refere

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Theo de Raadt
Claudio Jeker wrote: > On Tue, Nov 22, 2022 at 09:25:08AM +, Stuart Henderson wrote: > > Need to query (and set $if, which might be used in route commands etc) I > > think. > > > > I would prefer if people took a step back from configuring interfaces by > MAC address. It feels like a overl

Re: lladdr support for netstart/hostname.if (was: Re: Locking network card configuration)

2022-11-22 Thread Theo de Raadt
Miod Vallat wrote: > I'm a bit late to the thread, but whatever its outcome, things have to > work correctly on older sparc64 hardware, where the default behaviour > for on-board and Sun-branded expansion card interfaces is to use the > same MAC address. > > This hints that hostname. should have

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Theo de Raadt
Vitaliy Makkoveev wrote: > On Tue, Nov 22, 2022 at 11:25:55AM +0100, Claudio Jeker wrote: > > On Tue, Nov 22, 2022 at 09:25:08AM +, Stuart Henderson wrote: > > > Need to query (and set $if, which might be used in route commands etc) I > > > think. > > > > > > > I would prefer if people too

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Theo de Raadt
Claudio Jeker wrote: > Not all interfaces have MAC addresses. E.g. umb(4) would need a > different identifier (most probably the IMEI). Some interfaces inherit > the MAC address from an other interface (vlan, trunk). Then don't use hostname.MAC for those interfaces. The other mechanism will re

Re: lladdr support for netstart/hostname.if (was: Re: Locking network card configuration)

2022-11-22 Thread Miod Vallat
I'm a bit late to the thread, but whatever its outcome, things have to work correctly on older sparc64 hardware, where the default behaviour for on-board and Sun-branded expansion card interfaces is to use the same MAC address. This hints that hostname. should have priority over hoshname. for the

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Vitaliy Makkoveev
On Tue, Nov 22, 2022 at 11:25:55AM +0100, Claudio Jeker wrote: > On Tue, Nov 22, 2022 at 09:25:08AM +, Stuart Henderson wrote: > > Need to query (and set $if, which might be used in route commands etc) I > > think. > > > > I would prefer if people took a step back from configuring interfaces

Re: mg: handle prefix argument in shell-command{,-on-region}

2022-11-22 Thread Omar Polo
anyone? On 2022/11/09 09:00:03 +0100, Omar Polo wrote: > bump > > On 2022/10/25 14:30:51 +0200, Omar Polo wrote: > > On 2022/10/13 12:25:00 +0200, Omar Polo wrote: > > > shell-command (M-!) and shell-command-on-region (M-|) works by > > > displaying the output of the command in a new buffer, b

Re: interface hooks to pf(4) should be using PF_LOCK()/PF_UNLOCK()

2022-11-22 Thread David Gwynne
> On 22 Nov 2022, at 18:49, Alexandr Nedvedicky wrote: > > Hello, > > this change is required to unhook pf(4) from NET_LOCK(). > therefore I'd like to get it in. ok dlg@ > > On Mon, Nov 07, 2022 at 04:51:59AM +1000, David Gwynne wrote: >> >> >>> On 7 Nov 2022, at 4:12 am, Alexandr Nedved

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Claudio Jeker
On Tue, Nov 22, 2022 at 09:25:08AM +, Stuart Henderson wrote: > Need to query (and set $if, which might be used in route commands etc) I > think. > I would prefer if people took a step back from configuring interfaces by MAC address. It feels like a overly specific hack is introduced for a c

Re: reorder_kernel: suport ro /usr like library_aslr does

2022-11-22 Thread Thomas de Grivel
Hello, I use read only /usr also, I don't like a script changing mount options without a warning. If it's read-only reorder_kernel should fail. I just put a symlink from /usr/share/relink to /var/relink and everything works fine... With mount_mfs we could have a temporary directory but where has g

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Stuart Henderson
Need to query (and set $if, which might be used in route commands etc) I think. -- Sent from a phone, apologies for poor formatting. On 22 November 2022 08:37:05 Florian Obser wrote: On 2022-11-22 18:06 +10, David Gwynne wrote: There are a few things to keep in mind if we're going to use

Re: interface hooks to pf(4) should be using PF_LOCK()/PF_UNLOCK()

2022-11-22 Thread Alexandr Nedvedicky
Hello, this change is required to unhook pf(4) from NET_LOCK(). therefore I'd like to get it in. On Mon, Nov 07, 2022 at 04:51:59AM +1000, David Gwynne wrote: > > > > On 7 Nov 2022, at 4:12 am, Alexandr Nedvedicky wrote: > > > > Hello, > > > > diff below is the first step to make pfioctl()

Re: lladdr support for netstart/hostname.if

2022-11-22 Thread Florian Obser
On 2022-11-22 18:06 +10, David Gwynne wrote: > > There are a few things to keep in mind if we're going to use lladdrs like > this. > > vlan interfaces start with their lladdr as 00:00:00:00:00:00 and then assume > the lladdr of the parent interface when that is configured. > > Clonable devices (

Re: lladdr support for netstart/hostname.if (was: Re: Locking network card configuration)

2022-11-22 Thread David Gwynne
> On 22 Nov 2022, at 16:13, Andrew Hewus Fresh wrote: > > On Mon, Nov 21, 2022 at 04:56:07PM +0100, Martijn van Duren wrote: >> On Sun, 2022-11-20 at 19:35 -0700, Theo de Raadt wrote: >>> Steve Litt wrote: >>> Vitaliy Makkoveev said on Mon, 21 Nov 2022 03:48:21 +0300 >> On 20