On Tue, Oct 23, 2018 at 11:15:39PM -0700, Ayaka Koshibe wrote:
> Hi all,
>
> I've taken claudio@'s advice and restricted the pledge further. All of the
> promises except stdio were for parsing args and opening sockets.
>
> OK?
OK claudio@
>
> Thanks,
> Ayaka
>
>
> Index: switchctl.c
> =
This may have been broken for quite some time...
Fix usage message for "show ip bgp in/out" and add missing "neighbor" argument.
Index: bgplg.h
===
RCS file: /cvs/src/usr.bin/bgplg/bgplg.h,v
retrieving revision 1.14
diff -u -p -r1.14
Hi all,
I've taken claudio@'s advice and restricted the pledge further. All of the
promises except stdio were for parsing args and opening sockets.
OK?
Thanks,
Ayaka
Index: switchctl.c
===
RCS file: /cvs/src/usr.sbin/switchctl/sw
On Tue, Oct 23, 2018 at 09:53:48PM +, Adam Steen wrote:
> Hi tech
>
> The following diff allows vmd to specify which ports it can handle
> or fix "XXX something better than a hardcoded list here, maybe configure via
> vmd via the device list in vm create params?"
>
> There are currently two i
On Mon, 8 Oct 2018 07:59:15 -0700, Bob Beck wrote:
> works here and I like it. but probably for after unlock
>
It's after unlock -- pinging for OKs.
--
Ori Bernstein
This patch turns most warnings into errors, and uses the
appropriate fatal/fatalx so that we don't print bogus error
strings. It also adds checks for unsupported refcount sizes
and writes that clobber the header.
Ok?
diff --git usr.sbin/vmd/vioqcow2.c usr.sbin/vmd/vioqcow2.c
index 3a215599d49..e5
Hi tech
The following diff allows vmd to specify which ports it can handle
or fix "XXX something better than a hardcoded list here, maybe configure via
vmd via the device list in vm create params?"
There are currently two implementation of bsearch in the kernel and this patch
would add a third, I
I ran across this:
$ readelf -h /usr/local/bin/w3m
...
readelf(71968) in free(): bogus pointer (double free?) 0x1
Abort trap (core dumped)
In readelf.c there's a static arrary:
static bfd_vma dynamic_info[DT_JMPREL + 1];
Later this array is written to like this:
switch (entry->d_ta
Hi Mark,
On Tue, Oct 23, 2018 at 07:32:16PM +0200, Mark Kettenis wrote:
> > Date: Tue, 23 Oct 2018 18:40:42 +0200
> > From: Jan Klemkow
> > On Mon, Oct 22, 2018 at 09:45:06PM +0200, Mark Kettenis wrote:
> > > Diff below adds an acpipci(4) driver on amd64. For now the main
> > > purpose of this d
> Date: Tue, 23 Oct 2018 18:40:42 +0200
> From: Jan Klemkow
>
> Hi Mark,
>
> On Mon, Oct 22, 2018 at 09:45:06PM +0200, Mark Kettenis wrote:
> > Diff below adds an acpipci(4) driver on amd64. For now the main
> > purpose of this driver is to make the PCI-specific _OSC calls to
> > advertise the
> > Had the diff below in my tree for a very long time. Switch several
> > uvm_km_alloc()/uvm_km_valloc() calls over to km_alloc().
> >
> > ok?
> >
>
> ok but there is a knf spacing issue (end-pa). other than that nit, ok mlarkin
>
tested to work fine on amd64.
thanks
Not that I expected anything to change considering the patches submitted,
but Oct 21 snapshot (minus "Add support to create and convert disk images
from existing images") is similarly afflicted. Any candidate fixes or
patches for added logging will be put to test in short order :)
ci-openbsd$ dmes
Hi Mark,
On Mon, Oct 22, 2018 at 09:45:06PM +0200, Mark Kettenis wrote:
> Diff below adds an acpipci(4) driver on amd64. For now the main
> purpose of this driver is to make the PCI-specific _OSC calls to
> advertise the functionality we support. Most notably this advertises
> support for PCIE n
On Mon, Oct 22, 2018 at 09:45:06PM +0200, Mark Kettenis wrote:
> Diff below adds an acpipci(4) driver on amd64. For now the main
> purpose of this driver is to make the PCI-specific _OSC calls to
> advertise the functionality we support. Most notably this advertises
> support for PCIE native hotp
Hello
I just adapted the patch for 6.4 stable (for small failed hunks) and
recompiled/rebooted the kernel.
Thinkpad X1 Carbon 5th Gen, same changes in dmesg as phessler :
...
+acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x
...
(let me know if you want both as they're the same as his lapt
Hi,
When spamd runs in greylist mode the parent process (which runs greywatcher())
we know that the only files that it will ever access are PATH_SPAMD_DB in rw,
alloweddomains_file in r and that it will need to exec PATH_PFCTL so we can
unveil them with those permissions.
All other necessary file
On 2018 Oct 22 (Mon) at 21:45:06 +0200 (+0200), Mark Kettenis wrote:
:Diff below adds an acpipci(4) driver on amd64. For now the main
:purpose of this driver is to make the PCI-specific _OSC calls to
:advertise the functionality we support. Most notably this advertises
:support for PCIE native ho
On Mon, Oct 22, 2018 at 11:54:34PM -0700, Ori Bernstein wrote:
> On Mon, 22 Oct 2018 22:57:39 -0700, Ori Bernstein wrote:
>
> > While I'm at it, this patch fixes up a few nits around logging, where
> > warn was used instead of warnx, leading to some bogus error strings
> > being printed, and adds
On Sun, Oct 21, 2018 at 01:51:52PM +0200, Claudio Jeker wrote:
> On Thu, Oct 18, 2018 at 02:29:17PM +0200, Claudio Jeker wrote:
> > Change the way ribs are porcessed. Currently all async dumpers have to
> > call rib_dump_r() whenever progress should be made. Also creating the
> > context for such a
On Mon, Oct 22, 2018 at 11:54:34PM -0700, Ori Bernstein wrote:
> On Mon, 22 Oct 2018 22:57:39 -0700, Ori Bernstein wrote:
>
> > While I'm at it, this patch fixes up a few nits around logging, where
> > warn was used instead of warnx, leading to some bogus error strings
> > being printed, and adds
20 matches
Mail list logo
