On Tue, May 22, 2018 at 07:35:59PM +0200, Mark Kettenis wrote:
> > Date: Fri, 4 May 2018 20:14:38 +0200 (CEST)
> > From: Mark Kettenis
> >
> > > Date: Tue, 1 May 2018 11:55:00 +0200 (CEST)
> > > From: Mark Kettenis
> > >
> > > So after adding a quick hack to mitigate Spectre variant 2 to ARM
>
On Tue, May 22, 2018 at 03:39:11PM +0200, Martin Pieuchot wrote:
> Tests? Comments?
The regression tests pass with this diff on a dual core i386 machine.
bluhm
> Index: kern/exec_script.c
> ===
> RCS file: /cvs/src/sys/kern/exec_sc
On Tue, May 22, 2018 at 05:43:01PM +0200, Mark Kettenis wrote:
> > Date: Mon, 21 May 2018 17:25:47 -0700
> > From: Mike Larkin
> >
> > On Mon, May 21, 2018 at 12:44:47PM +0200, Mark Kettenis wrote:
> > > The diff below fixes I2C_OP_WRITE_WITH_STOP operations. Currently we
> > > run the read comp
On Sat, May 12, 2018 at 10:18:22AM +0800, Nan Xiao wrote:
> Hi tech@,
>
> Following is a trivial modification which removes unnecessary
> initialization of timeval. I am Sorry if this patch seems a little picky.
There are half-way cases elsewhere in the tree where we timerclear or
timespecclear a
Hey,
When you print the current time from boot(8) it can look
kinda dumb, especially if you have a single-digit day *and*
a single-digit hour/minute/second, e.g.:
boot> time
Tue May 8 5:3:2 2018
libsa's printf supports zero- and space-padded output, though,
so it's easy to make libsa's ctime loo
> Date: Fri, 4 May 2018 20:14:38 +0200 (CEST)
> From: Mark Kettenis
>
> > Date: Tue, 1 May 2018 11:55:00 +0200 (CEST)
> > From: Mark Kettenis
> >
> > So after adding a quick hack to mitigate Spectre variant 2 to ARM
> > Trusted Firmware (ATF), ARM actually designed a proper solution that
> > mi
Does anyone still love ed enough to give me an OK?
On 05/05/18 14:36, Martijn van Duren wrote:
> Hello tech@,
>
> The following patch simplifies the filename handling for ed and removes
> a few BACKWARDS flags. This patch changes the code in the following
> ways:
> - If there's no valid filename
> Date: Mon, 21 May 2018 17:25:47 -0700
> From: Mike Larkin
>
> On Mon, May 21, 2018 at 12:44:47PM +0200, Mark Kettenis wrote:
> > The diff below fixes I2C_OP_WRITE_WITH_STOP operations. Currently we
> > run the read completion code for those operations, but since there is
> > no data to read, t
The snmpd parts are OK with me but I don't think I'm qualified to OK
adding the new ioctl myself.
On 2018/05/18 11:08, Jan Klemkow wrote:
> On Mon, May 14, 2018 at 09:21:13PM +0200, Jan Klemkow wrote:
> > On Mon, May 14, 2018 at 06:53:20PM +0100, Stuart Henderson wrote:
> > > On 2018/05/14 17:59,
On Tue, May 22, 2018 at 03:39:11PM +0200, Martin Pieuchot wrote:
> By assuming that `f_data' is immutable, which AFAIK is true for sockets,
> we can remove the KERNEL_LOCK() from the following syscalls iff files are
> refcounted in an MP-safe way.
>
> This diff includes the EBUSY check in dup2(2)
By assuming that `f_data' is immutable, which AFAIK is true for sockets,
we can remove the KERNEL_LOCK() from the following syscalls iff files are
refcounted in an MP-safe way.
This diff includes the EBUSY check in dup2(2) which is currently required
to avoid races with accept(2) and will later ma
> Date: Tue, 22 May 2018 12:29:21 +0200
> From: Otto Moerbeek
>
> On Thu, May 03, 2018 at 05:23:18PM +, Miod Vallat wrote:
>
> > sys/dev/pckbc/pckbd.c introduces a buglet, where the value computed for
> > local variable `table' in pckbd_set_xtscancode() in the non-translating
> > case, is ov
On Thu, May 03, 2018 at 05:23:18PM +, Miod Vallat wrote:
> sys/dev/pckbc/pckbd.c introduces a buglet, where the value computed for
> local variable `table' in pckbd_set_xtscancode() in the non-translating
> case, is overwritten by accident.
>
> Unfortunately, this means that the keyboard ends
Hi tech@,
Below is the patch of resetting sysload if sysctl call failed in
usr.bin/top/machine.c, otherwise the memory of sysload is undetermined.
(The same process as uvmexp and bcstats).
Index: machine.c
===
RCS file: /cvs/src/usr.
On Tue, 22 May 2018 11:05:48 +0200 Claudio Jeker
wrote:
> On Tue, May 22, 2018 at 10:26:30AM +0200, Gerhard Roth wrote:
> > Hi,
> >
> > a snmpwalk of HOST-RESOURCES-MIB::hrSWRunTable doesn't scale very well
> > with an increasing number of running processes.
> >
> > For every process and each o
On Tue, May 22, 2018 at 10:26:30AM +0200, Gerhard Roth wrote:
> Hi,
>
> a snmpwalk of HOST-RESOURCES-MIB::hrSWRunTable doesn't scale very well
> with an increasing number of running processes.
>
> For every process and each of the 7 elements of the table, mib_hrswrun()
> would call kinfo_proc() w
Hi,
a snmpwalk of HOST-RESOURCES-MIB::hrSWRunTable doesn't scale very well
with an increasing number of running processes.
For every process and each of the 7 elements of the table, mib_hrswrun()
would call kinfo_proc() which queried all the processes running on the
system and sort them by pid.
17 matches
Mail list logo