The following diff fixes namespace polution with C++ in the stdio.h
header.
I was looking into a build issue when trying to build another program
dependent on a new port I posted (spdlog). Peeking at one of it's
headers I noticed a workaround for OpenBSD that doesn't work anyway.
Fixing the
Hi,
At least 6.9 and 7.0 (and -current) sometimes shows a dmesg that:
puc1 at pci1 dev 0 function 1 "ASIX AX99100" rev 0x00: ports: 16 com
com5 at puc1 port 0 apic 1 int 1: st16650, 32 byte fifo
com5: probed fifo depth: 0 bytes
In sys/dev/ic/com.c:com_fifo_probe(), I found that
Hi,
This time tdb_delete() doesn't kill passed `tdb' but schedules timeout
to do this. So this `tdb' is logically killed and should be not used,
but because the killer timeout is also serialized with netlock we don;t
catch use-after-free issue.
This was the reason I reverted my "per-cpu
This is just a quick hack for now, but we need something like it in
order to correctly extract some newer tars with correct timestamps, in
particular python-generated ones like
https://pypi.io/packages/source/w/wheel/wheel-0.36.2.tar.gz
Index: tar.c
A very small change with fixing an off by one copy to the return value.
It was also copying the '\n' character by mistake.
diff --git a/usr.sbin/smtpd/parse.y b/usr.sbin/smtpd/parse.y
index 832f4f2aec9..ff7b9a9a340 100644
--- a/usr.sbin/smtpd/parse.y
+++ b/usr.sbin/smtpd/parse.y
@@ -2543,13
While testing OpenBSD with XCP-ng (https://xcp-ng.org/), I noticed changing the
virtual interface state (connecting/disconnecting) was leading to a panic.
The following diff fixes the problem on my test host.
(this is kind of "backported" from OpenBSD 6.1...)
If you are using OpenBSD on a
Hi,
Goal is to ref count the tdb in ipsec. For that the counters that
access the tdb have to be pushed down the function hierarchie.
While there adjust the error handling. Output functions should
generate an errno.
ok?
bluhm
Index: netinet/ip_ah.c
On Fri, Oct 15, 2021 at 01:32:22PM +0200, Mark Kettenis wrote:
> > Date: Fri, 15 Oct 2021 14:04:08 +0300
> > From: Vitaliy Makkoveev
> >
> > The next diff before introduce rwlock(9) for UNIX sockets garbage
> > collector data.
> >
> > Release `unp_lock' before call unp_internalize() and take it
> Date: Fri, 15 Oct 2021 14:04:08 +0300
> From: Vitaliy Makkoveev
>
> The next diff before introduce rwlock(9) for UNIX sockets garbage
> collector data.
>
> Release `unp_lock' before call unp_internalize() and take it within when
> access garbage collector data such as `unp_rights',
The next diff before introduce rwlock(9) for UNIX sockets garbage
collector data.
Release `unp_lock' before call unp_internalize() and take it within when
access garbage collector data such as `unp_rights', `unp_msgcount' and
`unp_file'. The garbage collector rwlock(9) will be introduced with the
On 15/10/21(Fri) 09:27, Sebastien Marie wrote:
> Hi,
>
> The following diff removes VLOCKSWORK flag.
Nice.
> This flag is currently used to mark or unmark a vnode to actively
> check vnode locking semantic (when compiled with VFSLCKDEBUG).
>
> Currently, VLOCKSWORK flag isn't properly set for
Hi,
The following diff removes VLOCKSWORK flag.
This flag is currently used to mark or unmark a vnode to actively
check vnode locking semantic (when compiled with VFSLCKDEBUG).
Currently, VLOCKSWORK flag isn't properly set for several FS
implementation which have full locking support,
Hi,
The following diff is still without intented behaviour changes.
The first chunk replaces a direct vp->v_op->vop_lock() call by
VOP_LOCK() wrapper. It only adds some safety check on vop_lock being
NULL (and MUTEX_ASSERT_UNLOCKED on vnode_mtx).
Others chunks replaces several direct
On Sun, Oct 03, 2021 at 10:05:56AM +, Klemens Nanni wrote:
> On Sat, Oct 02, 2021 at 07:03:21PM +0200, vifino wrote:
> > On Sat Oct 2, 2021 at 6:36 PM CEST, Raf Czlonka wrote:
> > > On Sat, Oct 02, 2021 at 02:15:53PM BST, vifino wrote:
> > > > Index: ldapd.conf.5
> > > >
14 matches
Mail list logo