nd6 RTM_ADD logic

Hi, To make ND6 mp-safe, I have to guarantee the life time of ln = rt->rt_llinfo. This call to nd6_llinfo_settimer(ln) looks strange. The complicated logic can be replaced with what we have in ARP. Digging through the histroy shows a lot of refactoring that seems to make rt_expire handling here

Re: ure(4): add support for RTL8153D

Hi Kevin, This seems to work fine on my machine. The ure0 is built into my monitor: ure0 at uhub9 port 3 configuration 1 interface 0 "Realtek USB 10/100/1000 LAN" rev 3.20/33.00 addr 4 ure0: RTL8153D (0x7420), address c8:4b:d6:af:a7:8d I can get both v4 and v6 addresses over this interface and

Re: patch: profiling using utrace(2) (compatible with pledge and unveil)

On 2023/04/11 09:28:31 +0200, Sebastien Marie wrote: > Hi, > > After otto@ work on mallocdump using utrace(2), I started to look again at > profiling (see moncontrol(2)). > > The current implementation tries to write a gmon.out file at program exit(3) > time, which isn't compatible with pledge

mbuf quueue lockless access

Hi, The mbuf_queue API allows read access to integer variables which another CPU may change simultaneously. To prevent miss-optimisations by the compiler, they need the READ_ONCE() macro. Otherwise there could be two read operations with inconsistent values. Writing to integer in mq_set_maxlen(

Re: OpenBSD 7.2 on Oracle Cloud

On Thu, 4 May 2023, Aaron Mason wrote: > On Mon, May 1, 2023 at 4:56 AM Stefan Fritsch wrote: > > > > Hi, > > > > what qemu version are you using? I cannot reproduce this with qemu 7.2. > > Can you try with a newer qemu? > > > > Cheers, > > Stefan > > > > What is the host OS where you're runn

Re: malloc: less unlock/lock dancing

On Thu, Apr 27, 2023 at 02:17:10PM +0200, Otto Moerbeek wrote: > This was introduced to not stall other threads while mmap is called by > a thread. But now that mmap is unlocked, I believe it is no longer > useful. > > A full build is slighlty faster with this. But this also needs testing > with

Re: crontab: support random offsets for steps

> On May 3, 2023, at 1:32 PM, Todd C. Miller wrote: > > Crontab supports things like "*/20" in the minutes column to run > every 20 minutes. For example, given: > > */20 * * * * echo I am right on time > > The job above would run at 0, 20, and 40 minutes of every hours. > > job@ asked whe

Re: crontab: support random offsets for steps

On Thu, 04 May 2023 07:32:18 -0700, Navan Carson wrote: > Any chance the syntax could be: > > ~/20 * * * * command > > To align with how ~ is used currently. That is already a valid syntax, though not a terribly useful one. It currently results in a random number with a step of 20. - todd

OpenBGPD 8.0 released

We have released OpenBGPD 8.0, which will be arriving in the OpenBGPD directory of your local OpenBSD mirror soon. This release includes the following changes to the previous release: * Include OpenBSD 7.3 errata 001: A new ASPA object appeared in the RPKI ecosystem and exposed bugs in

Re: crontab: support random offsets for steps

On Wed, May 3, 2023, at 15:30, Todd C. Miller wrote: > Opinions? Does the proposed syntax seem OK? Speaking strictly as an operator/administrator, I think this is great. I would use it immediately, as it replaces deployed configuration I have in place today which does something roughly equivale

crontab: remove tmp file on seteuid() failure

Fix a bug introduced in rev 1.86 (fchown removal). Currently, if the second seteuid(2) were to fail (not really possible) we would leave a temporary file in the spool dir. This will be ignored by cron but we still want to clean it up. - todd Index: usr.sbin/cron/crontab.c =

cron: better error checking of random values

This fixes two issues with the parsing of random values: 1) A random value with a step is now rejected. For example: ~/10* * * * echo invalid 0~59/10 * * * * echo invalid 10~/10 * * * * echo invalid ~40/10 * * * * echo invalid Previously, the '/' would just be discarde

Re: mbuf quueue lockless access

> On 4 May 2023, at 20:52, Alexander Bluhm wrote: > > Hi, > > The mbuf_queue API allows read access to integer variables which > another CPU may change simultaneously. To prevent miss-optimisations > by the compiler, they need the READ_ONCE() macro. Otherwise there > could be two read opera

Re: cron: better error checking of random values

On Thu, May 04, 2023 at 03:30:30PM -0600, Todd C. Miller wrote: > This fixes two issues with the parsing of random values: > > 1) A random value with a step is now rejected. For example: > > ~/10* * * * echo invalid I've ben using ~/10 to randomly distribute four similar tasks so that t

Re: veb(4) control flooding via the discover flag only

On Sun, Apr 30, 2023 at 9:03 PM Nicolas Bouliane wrote: > > This make it possible to prevent port flooding > by simply disabling the discover bit per interface. > --- > sys/net/if_veb.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/sys/net/if_veb.c b/sys/net/if_veb.c >

Re: cron: better error checking of random values

On Thu, 04 May 2023 21:41:26 -, Klemens Nanni wrote: > On Thu, May 04, 2023 at 03:30:30PM -0600, Todd C. Miller wrote: > > This fixes two issues with the parsing of random values: > > > > 1) A random value with a step is now rejected. For example: > > > > ~/10* * * * echo invalid >

EPIPE returned by kevent(2)

I'm debugging a non-trivial multithreaded unit test in the current version of lang/ghc. It runs into some kind of unexpected condition not handled well by GHC. I suspect we do something non-standard to cause this behavior. These two ktrace items illustrate the issue: 12550/209588 T21651 CALL

Re: cron: better error checking of random values

On 23-05-04 05:40PM, Todd C. Miller wrote: > On Thu, 04 May 2023 21:41:26 -, Klemens Nanni wrote: > > > On Thu, May 04, 2023 at 03:30:30PM -0600, Todd C. Miller wrote: > > > This fixes two issues with the parsing of random values: > > > > > > 1) A random value with a step is now rejected. Fo