On Wed, 3 Oct 2018 11:36:53 +0200, Reyk Floeter wrote:
> On Tue, Oct 02, 2018 at 11:13:35PM -0700, Ori Bernstein wrote:
> > On Mon, 1 Oct 2018 11:24:01 -0700, Ori Bernstein
> > wrote:
> >
> > > On Mon, 1 Oct 2018 12:55:12 +0200
> > > Reyk Floeter wrote:
> > >
> > > > Hi Ori,
> > > >
> > > >
Attached is patch from netbsd for updated qcow definitions.
Comments? Ok?
+--+
Carlos
Index: msdos
===
RCS file: /home/los/cvs/src/usr.bin/file/magdir/msdos,v
retrieving revision 1.6
diff -u -p -r1.6 msdos
--- msdos 29 Jan 2016
Every few boots my bwfm device is not available. dmesg says:
bwfm0: timeout waiting for ioctl response
bwfm0: could not read io type
When this happens I reboot until the device is recognized again. dmesg says:
bwfm0 at pci10 dev 0 function 0 "Broadcom BCM43602" rev 0x01: msi
Is there a fix for
On Sat, Sep 29, 2018 at 10:44:41PM +0200, Klemens Nanni wrote:
> On Sat, Sep 29, 2018 at 06:17:05PM +0200, Fabian Mueller-Knapp wrote:
> > I have the following pf.conf:
> >
> > anchor quick {
> > pass
> > }
> > block
> >
> > # pfctl -sr
> > anchor quick all {
> > pass all flags S/SA
> > }
> >
* Mike Larkin [2018-10-03 12:19:09 -0700]:
How about this? pd, thoughts?
This code is just the rate limiter code.
Today the code says "have I reached the number of characters output based on
my baud rate that indicates I need to pause a bit?". And pausing after 0
characters has been output ma
On Wed, Oct 03, 2018 at 12:19:09PM -0700, Mike Larkin wrote:
> On Wed, Oct 03, 2018 at 12:13:05PM -0700, Mike Larkin wrote:
> > On Wed, Oct 03, 2018 at 12:06:47PM -0700, Pratik Vyas wrote:
> > > * Greg Steuck [2018-10-03 11:40:22 -0700]:
> > >
> > > > $ egdb /syzkaller/src/usr.sbin/vmd/obj/vmd /v
Thanks Pratik. I reverted my hack and applied your patch instead.
On Wed, Oct 03, 2018 at 12:13:05PM -0700, Mike Larkin wrote:
> On Wed, Oct 03, 2018 at 12:06:47PM -0700, Pratik Vyas wrote:
> > * Greg Steuck [2018-10-03 11:40:22 -0700]:
> >
> > > $ egdb /syzkaller/src/usr.sbin/vmd/obj/vmd /var/crash/vmd/38082.core
> > > Core was
On Wed, Oct 03, 2018 at 12:06:47PM -0700, Pratik Vyas wrote:
> * Greg Steuck [2018-10-03 11:40:22 -0700]:
>
> > $ egdb /syzkaller/src/usr.sbin/vmd/obj/vmd /var/crash/vmd/38082.core
> > Core was generated by `vmd'.
> > Program terminated with signal SIGFPE, Arithme
* Greg Steuck [2018-10-03 11:40:22 -0700]:
$ egdb /syzkaller/src/usr.sbin/vmd/obj/vmd /var/crash/vmd/38082.core
Core was generated by `vmd'.
Program terminated with signal SIGFPE, Arithmetic exception.
#0 0x0c07a64174a0 in vcpu_process_com_data (vei=,
vm_id
Since I don't understand how com1_dev.pause_ct can be zero, I'll hack
around the problem to keep the runs stable:
diff --git a/usr.sbin/vmd/ns8250.c b/usr.sbin/vmd/ns8250.c
index 74e86a92954..69957e38cce 100644
--- a/usr.sbin/vmd/ns8250.c
+++ b/usr.sbin/vmd/ns8250.c
@@ -237,7 +237,7 @@ vcpu_proces
On Wed, Oct 03, 2018 at 12:00:07PM -0700, Mike Larkin wrote:
> On Wed, Oct 03, 2018 at 11:40:22AM -0700, Greg Steuck wrote:
> > $ egdb /syzkaller/src/usr.sbin/vmd/obj/vmd /var/crash/vmd/38082.core
> > Core was generated by `vmd'.
> > Program terminated with signal
On Wed, Oct 03, 2018 at 11:40:22AM -0700, Greg Steuck wrote:
> $ egdb /syzkaller/src/usr.sbin/vmd/obj/vmd /var/crash/vmd/38082.core
> Core was generated by `vmd'.
> Program terminated with signal SIGFPE, Arithmetic exception.
> #0 0x0c07a64174a0 in vcpu_proces
Great minds think alike :) Thanks Carlos & Pratik. I just applied the patch
and will restart the fuzzer.
On Wed, Oct 3, 2018 at 11:37 AM Pratik Vyas wrote:
> * Greg Steuck [2018-10-03 10:56:28 -0700]:
>
> >Hi Mike,
> >
> >I'm getting core files from vmds. Here's the most recent one. Should I
>
$ egdb /syzkaller/src/usr.sbin/vmd/obj/vmd /var/crash/vmd/38082.core
Core was generated by `vmd'.
Program terminated with signal SIGFPE, Arithmetic exception.
#0 0x0c07a64174a0 in vcpu_process_com_data (vei=,
vm_id=, vcpu_id=)
at /syzkaller/src/usr.sbin/vm
* Greg Steuck [2018-10-03 10:56:28 -0700]:
Hi Mike,
I'm getting core files from vmds. Here's the most recent one. Should I
start collecting more stack traces and sending them to you?
ci-openbsd$ doas /usr/local/bin/egdb /syzkaller/src/usr.sbin/vmd/obj/vmd
/var/crash/vmd/89501.core
Reading sym
On Wed, Oct 03, 2018 at 10:56:28AM -0700, Greg Steuck wrote:
> Hi Mike,
>
> I'm getting core files from vmds. Here's the most recent one. Should I
> start collecting more stack traces and sending them to you?
>
> ci-openbsd$ doas /usr/local/bin/egdb /syzkaller/src/usr.sbin/vmd/obj/vmd
> /var/cras
Hi Mike,
I'm getting core files from vmds. Here's the most recent one. Should I
start collecting more stack traces and sending them to you?
ci-openbsd$ doas /usr/local/bin/egdb /syzkaller/src/usr.sbin/vmd/obj/vmd
/var/crash/vmd/89501.core
Reading symbols from /syzkaller/src/usr.sbin/vmd/obj/vmd..
On Wed, Oct 03, 2018 at 04:19:31PM +0200, Claudio Jeker wrote:
> I don't like how a lot of things got pushed into the global configuration
> section in bgpd.conf.5 especially since some bits should be their own
> sections. I see this for example for sets and for network statements.
>
> My proposal
On Wed, Oct 03, 2018 at 03:40:47PM +0100, Stuart Henderson wrote:
> On 2018/10/03 16:19, Claudio Jeker wrote:
> > I don't like how a lot of things got pushed into the global configuration
> > section in bgpd.conf.5 especially since some bits should be their own
> > sections. I see this for example
On 2018/10/03 16:19, Claudio Jeker wrote:
> I don't like how a lot of things got pushed into the global configuration
> section in bgpd.conf.5 especially since some bits should be their own
> sections. I see this for example for sets and for network statements.
>
> My proposal is to add two new se
I don't like how a lot of things got pushed into the global configuration
section in bgpd.conf.5 especially since some bits should be their own
sections. I see this for example for sets and for network statements.
My proposal is to add two new sections which gives us the following
structure:
> Date: Wed, 3 Oct 2018 14:28:41 +0200
> From: Patrick Wildt
>
> On Tue, Oct 02, 2018 at 06:07:22PM +0200, Mark Kettenis wrote:
> > > Date: Tue, 2 Oct 2018 17:24:42 +0200
> > > From: Patrick Wildt
> > >
> > > Hi,
> > >
> > > we already do have the sources for LLDB, the only thing left to do is
In one case (when a peer changes RIB) the RDE needs to withdraw all
prefixes of that peer and then during softreconfig it will load the
prefixes freshly form the new RIB. Since we now have a list of all
prefixes that have been sent to the peer use that one instead of doing a
full table walk over th
On Tue, Oct 02, 2018 at 06:07:22PM +0200, Mark Kettenis wrote:
> > Date: Tue, 2 Oct 2018 17:24:42 +0200
> > From: Patrick Wildt
> >
> > Hi,
> >
> > we already do have the sources for LLDB, the only thing left to do is
> > add the build infrastructure so that we actually compile all the
> > indep
On Wed, Oct 03, 2018 at 01:17:59PM +0200, Claudio Jeker wrote:
> On Wed, Oct 03, 2018 at 01:08:19PM +0200, Denis Fondras wrote:
> > Add a 'ovs' command to filter on Origin Validation State.
> >
> > 'bgpctl show rib ovs invalid' returns only prefixes that failed route origin
> > validation.
> >
>
On Wed, Oct 03, 2018 at 01:08:19PM +0200, Denis Fondras wrote:
> Add a 'ovs' command to filter on Origin Validation State.
>
> 'bgpctl show rib ovs invalid' returns only prefixes that failed route origin
> validation.
>
>
> Index: bgpctl/bgpctl.8
> ===
Add a 'ovs' command to filter on Origin Validation State.
'bgpctl show rib ovs invalid' returns only prefixes that failed route origin
validation.
Index: bgpctl/bgpctl.8
===
RCS file: /cvs/src/usr.sbin/bgpctl/bgpctl.8,v
retrieving r
On Tue, Oct 02, 2018 at 11:13:35PM -0700, Ori Bernstein wrote:
> On Mon, 1 Oct 2018 11:24:01 -0700, Ori Bernstein wrote:
>
> > On Mon, 1 Oct 2018 12:55:12 +0200
> > Reyk Floeter wrote:
> >
> > > Hi Ori,
> > >
> > > On Sun, Sep 30, 2018 at 12:27:00PM -0700, Ori Bernstein wrote:
> > > > I've add
29 matches
Mail list logo
