linux-kernel - Re: 2.6.24-rc2-mm1 -- strange apparent network failures

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200711152101.33266.kjwinchester@gmail.com>
Date:	Thu, 15 Nov 2007 21:01:32 -0400
From:	Kevin Winchester <kjwinchester@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	apw@...dowen.org, linux-kernel@...r.kernel.org,
	Andrew Morgan <morgan@...nel.org>
Subject: Re: 2.6.24-rc2-mm1 -- strange apparent network failures

On November 15, 2007 08:44:41 pm Andrew Morton wrote:
> On Thu, 15 Nov 2007 20:28:29 -0400
>
> Kevin Winchester <kjwinchester@...il.com> wrote:
> > On November 15, 2007 06:02:09 am Andy Whitcroft wrote:

> > I see this as well - the computer boots fine but no network.  The only
> > clues in the dmesg are:
> >
> > [  294.097876] warning: process `dhclient' gets w/ old libcap
> > [  294.097893] warning: process `dhclient' sets w/ old libcap
> >
> > So I'll try backing up the patch series to before:
> >
> > add-64-bit-capability-support-to-the-kernel.patch
>

That's the winner.  The changelog indicates that the patch is meant to keep 
compatibility with older userspace, so I guess it didn't quite keep as much 
compatibility as it wanted.

I have no idea what I'm doing, but I'll take a look at the patch anyway...

-- 
Kevin Winchester
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/