Re: MSI-X support

On 4.5.2016. 8:50, Mark Kettenis wrote: >> Date: Tue, 3 May 2016 15:23:07 -0700 >> From: Mike Larkin >> >> On Tue, May 03, 2016 at 09:40:28PM +0200, Mark Kettenis wrote: >>> Today mpi@ reminded me that I had written support for MSI-X some time >>> ago. Since he is

Preserve DiffServ when fragmenting ipv4

When fragmenting ipv4, we do not preserve DiffServ/ToS field. Here is how to observe this : [obsd1](vlan10) (vlan10)[obsd2](vlan20) --mtu600-- (vlan20)[obsd3] root@obsd2 # sysctl net.inet.ip.forwarding=1 root@obsd2 # tcpdump -ni $VLAN20DEV user@obsd3 $ nc -4ul root@obsd1 $ echo "pass

Re: midiplay: Fix out-of-bounds memory access

On Sun, May 01, 2016 at 12:53:17PM +0300, Vadim Zhukov wrote: > 2016-04-30 7:38 GMT+03:00 Jonathan Gray : > > On Wed, Apr 27, 2016 at 07:49:50PM -0700, Geoff Hill wrote: > >> Fix possible reads past the end of the buffer. > >> > >> Found by random fuzz testing (zzuf). Without the

Re: MSI-X support

On Tue, May 03, 2016 at 21:40 +0200, Mark Kettenis wrote: > Today mpi@ reminded me that I had written support for MSI-X some time > ago. Since he is interested in using multiple vectors, I extended the > code I had a bit to support that feature as well. This introduces a > new function: > > int

Re: MSI-X support

On Wed, May 04, 2016 at 04:01:54PM +0200, Mike Belopuhov wrote: > On Tue, May 03, 2016 at 21:40 +0200, Mark Kettenis wrote: > > Today mpi@ reminded me that I had written support for MSI-X some time > > ago. Since he is interested in using multiple vectors, I extended the > > code I had a bit to

vm.conf.5 - number of sections

It seems that there are only two sections. It looks like this mistake was introduced when copying a different .conf.5 file to use as a template. Index: usr.sbin/vmd/vm.conf.5 === RCS file: /cvs/src/usr.sbin/vmd/vm.conf.5,v retrieving

Re: FW: Re: watchdog suport for new hardware

It looks like other devices have: Name (_HID, EisaId ("PNP0501") instead of: Name (_HID, "SEL0002") I'm not sure what the significance of EisaId is, but it doesn't show up for our device. On Wed, May 4, 2016 at 9:34 AM, Chase Davis wrote: > Mike, > > Yes I think that it is

Re: vm.conf.5 - number of sections

On Wed, May 04, 2016 at 02:21:50PM +0200, Michal Mazurek wrote: > It seems that there are only two sections. It looks like this mistake > was introduced when copying a different .conf.5 file to use as a template. > > Index: usr.sbin/vmd/vm.conf.5 >

Re: FW: Re: watchdog suport for new hardware

On Wed, May 04, 2016 at 07:26:15AM -0500, Chase Davis wrote: > This was added to GENERIC: > > sel* at acpi? > > and these four lines were added to files.acpi: > # SEL embedded controller > device sel > attach sel at acpi with sel_acpi > file dev/acpi/sel_acpi.c sel_acpi > > With SEL0002 being

Re: MSI-X support

On Wed, May 04, 2016 at 08:50:53AM +0200, Mark Kettenis wrote: > > Date: Tue, 3 May 2016 15:23:07 -0700 > > From: Mike Larkin > > > > On Tue, May 03, 2016 at 09:40:28PM +0200, Mark Kettenis wrote: > > > Today mpi@ reminded me that I had written support for MSI-X some time >

Re: anti-ROP mechanism in libc

This gives me an idea for how to solve the lack of a first-stage bootloader (like biosboot(8)) on armv7. Currently U-Boot loads the kernel image directly into memory and jmp's to its entry point without an intermediary stage to read /etc/random.seed from disk and provide it to the kernel to

Re: FW: Re: watchdog suport for new hardware

> Date: Wed, 4 May 2016 09:41:18 -0500 > From: Chase Davis > > It looks like other devices have: Name (_HID, EisaId ("PNP0501") > instead of: Name (_HID, "SEL0002") > > I'm not sure what the significance of EisaId is, but it doesn't show > up for our device. Shouldn't be

Re: midiplay: Fix out-of-bounds memory access

On Wed, May 04, 2016 at 02:01:57PM +0200, Alexandre Ratchov wrote: > On Sun, May 01, 2016 at 12:53:17PM +0300, Vadim Zhukov wrote: > > 2016-04-30 7:38 GMT+03:00 Jonathan Gray : > > > On Wed, Apr 27, 2016 at 07:49:50PM -0700, Geoff Hill wrote: > > >> Fix possible reads past the end

Re: anti-ROP mechanism in libc

On Wed, May 04, 2016 at 08:28:41PM -0400, Ian Sutton wrote: > This gives me an idea for how to solve the lack of a first-stage > bootloader (like biosboot(8)) on armv7. Currently U-Boot loads the > kernel image directly into memory and jmp's to its entry point without > an intermediary stage to

Re: DMA overruns and iommu's

> From: "Ted Unangst" > Date: Mon, 02 May 2016 14:35:05 -0400 > > Mark Kettenis wrote: > > It is pretty clear that the DMA engine on the Davicom dc(4) hardware > > is broken and will read beyond the end of the buffer that we pass it. > > This is bad news for hardware that

Re: MSI-X support

> Date: Wed, 4 May 2016 07:14:15 -0700 > From: Mike Larkin > > On Wed, May 04, 2016 at 04:01:54PM +0200, Mike Belopuhov wrote: > > On Tue, May 03, 2016 at 21:40 +0200, Mark Kettenis wrote: > > > Today mpi@ reminded me that I had written support for MSI-X some time > > >

Re: FW: Re: watchdog suport for new hardware

> Date: Wed, 4 May 2016 15:00:03 -0500 > From: Chase Davis > > Forgive my ignorance, but what bearing does -release and -current have > on whether or not the HID is found by the match function? Because the code that the HID matching depends on was reworked after 5.9 was

Re: FW: Re: watchdog suport for new hardware

Makes perfect sense. Thanks for all the help. I will make sure that we are using release. Is there any other reason you could think of why match wouldn't work if SEL0002 shows up in the DSDT table? On Wed, May 4, 2016 at 3:25 PM, Mark Kettenis wrote: >> Date: Wed, 4 May

Re: bpf device nodes

On Tue, May 03, 2016 at 05:09:47AM -0600, Theo de Raadt wrote: > > On 2016-04-27, Martin Natano wrote: > > > > > /dev/bpf0 is for compatibility with existing binaries and is to > > > be removed after a transition period. > > > > What's the impact on ports going to be? > > >

enable shadow only pwd

i think it's time. otherwise we'll never find the bugs. Index: gen/getpwent.c === RCS file: /cvs/src/lib/libc/gen/getpwent.c,v retrieving revision 1.60 diff -u -p -r1.60 getpwent.c --- gen/getpwent.c 28 Dec 2015 22:08:18 -

Re: sed/regcomp bug?

Hello tech@, On 04/23/16 07:21, Jonathan Gray wrote on bugs@: > $ cat foo.sh > #!/bin/sh > > $1 -r ' > s/[[:space:]]//g > s/\ ' > $ cat foo.csv > R32G32B32A32_FLOAT , 128, 1, 1, 1, sf32, sf32, sf32, sf32, , >,, linear, > $ ./foo.sh sed <

Re: FW: Re: watchdog suport for new hardware

Forgive my ignorance, but what bearing does -release and -current have on whether or not the HID is found by the match function? On Wed, May 4, 2016 at 9:58 AM, Mark Kettenis wrote: >> Date: Wed, 4 May 2016 09:41:18 -0500 >> From: Chase Davis >> >>

Re: MSI-X support

> Date: Tue, 3 May 2016 15:23:07 -0700 > From: Mike Larkin > > On Tue, May 03, 2016 at 09:40:28PM +0200, Mark Kettenis wrote: > > Today mpi@ reminded me that I had written support for MSI-X some time > > ago. Since he is interested in using multiple vectors, I extended the

Re: FW: Re: watchdog suport for new hardware

>Forgive my ignorance, but what bearing does -release and -current have >on whether or not the HID is found by the match function? This is a body of source code that changes rapidly.

Re: bpf device nodes

>Yes, this also is what NetBSD and FreeBSD do, although I do hope >/dev/bpf0 can be removed some time in the future. then you need to go do a ports audit; almost assuredly, prepare yourself for disillusionment. don't do it now. do it in a year.

Re: FW: Re: watchdog suport for new hardware

> Authentication-Results: xs4all.nl; spf=pass smtp.mailfrom=gmail.com; > dkim=pass header.d=gmail.com; dmarc=pass header.from=gmail.com > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20120113; >