Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 28 Jun 2018 20:44:03 -1000
From: cpb <cpb@...416.org>
To: owl-users@...ts.openwall.com
Subject: Re: Minor problem with kernel 431stab123.1 VZ container
 networking

On Thu, Jun 28, 2018 at 03:53:19PM +0200, Solar Designer wrote:
> Hi Chris,
> 
> On Wed, Jun 20, 2018 at 06:10:01PM -1000, cpb wrote:
> > Hi, I am seeing a problem with the most recent Owl kernel from inside
> > the OpenVZ containers, which are also running Owl. Specifically:
> > 
> > These two things do not work inside i686 containers when the host is
> > running kernel-2.6.18-431.el5.028stab123.1.owl1.x86_64:
> > 
> > 1. "ifconfig" inside the containers does not work:
> > 
> >     root@...tainer:/ # ifconfig
> >     SIOCGIFCONF: Bad address
> > 
> > 2. Apache 2.2.34 (and 2.2.21) do not start, error_log shows:
> > 
> >     [Sat Jun 16 14:40:39 2018] [emerg] (14)Bad address: Couldn't set permissions on cross-process lock; check User and Group directives
> 
> (and more)
> 
> We think we have fixed the bug that caused these issues, in the kernel
> currently in Owl-current: 2.6.18-431.el5.028stab123.1.owl2.  It's not
> yet in 3.1-stable, but should be installable on 3.1 (and even on 3.0,
> but not older) as-is.  Please give it a try and let us know.

Kernel 2.6.18-431.el5.028stab123.1.owl2 works great in 32-bit containers!

Many thanks to everyone involved. I will study the patch so I can learn
more about trampoline alignment...128 bits coming someday...actually
I hope not - 32 is plenty for me! :) -CBopp

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.