pthread signal delivery

Hi, When killing a process, the signal is handled by any thread that does not block the signal. If all threads block the signal, we currently deliver it to the main thread. This does not conform to POSIX. If any thread unblocks the signal, it should be delivered immediately to this thread. We

Re: switch(4): add support for protected domains

Ayaka Koshibe(akosh...@openbsd.org) on 2019.05.09 15:56:49 -0700: > Hi, > > The following adds port protection support to switch(4). The behavior > copies that of bridge(4), where ports can be added to up to 31 protected > domains with a list of IDs using ifconfig(8): > > # ifconfig switch0

switch(4): add support for protected domains

Hi, The following adds port protection support to switch(4). The behavior copies that of bridge(4), where ports can be added to up to 31 protected domains with a list of IDs using ifconfig(8): # ifconfig switch0 protected pair1 1,2,.. Domain membership is checked for unicast, flooded

sysupgrade: tweak verbosity

Tweak sysupgrade's verbosity: * If we are verifying old sets, say so. This is not an instaneous operation. * Only say that we are verifying the (newly downloaded) sets, if we're actually doing so. OK? # rm /home/_sysupgrade/x*.tgz # sysupgrade -knf SHA256.sig 100%

KASSERT(9) header

All the places using KASSERT(9) include and not libkern.h. Shouldn't we recommend that? Index: KASSERT.9 === RCS file: /cvs/src/share/man/man9/KASSERT.9,v retrieving revision 1.1 diff -u -p -r1.1 KASSERT.9 --- KASSERT.9 19 Apr

Re: [patch] improve strptime(3) %z timezone parsing

Ingo Schwarze wrote: > I'm not mixing anything else into this diff. The other bugs should > be handled separately. > > OK? Works for me. (with additional comment removal)

Re: inteldrm: Use "the flush page mechanism" only on chips having it.

On Thu, May 09, 2019 at 10:26:52PM +1000, Jonathan Gray wrote: > On Thu, May 09, 2019 at 07:45:37AM +0200, Alexandre Ratchov wrote: > > In the intel_gtt_chipset_setup() routine, called at initialization, > > the driver maps pci space for certain chip models only, but later in > >

Re: [patch] improve strptime(3) %z timezone parsing

On Thu, May 09, 2019 at 08:38:43PM +0200, Ingo Schwarze wrote: > Hi, > > Theo de Raadt wrote on Sun, Mar 24, 2019 at 12:48:03PM -0600: > > Hiltjo Posthuma wrote: > >> On Sun, Feb 24, 2019 at 01:11:39PM +0100, Hiltjo Posthuma wrote: > > >>> 2. The military/nautical UTC offsets are [...] > >

Re: relayd: add from/to filter options

ok Reyk Floeter(r...@openbsd.org) on 2019.05.09 19:27:31 +0200: > Hi, > > the relayd code already had a few bits for from/to specifiers in > filter rules, but it wasn't finished. I did get occasional requests > if it would be possible to filter based on IPs (much like Allow/Deny > rules

Re: [patch] improve strptime(3) %z timezone parsing

Hi, Theo de Raadt wrote on Sun, Mar 24, 2019 at 12:48:03PM -0600: > Hiltjo Posthuma wrote: >> On Sun, Feb 24, 2019 at 01:11:39PM +0100, Hiltjo Posthuma wrote: >>> 2. The military/nautical UTC offsets are [...] broken by design. >> As discussed previously for point 2 I think it is fine to

sysupgrade: keep sets after upgrade

Add a -k flag to sysupgrade to keep the files in /home/_sysupgrade, since they will be deleted after the upgrade by default. Florian already added the installer part yesterday. OK? Index: sysupgrade.8 === RCS file:

relayd: add from/to filter options

Hi, the relayd code already had a few bits for from/to specifiers in filter rules, but it wasn't finished. I did get occasional requests if it would be possible to filter based on IPs (much like Allow/Deny rules elsewhere). Simple blocking should better be done in pf but the purpose of this is

Re: [patch] remove reference to HOSTALIASES in hostname(7)

Hi, Theo de Raadt wrote on Mon, Apr 15, 2019 at 12:56:35PM -0600: > Hiltjo Posthuma wrote: >> I noticed the man page hostname(7) still references the environment >> variable HOSTALIASES. This functionality seems to be removed in the >> commit: >>

bgpd, filterstate can never be NULL so don't check for it

This is cleanup. rde_filter() and rde_apply_set() are no longer called with a NULL filterstate (since introduction of the Adj-RIB-Out). So remove all those extra checks to make sure state is not NULL. -- :wq Claudio Index: rde_filter.c

Re: inteldrm: Use "the flush page mechanism" only on chips having it.

> Date: Thu, 9 May 2019 22:26:52 +1000 > From: Jonathan Gray > > On Thu, May 09, 2019 at 07:45:37AM +0200, Alexandre Ratchov wrote: > > In the intel_gtt_chipset_setup() routine, called at initialization, > > the driver maps pci space for certain chip models only, but later in > >

Re: stack trace / free(0) in isascan()

Sebastien Marie wrote: > > So calling free() with cf->cf_attach->ca_devsize should be fine. > Diff below. ok. didn't get to this one yet.

Re: Reorder comic fonts used in error pages for httpd(8) and relayd(8)

Thanks for your patch! So we have to figure out if people prefer the new fonts or the classic Comic Sans MS font. It is style vs. authenticity. But I think your suggestion is OK. Reyk > Am 09.05.2019 um 15:34 schrieb Nathan Galt : > > I happened upon ,

Reorder comic fonts used in error pages for httpd(8) and relayd(8)

I happened upon , currently a 404 Not Found page, and noticed that its font ordering was odd. While I appreciate the httpd author's attempt to inject a bit of fun into error pages, the ordering of the fonts in the font-family property could be improved.

relayd: SNI

Hi, this diff adds SNI support to relayd. It is a bit big and I have to break it down, but I'm sending this first version now to give people a chance to test. The major "infrastructure" change is that keypairs are not stored in relay structs anymore but in a global list where each keypair

less(1) UTF-8 cleanup: cmd_putstr()

Hi, let's start tackling the last file which is using stuff from charset.c: the file cmdbuf.c. The first dirty function is cmd_putstr(). Fortunately, it doesn't actually need to handle non-ASCII characters. The function cmd_putstr() is called only from command.c. Almost all callers pass literal

Re: stack trace / free(0) in isascan()

On 9.5.2019. 11:14, Sebastien Marie wrote: > On Thu, May 09, 2019 at 10:55:44AM +0200, Hrvoje Popovski wrote: >> >> with this diff i'm getting new traces > > it is (somehow) expected. > > the commit that starts showing traces do the following: > - when there is missing size on free() reports it

Re: inteldrm: Use "the flush page mechanism" only on chips having it.

On Thu, May 09, 2019 at 07:45:37AM +0200, Alexandre Ratchov wrote: > In the intel_gtt_chipset_setup() routine, called at initialization, > the driver maps pci space for certain chip models only, but later in > intel_gtt_chipset_flush() it calls bus_space_write() on it in cases > it's not

Re: less discriminatory battlestar

Ted Unangst(t...@tedunangst.com) on 2019.05.08 23:39:30 -0400: > there are lists of annointed usernames in battlestar. this creates an unfair > playing field! worse, there is a list of "bad" people! and i'm almost one of > them! ok, but i think you need krw@ to ok it too. > -static const char

Re: stack trace / free(0) in isascan()

On Thu, May 09, 2019 at 10:55:44AM +0200, Hrvoje Popovski wrote: > > with this diff i'm getting new traces it is (somehow) expected. the commit that starts showing traces do the following: - when there is missing size on free() reports it (with a backtrace to know the caller) - but report only

Re: stack trace / free(0) in isascan()

On 9.5.2019. 10:35, Sebastien Marie wrote: > On Thu, May 09, 2019 at 10:12:49AM +0200, Hrvoje Popovski wrote: >> Hi all, >> >> i update kernel from cvs few minutes ago and i'm seeing this stack trace >> in dmesg. i'm just reporting it. > > The principe of the game is to look at the free() call

Re: stack trace / free(0) in isascan()

On Thu, May 09, 2019 at 10:12:49AM +0200, Hrvoje Popovski wrote: > Hi all, > > i update kernel from cvs few minutes ago and i'm seeing this stack trace > in dmesg. i'm just reporting it. The principe of the game is to look at the free() call that still use 0 as size, and found the right size to

stack trace

Hi all, i update kernel from cvs few minutes ago and i'm seeing this stack trace in dmesg. i'm just reporting it. free with zero size: (2) Starting stack trace... free(80074100,2,0,80074100,1d5a05b47900fbf4,81d287e8) at free+0xd8

Re: [patch] cwm: filter duplicate hostnames in ssh menu

* Landry Breuil le [06-05-2019 09:45:08 +0200]: > On Mon, May 06, 2019 at 08:04:02AM +0200, Bruno Flückiger wrote: > > On 01.05., Marcus MERIGHI wrote: > > > Hello, > > > > > > o...@demirmen.com (Okan Demirmen), 2019.04.29 (Mon) 16:19 (CEST): > > > > On Fri 2019.04.26 at 07:15 +0200, Bruno