Hello -
I noticed some negative roundtrip times when running traceroute, which
uses the monotonic clock to calculate the RTT.
If I run the following code, it eventually bombs. It bombs quick if I
launch Firefox.
timespeccmp failed
tp1 s:103780 n:63101042
tp2 s:103779 n:761117849
#
Hello,
On Wed, Jun 05, 2019 at 10:50:18AM -0300, Martin Pieuchot wrote:
> On 04/06/19(Tue) 23:57, Alexandr Nedvedicky wrote:
> > Hello,
> >
> > I see, I owe some clarification to share wider context of this change.
> >
> > On Tue, Jun 04, 2019 at 10:32:57AM -0300, Martin Pieuchot wrote:
> > > On
Christian Weisgerber:
> > To reproduce:
> >
> > mkdir -p /tmp/test /tmp/plop
> > openrsync -rx /tmp/test/ /tmp/plop/
> >
> > Result:
> >
> > openrsync(3470) in free(): bogus pointer (double free?) 0x7f7dcdc8
> > Abort trap (core dumped)
> >
> > The patch below fixes it and
Hiltjo Posthuma:
> I noticed a free() issue on an uninitialized pointer on a certain condition.
>
> To reproduce:
>
> mkdir -p /tmp/test /tmp/plop
> openrsync -rx /tmp/test/ /tmp/plop/
>
> Result:
>
> openrsync(3470) in free(): bogus pointer (double free?) 0x7f7dcdc8
>
On Sat, Jun 01, 2019 at 06:12:16PM -0500, Katherine Rohl wrote:
> Couple questions:
>
> > This means no interrupt will be injected. I'm not sure if that's what you
> > want.
> > See vm.c: vcpu_exit_inout(..). It looks like you may have manually asserted
> > the
> > IRQ in this file, which is a b
On Sun, Jun 02, 2019 at 03:21:34PM +0200, Jasper Lievisse Adriaanse wrote:
> On Sat, Jun 01, 2019 at 06:12:16PM -0500, Katherine Rohl wrote:
> > Couple questions:
> >
> > > This means no interrupt will be injected. I'm not sure if that's what you
> > > want.
> > > See vm.c: vcpu_exit_inout(..). I
Frederic Cambus:
> Here is a diff to sync kernel fonts with the latest released Spleen
> version, bringing the following improvements:
[...]
> - Add some artefacts on each side of the lower case 'i' characters
Yes, please!
Actually, I still think the 'i' should have a wide foot like the '1'...
bu
On Wed, Jun 05, 2019 at 08:39:51AM +0200, Renaud Allard wrote:
>
>
> On 6/5/19 8:20 AM, Gilles Chehade wrote:
> > On Tue, Jun 04, 2019 at 03:54:11PM +0200, Renaud Allard wrote:
> > >
> > >
> > > On 6/3/19 11:53 AM, Renaud Allard wrote:
> > > > > >
> > > > > > On 5/29/19 9:58 AM, Florian Obser
On 02/06/19(Sun) 22:03, Mark Kettenis wrote:
> > Date: Sat, 1 Jun 2019 18:55:20 -0300
> > From: Martin Pieuchot
> [...]
> > - First change is to stop calling tsleep(9) at PUSER. That makes
> > it clear that all "sleeping priorities" are smaller than PUSER.
> > That's important to understand
On 04/06/19(Tue) 23:57, Alexandr Nedvedicky wrote:
> Hello,
>
> I see, I owe some clarification to share wider context of this change.
>
> On Tue, Jun 04, 2019 at 10:32:57AM -0300, Martin Pieuchot wrote:
> > On 04/06/19(Tue) 01:37, Alexandr Nedvedicky wrote:
> > > Hello,
> > >
> > > diff below i
> Date: Wed, 5 Jun 2019 12:57:27 +0200
> From: Frederic Cambus
>
> Hi tech@,
>
> Here is a diff to sync kernel fonts with the latest released Spleen
> version, bringing the following improvements:
>
> - Shift the middle bar of the upper case 'G' one pixel down in the 12x24
> version
> - Shift
On 6/5/19 8:39 AM, Renaud Allard wrote:
On 6/5/19 8:20 AM, Gilles Chehade wrote:
On Tue, Jun 04, 2019 at 03:54:11PM +0200, Renaud Allard wrote:
On 6/3/19 11:53 AM, Renaud Allard wrote:
On 5/29/19 9:58 AM, Florian Obser wrote:
why not let acme-client generate the key?
Here is a more
Hi tech@,
Here is a diff to sync kernel fonts with the latest released Spleen
version, bringing the following improvements:
- Shift the middle bar of the upper case 'G' one pixel down in the 12x24
version
- Shift lower case 'k' character right, for better alignment in the 12x24,
16x32, and 32
Hi all,
when closing tcpdump while sending high rate traffic over box i'm
getting log below:
x3550m4# tcpdump -ni ix1
^C
x3550m4# tcpdump: send_fd: sendmsg(3): Broken pipe
tcpdump: send_fd: sendmsg: expected sent 1 got -1
OpenBSD 6.5-current (GENERIC.MP) #6: Tue Jun 4 15:05:10 MDT 2019
dera
On Tue, Jun 04, 2019 at 09:56:27AM +0200, Stefan Sperling wrote:
> That problem was not quite fixed yet so the previous diff was backed out.
> The problem should be fixed with this version.
Please ignore this.
Ken found that it triggers the same panic yet again.
> diff 108b98dc66011292b9ce4c54c4
> Date: Wed, 5 Jun 2019 10:16:25 +0200
> From: Sebastien Marie
>
> Hi,
>
> I would like to have feedback and testing on this diff. The initial work
> was done by ian@.
Don't forget to run "make syscalls" in sys/kern when building your own
kernel with this diff!
> It unlocks read(2) and write(2
Hi Mitchell
Thanks a lot for the work you are putting into BFD, I'll be able to
review this properly over the weekend.
-peter
On 2019 Jun 03 (Mon) at 20:37:17 +1000 (+1000), Mitchell Krome wrote:
:Hi,
:
:Testing bfd against frr on linux, their bfd implementation sends polls
:as soon as the sess
Hi,
I would like to have feedback and testing on this diff. The initial work
was done by ian@.
It unlocks read(2) and write(2) families, and push the KERNEL_LOCK
deeper in the code path. With it, read(2) and write(2) on socket will be
KERNEL_LOCK-free.
read(2) and write(2) are file type agnostic
18 matches
Mail list logo