On Thu, Sep 17, 2020 at 06:29:48PM -0500, Scott Cheloha wrote:
> [...]
>
> Using nanosleep(2) to print the stats periodically causes the period
> to drift. If you use setitimer(2) it won't drift.
>
> ok?
19 month bump and rebase.
I have updated the patch according to input from kn@.
Once agai
Hello,
On Thu, Apr 28, 2022 at 10:31:33PM +0200, Alexander Bluhm wrote:
>
> Thanks. regress/sys/netinet6/frag6 found a small issue. If the
> icmp6 header is fragmented, we cannot pull the icmp6 header. I had
> to copy the fragment check to the beginning of case IPPROTO_ICMPV6.
>
> This chunk
Hello Moritz,
I like your change. There is just one nit see comment below.
>
>
> Index: sys/net/pf_if.c
> ===
> RCS file: /cvs/src/sys/net/pf_if.c,v
> retrieving revision 1.103
> diff -u -p -r1.103 pf_if.c
> --- sys/net/pf_if.c
On Thu, Apr 28, 2022 at 08:15:20AM +0200, Alexandr Nedvedicky wrote:
> Hello,
>
> On Thu, Apr 28, 2022 at 12:36:40AM +0200, Alexander Bluhm wrote:
> > On Wed, Apr 27, 2022 at 11:47:45PM +0200, Alexander Bluhm wrote:
> > > New diff:
> > > - make off and end relative to opts array
> > > - check leng
This adds return value check for sk_X509_push.
In error case, allocated memories are freed at 'export_end:'.
After this diff, I would like to add more another return value check.
ok?
Index: pkcs12.c
===
RCS file: /cvs/src/usr.bin/ope
Hi tech@,
syzkaller reported pfi_get_interfaces
https://syzkaller.appspot.com/bug?id=963ef41930bb84af584be3bf910a3f67d65581a0
which does a copyout while holding NET and PF lock.
The following diff should address this.
mbuhl
Index: sys/net/pf_if.c
===
On Thu, Apr 28, 2022 at 07:24:22PM +0200, Alexander Bluhm wrote:
> I still need an ok for this diff. It is the final step before we
> can run IP forwaring in parallel.
Fine with me. If it holds you back put it in OK claudio@
I will rip the rttimer code appart in the next days and make that API a
I still need an ok for this diff. It is the final step before we
can run IP forwaring in parallel.
bluhm
On Thu, Apr 21, 2022 at 05:44:17PM +0200, Alexander Bluhm wrote:
> On Wed, Apr 20, 2022 at 08:12:51PM +0200, Alexander Bluhm wrote:
> > mvs@ reminded me of a crash I have seen in December. R
On Thu, Apr 28, 2022 at 05:51:57PM +0200, Alexander Bluhm wrote:
> On Wed, Apr 27, 2022 at 12:10:59PM +0200, Claudio Jeker wrote:
> > There is no need to have a rttimer queue per rdomain. The rttimer itself
> > is rdomain aware and so this just make everything more complicated for no
> > gain.
> >
On Wed, Apr 27, 2022 at 12:10:59PM +0200, Claudio Jeker wrote:
> There is no need to have a rttimer queue per rdomain. The rttimer itself
> is rdomain aware and so this just make everything more complicated for no
> gain.
>
> This diff just drops back to a single queue and initializes the queues i
speaker(4) is a whimsical thing, but I don't think we should have a
dedicated chiptune interpreter in the kernel.
This patch unhooks the driver and the manpage from the build. The
driver is built for alpha, amd64, and i386.
A subsequent patch will move all relevant files to the attic and clean
u
rw_enter(9) can sleep. When the lock is finally acquired by the
pagedaemon the previous check might no longer be true and the page
could be busy. In this case we shouldn't touch it.
Diff below recheck for PG_BUSY after acquiring the lock and also
use a variable for the lock to reduce the differe
On Wed, Apr 27, 2022 at 10:48:42PM +0200, Caspar Schutijser wrote:
> Hi,
>
> On Thu, Mar 24, 2022 at 07:11:42AM +0100, Alexandre Ratchov wrote:
> > Most audio/video players do a stop/start cycle whenever the play
> > position is changed, track is changed, etc. Currently, stopping drains
> > the pl
13 matches
Mail list logo
