ksh emacs search-history misbehaviour

2021-09-13 Thread Alexander Hall
in emacs search-history mode, abort if ^@ is encountered This has been bugging me for ages, and I finally realized it was me accidentally pressing Ctrl+, rendering ^@ (a.k.a '\0' or NUL) Easily tested with: Ctrl+R Ctrl+ ... Minimal investigation, for reference: bash: misbehaves in a slightly

Re: FIDO/U2F not working with latest snapshot

2021-09-13 Thread Mitchell Riedstra
> Thanks, the diff below should hopefully work as it corrects a > regression > introduced in uhidev_attach(). However, I'm not still convinced that > this is a good idea. The patch applies and works, though I noticed in uhidev_attach osize is being checked twice, was it meant to be fsize? ( patch

Re: riscv64: icache flush using sysarch(2)

2021-09-13 Thread Theo de Raadt
Mark Kettenis wrote: > Really depends on how the future riscv64 instructions behave. A valid > concern so the XXX is appropriate. But I would pass the address and > size to pmap_proc_iflush(). Yes, let the pmap decide what it wants to do.

Re: riscv64: icache flush using sysarch(2)

2021-09-13 Thread Mark Kettenis
> From: Jeremie Courreges-Anglas > Date: Mon, 13 Sep 2021 21:35:33 +0200 > > On Thu, Sep 09 2021, Mark Kettenis wrote: > >> From: Jeremie Courreges-Anglas > >> Date: Sun, 05 Sep 2021 21:41:35 +0200 > >> > >> On Sat, Sep 04 2021, Jeremie Courreges-Anglas wrote: > >> > The first problem I was

Re: riscv64: icache flush using sysarch(2)

2021-09-13 Thread Jeremie Courreges-Anglas
On Thu, Sep 09 2021, Mark Kettenis wrote: >> From: Jeremie Courreges-Anglas >> Date: Sun, 05 Sep 2021 21:41:35 +0200 >> >> On Sat, Sep 04 2021, Jeremie Courreges-Anglas wrote: >> > The first problem I was able to diagnose using egdb on riscv was >> > lang/python/2.7 using libffi and aborting

Re: teach pf to refragment ipv4 packets

2021-09-13 Thread Alexander Bluhm
On Wed, Sep 01, 2021 at 08:08:48AM +1000, David Gwynne wrote: > I guess the overall question is if an IPv4 packet size is a hop by hop > thing, or whether the endpoints should have final say about what they're > prepared to deal with. You are moving the layer 2 MTU size configuration to the