Re: tftpd(8): diff for ip path rewrite

2017-10-20 Thread Jeremie Courreges-Anglas
On Fri, Oct 20 2017, Sebastien Marie wrote: > On Thu, Oct 19, 2017 at 08:58:12PM +0200, Jan Klemkow wrote: >> >> Index: tftpd.c >> === >> RCS file: /mount/openbsd/cvs/src/usr.sbin/tftpd/tftpd.c,v >> retrieving

Re: tftpd(8): diff for ip path rewrite

2017-10-20 Thread Jeremie Courreges-Anglas
On Thu, Oct 19 2017, Stuart Henderson wrote: > On 2017/10/19 16:22, Theo de Raadt wrote: >> I am always worried by non-intuitive magic behaviour. >> >> It may serve some obvious purposes, but for someone else it is going >> to break things. >> >> I worry. > > The

Re: Refactor TCP partial ACK handling

2017-10-20 Thread Klemens Nanni
On Fri, Oct 20, 2017 at 09:07:20PM +0200, Mike Belopuhov wrote: > This is a small and not intrusive refactoring of partial ACK handling > but it certainly doesn't look like one. It's intended to be applied > after the TCP SACK diff that I've sent earlier and basically moves the > conditional

Re: proctreelk

2017-10-20 Thread Martin Pieuchot
On 14/10/17(Sat) 22:07, Philip Guenther wrote: > > The diff below adds proctreelk, an rwlock protecting the links of the > process tree and related bits, as well as uidinfolk, an rwlock protecting > the uidinfo hash table. > > Parts of this are based on FreeBSD's proctree_lock, particularly

Re: gas dwarf2 support

2017-10-20 Thread Mark Kettenis
> Date: Mon, 16 Oct 2017 00:26:10 +0200 (CEST) > From: Mark Kettenis > > The diff below implements a few more CFI directives in order to be > able to build clang on sparc64. > > ok? ping? I'd like to get this in early in the cycle just in case this produces some

Re: Please test: IPsec w/o KERNEL_LOCK()

2017-10-20 Thread Klemens Nanni
On Mon, Oct 16, 2017 at 12:47:06PM +0200, Martin Pieuchot wrote: > On 11/10/17(Wed) 17:01, Martin Pieuchot wrote: > > OpenBSD 6.2 includes nice performance and latency improvements due to > > the work done in the Network Stack in the previous years. However as > > soon as IPsec is enabled, all

close cron sockets in child processes

2017-10-20 Thread Florian Riehm
Hi, cron(8) opens /var/run/cron.sock for communication with crontab(1). The forked cronjobs have the socked still open. This prevents restarting cron while a job is running: (CRON) DEATH (already running) I think cron's children should not inherit sockets. ok? friehm Index:

Re: close cron sockets in child processes

2017-10-20 Thread Jeremie Courreges-Anglas
On Fri, Oct 20 2017, Florian Riehm wrote: > Hi, > > cron(8) opens /var/run/cron.sock for communication with crontab(1). > The forked cronjobs have the socked still open. > This prevents restarting cron while a job is running: > (CRON) DEATH (already running) Hah. > I think

Re: close cron sockets in child processes

2017-10-20 Thread Todd C. Miller
On Fri, 20 Oct 2017 16:25:32 +0200, Florian Riehm wrote: > cron(8) opens /var/run/cron.sock for communication with crontab(1). > The forked cronjobs have the socked still open. > This prevents restarting cron while a job is running: > (CRON) DEATH (already running) > > I think cron's children

Refactor TCP partial ACK handling

2017-10-20 Thread Mike Belopuhov
This is a small and not intrusive refactoring of partial ACK handling but it certainly doesn't look like one. It's intended to be applied after the TCP SACK diff that I've sent earlier and basically moves the conditional (SEQ_LT(th->th_ack, tp->snd_last)) out of tcp_sack_partialack and