linux-kernel - Re: linux-next: Tree for June 25

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: <200806260228.38674.rjw@sisk.pl>
Date:	Thu, 26 Jun 2008 02:28:38 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	kernel-testers@...r.kernel.org
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: Tree for June 25

On Wednesday, 25 of June 2008, Stephen Rothwell wrote:
> Hi all,

Hi,

> Changes since next-20080624:
> 
> The tip-core tree gained three conflicts against Linus' tree.
> 
> The sched tree gained a conflict against the cpus4096 tree.
> 
> The x86 tree gained a conflict against the ftrace tree.  It also required
> three patches that Ingo supplied.
> 
> The pci tree gained two conflicts against the x86 tree.
> 
> The v4l-dvb tree has had another commit reverted for a build problem,
> however that may have been due to a mismerge in yesterday's tree.
> 
> The acpi tree gained two conflicts against the x86 tree.
> 
> The tests tree gained a conflict against the sched tree.
> 
> The vfs tree gained a conflict against the sched tree.
> 
> The rr tree gained a conflict against each of the sched and powerpc
> trees.  It also required a patch and a commit reverted for build problems.
> 
> The pcmcia tree lost its conflict against Linus' tree.

This tree is completely broken on my test box (x86-64 HP nx6325) and I can't
even bisect it. :-(

It hits a NULL pointer dereference in find_symbol during boot, but when I tried
to bisect this issue, I hit another one that made the box hang solid during
boot (early, no messages available).

If things continue going this way, 2.6.27 will be a disaster ...

Thanks,
Rafael
--
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/