linux-kernel - Re: Regression from 2.6.36

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]

Date:	Wed, 16 Mar 2011 20:53:05 -0400
From:	Dave Jones <davej@...hat.com>
To:	Greg KH <greg@...ah.com>
Cc:	azurIt <azurit@...ox.sk>, linux-kernel@...r.kernel.org
Subject: Re: Regression from 2.6.36

On Wed, Mar 16, 2011 at 05:15:19PM -0700, Greg Kroah-Hartman wrote:

 > > Do you need any other information from me ? I'm able to try other versions or
 > > patches but, please, take into account that I have to do this on _production_
 > > server (I failed to reproduce it in testing environment). Also, I'm able to try
 > > only one kernel per day.
 > 
 > Ick, one kernel per day might make this a bit difficult, but if there
 > was any way you could use 'git bisect' to try to narrow this down to the
 > patch that caused this problem, it would be great.
 > 
 > You can mark 2.6.35 as working and 2.6.36 as bad and git will go from
 > there and try to offer you different chances to find the problem.

Comparing the output of a perf profile between the good/bad kernels might
narrow it down faster than a bisect if something obvious sticks out.

	Dave

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