linux-kernel - Re: Heads up Linux 2.6.38-rc4 compile problems.

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: <AANLkTikJL_4-7F_2oSuefSpL7ak3+OWLk7F+bDqWT8XJ@mail.gmail.com>
Date:	Tue, 8 Feb 2011 12:44:17 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	David Miller <davem@...emloft.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Heads up Linux 2.6.38-rc4 compile problems.

On Tue, Feb 8, 2011 at 12:28 PM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
>
> A quick heads up.  2.6.38-rc4 looks like the worst kernel I've ever tried to
> test.  It boots up properly and looks ok, but I can't get it to even
> compile the programs I usually test with. 2.6.38-rc3 at least managed
> that yesterday.

gcc dying with ICE or SIGSEGV? Or what? Seriously lacking information here.

Are you using btrfs or cifs (the two filesystems that had
bigger-than-average changes)?

Any chance to bisect it (even if just partially - a couple of
bisection runs would already narrow it down quite a bit)?

> From 2.6.38-rc3 I managed to figure out that tftp transfers over ipv6
> with curl are dying in with a getpeername problem.

Hmm. Adding Davem for that one, although I'd expect you to be able to
figure out some networking problem on your own and perhaps give a
better report?

                             Linus
--
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/