linux-kernel - Re: 2.6.19-rc2-mm2

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: <20061026061131.GA9265@nineveh.rivenstone.net>
Date:	Thu, 26 Oct 2006 02:11:32 -0400
From:	jhf@...umbus.rr.com (Joseph Fannin)
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org, paulus@...ba.org,
	linuxppc-dev@...abs.org
Subject: Re: 2.6.19-rc2-mm2

On Fri, Oct 20, 2006 at 01:56:41AM -0700, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc2/2.6.19-rc2-mm2/
>

    The "Lazy interrupt disabling for 64-bit machines" patch
(which is in -rc2-mm2 through git-powerpc) seems to make -rc2-mm2
not build for ppc32 when KEXEC is enabled.  Building with kexec
enabled worked in -rc2-mm1.

    Building -mm2 fails when trying to make the vmlinux.  I don't have
the exact messages anymore, sorry, but it was an "undefined reference
to hard_irq_disable' in arch/powerpc/kernel/entry_32.S".  This appears
to be the result of an earlier warning about an "implicit
declaration of hard_irq_disable" in arch/powerpc/kernel/crash.c .

    (There's a comment at the top of that file that made it sound to
me like the file is for PPC64 only, but looking closer makes me think
that's not the case.)

    Backing out that "lazy interrupt" patch got -mm2 building again.
Turning kexec off works too.

    I don't use kexec, I just have it config'd on.  I doubt anyone is
actually using kexec in -mm on ppc32.  I'm just sayin'.

--
Joseph Fannin
jhf@...umbus.rr.com

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