Re: cut: Fix segmentation fault

Hi, On Wed, Mar 28, 2018 at 12:53:47AM +0200, Ingo Schwarze wrote: > Ouch, you are right. But then, the code feels counter-intuitive > and the error message confusing. I agree. Talking about a zero out of nothing seems weird, even though I have learned yesterday that "a=''; echo $((a))" is "0".

Re: interface queue transmit mitigation (again)

On 28/03/18(Wed) 11:28, David Gwynne wrote: > On Thu, Mar 15, 2018 at 03:25:46PM +0100, Martin Pieuchot wrote: > > On 14/03/18(Wed) 13:00, David Gwynne wrote: > > > this adds transmit mitigation back to the tree. > > > > > > it is basically the same diff as last time. the big difference this > >

Re: disklabel,fsck_ffs: division by zero on invalid frag sizes

On Tue, Mar 27, 2018 at 07:50:18PM +0200, Otto Moerbeek wrote: > On Tue, Mar 27, 2018 at 12:46:03PM +0200, Tobias Stoeckmann wrote: > > > Resending this old diff. Adjusted to apply with -current source: > > > > Illegal fragmentation block sizes can trigger division by zero in the > > disklabel

com.4: -socppc

Hi, socppc@attic was asking for this. -Artturi diff --git share/man/man4/com.4 share/man/man4/com.4 index 6301f04ae60..9c5f0d23230 100644 --- share/man/man4/com.4 +++ share/man/man4/com.4 @@ -91,10 +91,6 @@ .Cd "com0 at ioc? base 0x00020178" .Cd "com1 at ioc? base 0x00020170" .Pp -.Cd "#

Re: NFS vs NET_LOCK()

On 27/03/18(Tue) 15:47, Visa Hankala wrote: > On Tue, Mar 27, 2018 at 11:00:20AM +0200, Martin Pieuchot wrote: > > Diff below prevents a future lock ordering problem between NFSnode > > locks (similar to Inode locks) and the NET_LOCK(). > > > > It ensures the NET_LOCK() is always locked *after*

Re: com.4: -socppc

On 28/03/18(Wed) 12:46, Artturi Alm wrote: > Hi, > > socppc@attic was asking for this. It is not in the attic, please do not waste our time :)

Re: disklabel,fsck_ffs: division by zero on invalid frag sizes

> On Mar 28, 2018, at 11:56 AM, Tobias Stoeckmann wrote: > >> On Wed, Mar 28, 2018 at 12:25:01PM +0200, Otto Moerbeek wrote: >> Hmm, on what platform are you doing this? I could not reproduce your >> problem on arm64 -current, > > To sum it up: It was my fault, -current

ufs free()

Hello - This diff adds sizes to free(), which completes ufs/ffs. OK? Index: ufs/ffs/ffs_inode.c === RCS file: /cvs/src/sys/ufs/ffs/ffs_inode.c,v retrieving revision 1.76 diff -u -p -r1.76 ffs_inode.c --- ufs/ffs/ffs_inode.c 27 Feb

relayd http check fix

Hi! If relayd http check doesn't get any answer to its http check it marks backend host as up. host x.y.z, check http code (2010ms,tcp read timeout), state down -> up, availability 14.29% sample config: relay test { listen on x.x.x.x port forward to port check http "/" code 200 }

Re: sem_trywait(3) and sem_wait(3) can return EINTR

On Wed, Mar 28, 2018 at 2:14 PM, Paul Irofti wrote: > > I do not know if this is expected or not, but sem_trywait(3) can and > does return EINTR. From the manpage I got the impression that it should > not. Should we amend the manpage or is this something to be fixed in the >

Re: Anyone can suggest a BitCoin processor to the OpenBSD Foundation? BitPay has become terrible

So, related to this topic, Apparently BitPay has now fixed us up again. I have put the button back on the web site, if anyone wants to try a bitcoin donation is is supposed to be possible again

Re: use hashfree on pcb hash tables

round #2. keep track of size (num of elements) in the inpcbtable struct. passes regress tests. OK? Index: netinet/in_pcb.c === RCS file: /cvs/src/sys/netinet/in_pcb.c,v retrieving revision 1.228 diff -u -p -r1.228 in_pcb.c ---

sem_trywait(3) and sem_wait(3) can return EINTR

Hi, I do not know if this is expected or not, but sem_trywait(3) can and does return EINTR. From the manpage I got the impression that it should not. Should we amend the manpage or is this something to be fixed in the implementation? 73 do { 74 r =

Re: unbound 1.7.0

On Wed, Mar 28, 2018 at 12:31:01PM +0200, Florian Obser wrote: > I guess nobody is going to review a 10k line diff... so benno actually read the diff and points out that we need this: (already reported upstream) diff --git services/authzone.c services/authzone.c index 13e36b2c..fac8e4ed 100644

Re: interface queue transmit mitigation (again)

On 28.3.2018. 3:28, David Gwynne wrote: > On Thu, Mar 15, 2018 at 03:25:46PM +0100, Martin Pieuchot wrote: >> On 14/03/18(Wed) 13:00, David Gwynne wrote: >>> this adds transmit mitigation back to the tree. >>> >>> it is basically the same diff as last time. the big difference this >>> time is that

xhci@fdt; legacy binding support

The Marvell Aramada device trees use a legacy binding for the XHCI USB PHY. This diff adds support for this misfeature as fixing the device trees may take a while. It also adds support for the "usb-nop-xceiv" PHY type, which contains the reference to the regulator that supplies power to the USB

Re: disklabel,fsck_ffs: division by zero on invalid frag sizes

On Wed, Mar 28, 2018 at 12:25:01PM +0200, Otto Moerbeek wrote: > Hmm, on what platform are you doing this? I could not reproduce your > problem on arm64 -current, To sum it up: It was my fault, -current is all fine. The issue can be reproduced with 6.2-stable amd64 and somewhere between

Re: NFS vs NET_LOCK()

On Wed, Mar 28, 2018 at 11:59:46AM +0200, Martin Pieuchot wrote: > Index: uvm/uvm_vnode.c > === > RCS file: /cvs/src/sys/uvm/uvm_vnode.c,v > retrieving revision 1.99 > diff -u -p -r1.99 uvm_vnode.c > --- uvm/uvm_vnode.c 8 Mar 2018