tweak ohci_checkrev output

2019-01-04 Thread David Gwynne
this makes the thing calling ohci_checkrev responsible for the preceding separator and white space. it helps ohci at fdt were we don't print an interrupt string out, it just follows the attach point. this is extremely lightly tested, so eyes are welcome. ok? Index: arch/loongson/dev/ohci_voyager

sbin/wsconsctl: show more data

2019-01-04 Thread Artturi Alm
Hi, guessing i'm not the only one wondering about these sizes, as w/current snapshot the font does seem too big for me(on 2560x1440 display, for which radeondrm(4) has never gotten the size right(giving only 1920x1200)). display.part of wsconsctl output w/the diff: display.type=radeondrm display.

Re: pfctl: tables: improve namespace collision warnings

2019-01-04 Thread Klemens Nanni
On Wed, Jan 02, 2019 at 11:27:18PM +0100, Alexandr Nedvedicky wrote: > I don't object your change. However I hesitate to give OK too. I hope PF > users, who have non-trivial rulesets will speak up here. Feedback is welcome. > IMO opinion we are hitting limitations of pfctl(8) here. Making warning

Re: unveil file(1)

2019-01-04 Thread Theo de Raadt
Ted Unangst wrote: > Theo de Raadt wrote: > > > unveil isn't really buying much if you pledge "rpath" immediately after, > > > so if you want just add another pledge here instead, that is fine. > > > > "rpath" is obviously cheaper than unveil of even 1 file. > > here is a diff that simply adds

Re: unveil file(1)

2019-01-04 Thread Bryan Steele
On Fri, Jan 04, 2019 at 11:52:05AM -0500, Ted Unangst wrote: > Theo de Raadt wrote: > > > unveil isn't really buying much if you pledge "rpath" immediately after, > > > so if you want just add another pledge here instead, that is fine. > > > > "rpath" is obviously cheaper than unveil of even 1 fil

Re: unveil file(1)

2019-01-04 Thread Ted Unangst
Theo de Raadt wrote: > > unveil isn't really buying much if you pledge "rpath" immediately after, > > so if you want just add another pledge here instead, that is fine. > > "rpath" is obviously cheaper than unveil of even 1 file. here is a diff that simply adds another pledge. the attack surface

vmd console freeze and locked (?) qcow2 image

2019-01-04 Thread Thomas L.
Hi, I am running -current and installed Arch Linux on vmd. Unfortunatly, after a while the vmd console freezes. I tried stoping the vm with vmctl stop, but it keept hanging (maybe related to the console hanging?). So I terminated the vm with vmctl stop -f. Now, the vm won't start up complaining t

Re: video(1) pledge (& updated kernel diff)

2019-01-04 Thread Matthieu Herrb
On Sun, Dec 30, 2018 at 12:14:58PM +0100, Sebastien Marie wrote: > On Sun, Dec 30, 2018 at 10:58:58AM +0100, Landry Breuil wrote: > > On Sat, Dec 29, 2018 at 09:30:22AM +0100, Sebastien Marie wrote: > > > On Fri, Dec 28, 2018 at 09:41:06PM +0100, Landry Breuil wrote: > > > > > > I would separate t

Re: teach arm64 to print unconfigured simplebus devices

2019-01-04 Thread Mark Kettenis
> Date: Thu, 3 Jan 2019 22:47:14 +1100 > From: Jonathan Gray > Cc: tech@openbsd.org > Content-Type: text/plain; charset="utf-8" > Content-Disposition: inline > > On Wed, Jan 02, 2019 at 04:08:53PM +1000, David Gwynne wrote: > > This makes it more obvious what interesting things there are to hack

Re: revised patch: tail(1) do not try to reopen stdin

2019-01-04 Thread Martijn van Duren
Committed, thanks. On 1/3/19 11:08 AM, leo_...@volny.cz wrote: > Alright, these ones get rid of is_stdin altogether. Isn't it better this > way? > >--zeurkous. > > Index: src/usr.bin/tail/extern.h > === > RCS file: /cvs/src

Re: revised patch: tail(1) do not try to reopen stdin

2019-01-04 Thread Todd C . Miller
On Thu, 03 Jan 2019 12:51:48 +0100, Martijn van Duren wrote: > On 1/3/19 11:08 AM, leo_...@volny.cz wrote: > > Alright, these ones get rid of is_stdin altogether. Isn't it better this > > way? > > > Looks OK to me, anyone else want to OK this? OK millert@ - todd

Re: unveil file(1)

2019-01-04 Thread Theo de Raadt
> Just saying "you should not do that" will not prevent any user to do it > anyway. That is not what I was saying. Most of us strive to write utilities in the most efficient way. We don't use system features in programs that don't require it. We write a sparing but sufficient userland. That's

Re: unveil file(1)

2019-01-04 Thread Theo de Raadt
> But, is the situation with unveil(2) worst that before ? It seems to me > a user could already doing vnode comsuption with just opening as many > file descriptors it can (and fork and repeat when RLIMIT_NOFILES is > reached for the process). No, it is a little different. An unveil is a tighter

rewrite of bgpd update code

2019-01-04 Thread Claudio Jeker
This is a major diff which replaces some old code of bgpd. Using the Adj-RIB-Out it is possible to replace the old code generating updates and queuing them in two RB trees with a RB tree of prefix elements. The big benefit of this is a lot less memeory pressure during large operations (e.g. when st

Re: ohci at fdt (for pine64)

2019-01-04 Thread Mark Kettenis
> From: David Gwynne > Date: Fri, 4 Jan 2019 08:54:17 +1000 > > > On 3 Jan 2019, at 20:54, Mark Kettenis wrote: > > > >> + /* Map and establish the interrupt. */ > >> + splassert(IPL_USB); > >> + sc->sc_ih = fdt_intr_establish(faa->fa_node, IPL_USB, > >> + ohci_intr, &sc->sc, devname);

Re: unveil file(1)

2019-01-04 Thread Sebastien Marie
Hi, First, for the specific case of file(1), I agree that calling "rpath" is what to do. No point to use unveil("/", "r"). On Thu, Jan 03, 2019 at 06:34:06PM -0700, Theo de Raadt wrote: > > You are abusing kernel resources. > if a userland program could be be crafted to abuse kernel resources,