Re: Add Intel Optane DC to pcidevs

2022-12-01 Thread Jonathan Gray
On Fri, Dec 02, 2022 at 05:43:19AM +0100, Andreas Bartelt wrote: > On 12/2/22 04:54, Jonathan Gray wrote: > > On Sun, Nov 27, 2022 at 03:21:45PM +0100, Andreas Bartelt wrote: > > > Hi, > > > > > > Intel Optane DC SSDs are not yet identified in CURRENT (e.g., > > >

Re: Add Intel Optane DC to pcidevs

2022-12-01 Thread Andreas Bartelt
On 12/2/22 04:54, Jonathan Gray wrote: On Sun, Nov 27, 2022 at 03:21:45PM +0100, Andreas Bartelt wrote: Hi, Intel Optane DC SSDs are not yet identified in CURRENT (e.g.,

Re: Add Intel Optane DC to pcidevs

2022-12-01 Thread Jonathan Gray
On Sun, Nov 27, 2022 at 03:21:45PM +0100, Andreas Bartelt wrote: > Hi, > > Intel Optane DC SSDs are not yet identified in CURRENT (e.g., > https://ark.intel.com/content/www/us/en/ark/products/201861/intel-optane-ssd-dc-p5800x-series-400gb-2-5in-pcie-x4-3d-xpoint.html > ). > > The following

Re: lladdr support for netstart/hostname.if

2022-12-01 Thread Andrew Hewus Fresh
How about this adjustment to the man page? Index: share/man/man5/hostname.if.5 === RCS file: /cvs/src/share/man/man5/hostname.if.5,v retrieving revision 1.79 diff -u -p -r1.79 hostname.if.5 --- share/man/man5/hostname.if.526

netcat UDP behavior in verbose mode

2022-12-01 Thread Marco Pfatschbacher
The other day I was trying to send a syslog UDP packet via netcat. Out of habit I was running it with the -v flag and noticed that it corrupted my syslog packet with three 'X' characters. Turns out verbose mode enables udptest() which is meant to get feedback if the "connection" is successful and

OpenIKED 7.2 released

2022-12-01 Thread Tobias Heider
We have released OpenIKED 7.2, which will be arriving in the OpenIKED directory of your local OpenBSD mirror soon. This release includes the following changes to the previous release: * Added iked connection statistics counters that can be viewed with 'ikectl show stats' * Added support

tcpdump(8): grok Alexey Kuznetzov's modified libpcap format.

2022-12-01 Thread Martijn van Duren
I received a pcap file from someone containing kuznetzov's pcap format. According to "upstream" libpcap[0] this format uses struct pcap_sf_patched_pkthdr, which is: struct pcap_sf_patched_pkthdr { struct pcap_timeval ts; /* time stamp */ bpf_u_int32 caplen; /* length of portion

Re: Use `ps_mtx' mutex(9) to protect `ps_ucred' and unlock setuid(2), ...

2022-12-01 Thread Vitaliy Makkoveev
On Thu, Dec 01, 2022 at 11:28:59AM -0800, Philip Guenther wrote: > On Thu, Dec 1, 2022 at 10:31 AM Vitaliy Makkoveev wrote: > ... > > > --- sys/sys/sysctl.h7 Nov 2022 14:25:44 - 1.231 > > +++ sys/sys/sysctl.h1 Dec 2022 18:15:06 - > > @@ -587,7 +587,7 @@ struct kinfo_vmentry

Re: Use `ps_mtx' mutex(9) to protect `ps_ucred' and unlock setuid(2), ...

2022-12-01 Thread Philip Guenther
On Thu, Dec 1, 2022 at 10:31 AM Vitaliy Makkoveev wrote: ... > --- sys/sys/sysctl.h7 Nov 2022 14:25:44 - 1.231 > +++ sys/sys/sysctl.h1 Dec 2022 18:15:06 - > @@ -587,7 +587,7 @@ struct kinfo_vmentry { > > #define_FILL_KPROC_MIN(a,b) (((a)<(b))?(a):(b)) > > -#define

Re: mbufs growing in 7.2

2022-12-01 Thread 4
it's sad, but still the problem remains. during the week, in the absence of any significant network load, mbufs increased from 650 to ~1100. i am informing you because you will be tempted to write off the problem, for example, to a single faulty hardware. but maybe this is not an igc problem,

Document 'uidinfo' structure locks

2022-12-01 Thread Vitaliy Makkoveev
Index: sys/sys/proc.h === RCS file: /cvs/src/sys/sys/proc.h,v retrieving revision 1.335 diff -u -p -r1.335 proc.h --- sys/sys/proc.h 23 Nov 2022 11:00:27 - 1.335 +++ sys/sys/proc.h 1 Dec 2022 18:48:47 - @@

Use `ps_mtx' mutex(9) to protect `ps_ucred' and unlock setuid(2), ...

2022-12-01 Thread Vitaliy Makkoveev
..., setgid(2), setgroups(2), setreuid(2), setregid(2), sys_setegid(2), sys_seteuid(2), setresuid(2), setresgid(2). These syscalls do the same: they overwrite `ps_ucred' by newly allocated credentials structure, so unlock them all. Unlocked chgproccnt() call is safe, because `uidinfolk'

Re: midicat(1): use err(3)

2022-12-01 Thread Alexandre Ratchov
On Wed, Nov 30, 2022 at 09:20:26AM -0600, Scott Cheloha wrote: > Couple related things: > > - Use err(3) everywhere. > > For many of these errors we are not currently printing the errno > string. Is there any reason not to do so? The errno string is > useful. > > - Set ifile/ofile to