Re: inteldrm(4) fix

2019-12-17 Thread Philip Guenther
On Tue, Dec 17, 2019 at 5:02 AM Mark Kettenis wrote: > Hit the > > KASSERT(curcpu()->ci_inatomic == 0); > > in pagefault_disable(). Analysis of the code in i915_gem_execbuffer.c > shows that pagefault_disable() may be called when page faults are > already disabled, i.e. from

Re: openssl.1: note default -md value for openssl enc and how to get list of available hashes

2019-12-17 Thread Fabio Scotoni
On 12/18/19 5:46 AM, Theo Buehler wrote: > The diff modifies the CA section, not ENC. I need to check if we can > do something about the weak defaults there, but the diff is not > correct. That's my bad. New diff inline. > For ENC, it's indeed correct that the default was changed from md5 to >

Re: openssl.1: note default -md value for openssl enc and how to get list of available hashes

2019-12-17 Thread Theo Buehler
On Mon, Dec 16, 2019 at 07:15:15PM +0100, Fabio Scotoni wrote: > This diff changes the documentation of openssl(1) enc to note the > default value (sha256) and replace the "hardcoded" list of md5, sha1 > with instructions to use list-message-digest-algorithms instead. The diff modifies the CA

midi(4): *sleep(9) -> *sleep_nsec(9)

2019-12-17 Thread Scott Cheloha
The only conversion I'm having trouble with is the tsleep(). The comment says "20ms", but then we use some arithmetic to derive a count of ticks. Given hz * MIDI_MAXWRITE / MIDI_RATE You have hz ticks/second, and 32 bytes, and 3125 bytes/second, so you have hz ticks 32 bytes

Re: attention please: host's IP stack behavior got changed slightly

2019-12-17 Thread Alexander Bluhm
On Mon, Dec 16, 2019 at 03:42:27PM +0100, Alexandr Nedvedicky wrote: > > I think this is a "do as I want" kind of thing. If I use pf(4) to redirect > > traffic to a different address then I think our version of strict host > > model should step back and accept the connection. > > and also the

Re: NSD update to 4.2.4

2019-12-17 Thread Stuart Henderson
Unless there are objections or requests for more time to review, I plan to commit the NSD and Unbound updates tomorrow.

Re: usbhidaction(1) with a foot pedal/control

2019-12-17 Thread Theo de Raadt
Reyk Floeter wrote: > > 1. Shall I *simply* introduce chmod(1)/chown(8) step in the above script? > > > > Yes, this is what I recommend. The good thing is that your script > already knows the exact uhid device of your footpedal, so doing a > chmod/chown for this will not automatically open

Re: usbhidaction(1) with a foot pedal/control

2019-12-17 Thread Reyk Floeter
Hi, On Tue, Dec 17, 2019 at 06:57:54PM +, Raf Czlonka wrote: > I use a Philips USB foot pedal[0] as an additional input device. > With usbhidaction(1), I can "program" its four "buttons". > > After recent changes to uhid(4) device nodes' permissions, my USB > foot pedal "stopped working". >

Re: usbhidaction(1) with a foot pedal/control

2019-12-17 Thread Theo de Raadt
Raf Czlonka wrote: > Hi all, > > I use a Philips USB foot pedal[0] as an additional input device. > With usbhidaction(1), I can "program" its four "buttons". > > After recent changes to uhid(4) device nodes' permissions, my USB > foot pedal "stopped working". > > I understand that it is a

usbhidaction(1) with a foot pedal/control

2019-12-17 Thread Raf Czlonka
Hi all, I use a Philips USB foot pedal[0] as an additional input device. With usbhidaction(1), I can "program" its four "buttons". After recent changes to uhid(4) device nodes' permissions, my USB foot pedal "stopped working". I understand that it is a *very recent* change but I rely on this

Re: Potential fix for fsck on ext2 rev1 filesystems

2019-12-17 Thread Todd C . Miller
On Tue, 17 Dec 2019 18:11:17 +, Chris Waddey wrote: > Long story short, it seems that a call to memset was writing zeros over > the curino structure because the rev1 inode structure takes up 256 bytes > on disk but only 156 in memory. I assume that the patch below (which > worked fine on my

Re: Potential fix for fsck on ext2 rev1 filesystems

2019-12-17 Thread Chris Waddey
Except my the 's in the diff are supposed to be &'s. Index: pass2.c === RCS file: /cvs/src/sbin/fsck_ext2fs/pass2.c,v retrieving revision 1.15 diff -u -p -r1.15 pass2.c --- pass2.c 28 Apr 2016 12:17:15 - 1.15 +++ pass2.c

Re: openssl.1: note default -md value for openssl enc and how to get list of available hashes

2019-12-17 Thread Jason McIntyre
On Mon, Dec 16, 2019 at 07:15:15PM +0100, Fabio Scotoni wrote: > This diff changes the documentation of openssl(1) enc to note the > default value (sha256) and replace the "hardcoded" list of md5, sha1 > with instructions to use list-message-digest-algorithms instead. > i'm happy to commit this

Potential fix for fsck on ext2 rev1 filesystems

2019-12-17 Thread Chris Waddey
Hello all. I while back I put an ext2 rev1 filesystem on my disk (not sure why any more, but oh well). Whenever fsck ran, it stopped during pass2 with the error message "wrong type to dirscan 0". Long story short, it seems that a call to memset was writing zeros over the curino structure because

unwind(8): more unified caches & memory reporting

2019-12-17 Thread Florian Obser
This unifies the neg and key caches and adds unwindctl status memory. Please test with your normal workload and report back unwindctl status and unwindctl status memory after maybe a days usage. OK? commit eb2d659a831106f3ff1e62e7cdd8dc8bc13fd9f2 Author: Florian Obser Date:

inteldrm(4) fix

2019-12-17 Thread Mark Kettenis
Hit the KASSERT(curcpu()->ci_inatomic == 0); in pagefault_disable(). Analysis of the code in i915_gem_execbuffer.c shows that pagefault_disable() may be called when page faults are already disabled, i.e. from eb_relocate_slow() where eb_relocate_vma() is called after pagefault_disable().