linux-kernel - Re: bisect results of MSI-X related panic (help!)

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: <200909120623.49764.elendil@planet.nl>
Date:	Sat, 12 Sep 2009 06:23:47 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Jesse Brandeburg <jesse.brandeburg@...el.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>, Tejun Heo <tj@...nel.org>
Subject: Re: bisect results of MSI-X related panic (help!)

Jesse Brandeburg wrote:
> I've bisected, here is my bisect log, problem is that the commit
> identified is a merge commit, and *I don't know what to revert to test*.
> It appears the parent of the merge:
> 6e15cf04860074ad032e88c306bea656bbdd0f22 is marked good, but looks to be
> in a possibly related area to the panic.

That merge does contain quite a few merge fixups, so it's quite possible 
one of them is the cause of the failure.
Maybe the simplest way to verify that is to compile both parents of the 
merge to doublecheck that they work OK. Then, if a compile of the merge 
itself is bad, the problem really is in the merge commit itself.

That commit is the "percpu" merge, so I've added Tejun (author of most of 
that branch) and Ingo (merger) in CC.

Hope that helps.

Cheers,
FJP
--
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/