| 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
| ||
|
Message-ID: <4AAE0F7B.5050203@kernel.org> Date: Mon, 14 Sep 2009 18:40:11 +0900 From: Tejun Heo <tj@...nel.org> To: Frans Pop <elendil@...net.nl> CC: Jesse Brandeburg <jesse.brandeburg@...el.com>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, Ingo Molnar <mingo@...e.hu> Subject: Re: bisect results of MSI-X related panic (help!) Frans Pop wrote: > 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. Sorry, the oops doesn't ring a bell, well, not yet at least. It would be great if the bisection can be narrowed down more. -- tejun -- 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/
Powered by blists - more mailing lists