* Maxime Villard [2020-02-22 12:16:35 +0100]:
CVSROOT:/cvs
Module name:src
Changes by: morti...@cvs.openbsd.org2020/02/15 15:59:55
Modified files:
sys/arch/amd64/amd64: vmm.c
Log message:
Add bounds check on addresses passed from guests in pvclock.
Fixes an is
On Tue, Feb 25, 2020 at 05:58:57PM +0100, Alexander Bluhm wrote:
> On Mon, Feb 24, 2020 at 07:58:23PM -0800, Andrew Hewus Fresh wrote:
> > Index: gnu/usr.bin/perl/cpan/Term-ReadKey/Makefile.PL
> > ===
> > RCS file: /cvs/src/gnu/usr.bin
On Mon, Feb 24, 2020 at 07:58:23PM -0800, Andrew Hewus Fresh wrote:
> Index: gnu/usr.bin/perl/cpan/Term-ReadKey/Makefile.PL
> ===
> RCS file: /cvs/src/gnu/usr.bin/perl/cpan/Term-ReadKey/Makefile.PL,v
> retrieving revision 1.3
> diff -u
On Tue, Feb 25, 2020 at 12:16:22PM +, Stuart Henderson wrote:
> Sometimes you want to redirect a request to another site but maintaining
> the same type of connection (http or https) as the original request.
> Currently to do this in httpd you have to duplicate the whole server block
> (once fo
seems reasonable, OK florian
On Tue, Feb 25, 2020 at 12:16:22PM +, Stuart Henderson wrote:
> Sometimes you want to redirect a request to another site but maintaining
> the same type of connection (http or https) as the original request.
> Currently to do this in httpd you have to duplicate the
The VOP layer passes a "struct proc" pointer encoded as `a_p' in most
of its arguments. This pointer is most of the time only used to re-
enter the VFS layer. Due to that design, a lot of "struct proc *" are
being passed up to the generic file descriptor layer.
Diff below starts reducing this by
On Tue, Feb 25, 2020 at 01:06:31PM +0100, Tobias Heider wrote:
> Hi,
>
> I tried to figure out the reason for the lost Tx receive interrupt
> by comparing iwm with iwlwifi and I think our handling of the
> periodic RX interrupt is a bit off.
Very nice find.
Not sure if the lost Tx interrupt is r
On 2020/02/25 13:00, Stefan Sperling wrote:
> On Tue, Feb 25, 2020 at 10:40:47AM +, Stuart Henderson wrote:
> > On 2020/02/24 11:56, Stefan Sperling wrote:
> > > These functions will compute the wrong display width for input which is
> > > already a hex string. This bug doesn't trigger because
On Tue, Feb 25, 2020 at 01:02:06PM +0100, Alexandre Ratchov wrote:
> On Thu, Feb 13, 2020 at 04:52:12AM +, Raf Czlonka wrote:
> >
> > Hi Alexandre,
> >
> > I have to say that I also find the two ranges mildly confusing,
> > i.e. 0-255 in one place, and 0-127 in another. In terms of units,
> >
Sometimes you want to redirect a request to another site but maintaining
the same type of connection (http or https) as the original request.
Currently to do this in httpd you have to duplicate the whole server block
(once for http, once for https, with different "block return" target URLs).
With
Hi,
I tried to figure out the reason for the lost Tx receive interrupt
by comparing iwm with iwlwifi and I think our handling of the
periodic RX interrupt is a bit off.
In linux on receive of any of the possible RX interrupts the periodic
interrupt is disabled and then reenabled. As far as I unde
On Thu, Feb 13, 2020 at 04:52:12AM +, Raf Czlonka wrote:
>
> Hi Alexandre,
>
> I have to say that I also find the two ranges mildly confusing,
> i.e. 0-255 in one place, and 0-127 in another. In terms of units,
> personally, I'm used to, and quite like, the granularity of 0-255.
>
> Again, n
On Tue, Feb 25, 2020 at 10:40:47AM +, Stuart Henderson wrote:
> On 2020/02/24 11:56, Stefan Sperling wrote:
> > These functions will compute the wrong display width for input which is
> > already a hex string. This bug doesn't trigger because we never actually
> > pass an ASCII hex string in, b
On 2020/02/24 11:56, Stefan Sperling wrote:
> These functions will compute the wrong display width for input which is
> already a hex string. This bug doesn't trigger because we never actually
> pass an ASCII hex string in, but it is still a bug.
>
> ASCII hex strings are printable ASCII, so there
14 matches
Mail list logo
