match on more ure(4) devices

match on additional device ids from lenovo windows driver https://download.lenovo.com/consumer/options/thinkpad_usb-c_dock_gen2_drivers_v1.0.3.03241.exe and linux driver Index: usbdevs === RCS file: /cvs/src/sys/dev/usb/usbdevs,v

scsi_xfer pool exhausted! (syzkaller machine)

I just hit the endless "scsi_xfer pool exhausted!" stream that others reported over the years. I don't believe people previously found a satisfactory resolution to the problem. The machine in question is a Google Compute Engine VM (I found reports of vmware VM with this symptom). One thing I

Re: Make df output more human friendly in daily(8)

On Sat, 3 Oct 2020 13:53:13 +0100, Stuart Henderson wrote: > > +next_part "Backing up filesystems with dump:" > > +dump w | grep -vB1 ^Dump > > The "next_part" header text is wrong, it isn't doing a backup here, > it's only reporting which need to be dumped. Thanks! Here's a version with

Re: Make df output more human friendly in daily(8)

Hi Daniel/Ingo, On Fri, 2 Oct 2020 15:41:31 -0400 Daniel Jakots wrote: > +next_part "Backing up filesystems with dump:" > +dump w | grep -vB1 ^Dump That command doesn't dump disks. w shows the operator what to dump. Cheers, Craig.

arm64 dt(4) improvements

Diff below has two dt(4) improvements. It fixes the construction of the call frame that accompanies the stack frame. Currently it sticks the saved copy of the LR register in there. But instead it should stick the value of the ELR in there to record the location where the trap happened. This

ls: match historic behavior listing empty directories

This is adapted from FreeBSD revs 130236 and 130237 which have the following log message: If we are asked to print the total number of blocks, do so even if we have no entries to print (either due to an empty directory or an error). This makes the -l and -s options more consistent,

Re: Support astfb(4) in wsfb(4)

On Sat, Oct 03, 2020 at 04:50:28PM +0200, Mark Kettenis wrote: > The astfb(4) is a little-endian framebuffer on a (for now) big-endian > architecture. Therefore we need to tell X that the pixels have their > color components laid out in a non-standard way. > > Note that support for this pixel

Re: pthread_spin_unlock and ownership behaviour

> For shits and giggles I deceided to look into pthread_spin_unlock and > saw that we return EPERM here, while POSIX states that this behaviour > is unconditionally undefined.[0] Is there a reason why we shouldn't > abort here as well? Undefined doesn't mean it can turn into a bowl of petunias.

Support astfb(4) in wsfb(4)

The astfb(4) is a little-endian framebuffer on a (for now) big-endian architecture. Therefore we need to tell X that the pixels have their color components laid out in a non-standard way. Note that support for this pixel layout in X is weak. Normal stuff works but the software rendering in Mesa

Re: Make df output more human friendly in daily(8)

On 2020/10/03 08:44, Daniel Jakots wrote: > On Sat, 3 Oct 2020 08:00:44 +0200, Ingo Schwarze > wrote: > > > But this needs to remain: > > > > > -Reports on which file systems need to be dumped via > > > -.Xr dump 8 . > > > -.It > > Indeed, I wrongly assumed that the other dump call was

Re: Make df output more human friendly in daily(8)

On Sat, 3 Oct 2020 08:00:44 +0200, Ingo Schwarze wrote: > But this needs to remain: > > > -Reports on which file systems need to be dumped via > > -.Xr dump 8 . > > -.It Indeed, I wrongly assumed that the other dump call was silent. Here's the updated diff: Index: share/man/man8/daily.8

Re: pthread_spin_unlock and ownership behaviour

Ports-wise, from a Nov 2019 build on i386, these used it: $ grep -Rl pthread_spin_unlock wrkscan wrkscan/devel/libivykis wrkscan/x11/gnustep/base wrkscan/x11/e17/eina wrkscan/misc/posixtestsuite wrkscan/net/libunbound wrkscan/net/libshout wrkscan/net/icecast wrkscan/net/bird/1,-doc

Re: mmap: Do not push KERNEL_LOCK() too far

> Date: Fri, 2 Oct 2020 10:32:27 +0200 > From: Martin Pieuchot > > On 01/10/20(Thu) 21:44, Mark Kettenis wrote: > > > Date: Thu, 1 Oct 2020 14:10:56 +0200 > > > From: Martin Pieuchot > > > > > > While studying a bug report from naddy@ in 2017 when testing guenther@'s > > > amap/anon locking

Re: fix: ospf6d(8): wrong intra area announcement

On Fri, Oct 02, 2020 at 02:01:09AM +0200, Jan Klemkow wrote: > Hi, > > The new intra area db entry has to be saved into the tree before > orig_intra_area_prefix_lsas() is called. If not, the ospf6d will not > announce the new intra area db for a newly learned link from another > ospf router of

pthread_spin_unlock and ownership behaviour

Back in 2012 kurt@ added an abort call for the undefined behaviour cases on pthread_mutex_unlock. This helped me a great deal in examining the cause of some weird behaviour in icinga (or in the case of openbsd, just plain crash). For shits and giggles I deceided to look into pthread_spin_unlock

new: rp(4): RocketPort multi serial port pci card driver

Hi, The following diff contains a port of the FreeBSD driver for RocketPort PCI cards. The tty interface works with getty(8) and the cua part with cu for outbound connections. Some issues are still in, which I could not figure out yet. I worked on this driver for one and half year now, and

Re: Please test: switch select(2) to kqfilters

On 02/10/20(Fri) 19:09, Scott Cheloha wrote: > On Fri, Oct 02, 2020 at 12:19:35PM +0200, Martin Pieuchot wrote: > > @@ -635,12 +642,39 @@ sys_kevent(struct proc *p, void *v, regi > > goto done; > > } > > > > + > > KQREF(kq); > > FRELE(fp, p); > > - error =

Re: Make df output more human friendly in daily(8)

Hi Daniel, my OK still stands, except that you went too far in one respect in the manual page, see below. Yours, Ingo Daniel Jakots wrote on Fri, Oct 02, 2020 at 03:41:31PM -0400: > Index: share/man/man8/daily.8 > === > RCS