On Tue, Jan 23, 2018 at 03:43:35PM +0100, Martin Pieuchot wrote:
> ifiq_destroy() is not called with the NET_LOCK() held, so there's no
> need to check for that.
>
> Simply put an assert.
OK bluhm@
> Index: net/ifq.c
> ===
> RCS fil
this implements an ipe(4) driver that supports ip encapsulation
largely as per rfc1241.
it is interesting because it has Flow Id in the encapsulation header
which identifies distinct ip tunnels between the same endpoints.
this allows you to carry trffic for different routing domains over
ip betwee
Hi,
quite primitive features, but until cwmrc parsing grows to support passing
arguments with binds(i jk:P), these cover some cases for binary minded ppl
partitioning the available pixels for use:)
Comments?
I left out man page bits on purpose, but this works with ie.:
bind-key C4-h windo
> On 24 Jan 2018, at 00:43, Martin Pieuchot wrote:
>
> ifiq_destroy() is not called with the NET_LOCK() held, so there's no
> need to check for that.
>
> Simply put an assert.
ok.
>
> Index: net/ifq.c
> ===
> RCS file: /cvs/src/
POSIX says awk supports \v and \a escapes but ours does not.
I used \007 for BEL since that is what awk's lex.c uses, though we
could safely use '\a' there instead.
See http://mm.icann.org/pipermail/tz/2018-January/025932.html
for context.
- todd
Index: usr.bin/awk/b.c
=
> Date: Tue, 23 Jan 2018 18:14:31 +0100
> From: Martin Pieuchot
>
> On 23/01/18(Tue) 18:10, Mark Kettenis wrote:
> > > Date: Tue, 23 Jan 2018 14:06:08 +
> > > From: Visa Hankala
> > >
> > > On Mon, Jan 22, 2018 at 11:12:13AM +0100, Martin Pieuchot wrote:
> > > > Diff below moves the common
On Tue, Jan 23, 2018 at 06:14:31PM +0100, Martin Pieuchot wrote:
> On 23/01/18(Tue) 18:10, Mark Kettenis wrote:
> > > Date: Tue, 23 Jan 2018 14:06:08 +
> > > From: Visa Hankala
> > >
> > > On Mon, Jan 22, 2018 at 11:12:13AM +0100, Martin Pieuchot wrote:
> > > > Diff below moves the common mut
On Mon, Jan 22, 2018 at 04:23:59PM +0100, Martin Pieuchot wrote:
> Diff below adds a new feature to bridge(4), similar to Cisco's Protected
> Port but with more possibilities.
>
> The idea is to prevent traffic to flow between some members of a bridge(4).
> For example:
> - you want to prevent s
On Tue, Jan 23, 2018 at 08:12:49PM +0300, Denis wrote:
> Running namecoind 13.2 for about two years. OpenBSD 6.1amd64 is the last
> version which supports it.
>
> On 6.2 I stuck with malloc() hardening. With no any malloc.conf options
> I have these errors:
>
> namecoind (4563) malloc():bogus po
On 23/01/18(Tue) 18:10, Mark Kettenis wrote:
> > Date: Tue, 23 Jan 2018 14:06:08 +
> > From: Visa Hankala
> >
> > On Mon, Jan 22, 2018 at 11:12:13AM +0100, Martin Pieuchot wrote:
> > > Diff below moves the common mutex implementation to kern/ and enable it
> > > for
> > > alpha, amd64, arm64
Running namecoind 13.2 for about two years. OpenBSD 6.1amd64 is the last
version which supports it.
On 6.2 I stuck with malloc() hardening. With no any malloc.conf options
I have these errors:
namecoind (4563) malloc():bogus pointer (double free?) 0xdfdfdfdfdfdfdfdf
namecoind (4563) free(): chunk
> Date: Tue, 23 Jan 2018 14:06:08 +
> From: Visa Hankala
>
> On Mon, Jan 22, 2018 at 11:12:13AM +0100, Martin Pieuchot wrote:
> > Diff below moves the common mutex implementation to kern/ and enable it for
> > alpha, amd64, arm64, i386, mips64, powerpc.
>
> Your diff seems to miss the necess
Diff below adds a new feature to bridge(4), similar to Cisco's Protected
Port but with more possibilities.
The idea is to prevent traffic to flow between some members of a bridge(4).
For example:
- you want to prevent some of your servers to talk to each others, or
- you want employees/student
On 11/01/18(Thu) 11:58, David Gwynne wrote:
> im sending this out more as a backup than a serious diff.
>
> this tweaks bpf so it can be used by subsystems, not just interfaces.
> this is done by making bpf store and use names (eg, "pf" and "em0")
> instead of just interfaces. interfaces get some
On Tue, Jan 23, 2018 at 03:23:24PM +0100, Martin Pieuchot wrote:
> On 23/01/18(Tue) 14:06, Visa Hankala wrote:
> > In addition, you should put the common mutex code into kern_mutex.c.
> > Lets keep kern_lock.c for the mplock only.
>
> I'm more in favor of putting everything into kern_lock.c. We'r
ifiq_destroy() is not called with the NET_LOCK() held, so there's no
need to check for that.
Simply put an assert.
Index: net/ifq.c
===
RCS file: /cvs/src/sys/net/ifq.c,v
retrieving revision 1.21
diff -u -p -r1.21 ifq.c
--- net/ifq.c
On 23/01/18(Tue) 14:06, Visa Hankala wrote:
> On Mon, Jan 22, 2018 at 11:12:13AM +0100, Martin Pieuchot wrote:
> > Diff below moves the common mutex implementation to kern/ and enable it for
> > alpha, amd64, arm64, i386, mips64, powerpc.
>
> Your diff seems to miss the necessary bits in .
Indeed
On Mon, Jan 22, 2018 at 11:12:13AM +0100, Martin Pieuchot wrote:
> Diff below moves the common mutex implementation to kern/ and enable it for
> alpha, amd64, arm64, i386, mips64, powerpc.
Your diff seems to miss the necessary bits in .
In addition, you should put the common mutex code into kern_m
On Fri, 19 Jan 2018 16:00:55 +0100
Michael Gmelin wrote:
> ...
> According to the X509_check_host(3)
> (src/lib/libcrypto/man/X509_check_host.3), "The namelen argument must
> be the number of characters in the name string or zero, in which case
> the length is calculated with strlen(name)" for
Diff below moves the common mutex implementation to kern/ and enable it for
alpha, amd64, arm64, i386, mips64, powerpc.
ok?
Index: kern/kern_lock.c
===
RCS file: /cvs/src/sys/kern/kern_lock.c,v
retrieving revision 1.52
diff -u -p -r1
20 matches
Mail list logo
