linux-kernel - Re: Linux 3.2.38

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:	Fri, 8 Feb 2013 14:08:19 -0500
From:	tmhikaru@...il.com
To:	Ben Hutchings <ben@...adent.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: Linux 3.2.38

	I just wanted to give a heads up so you knew where I'm at and that I
haven't forgotten to do the bisection. Well, I'm doing the bisection - and
it's having me chase wild geese. This bug is apparently not always occuring
when it's possible for it to, confusing the issue.

	Currently I'm recompiling 3.2.37 from scratch to ensure that my
environment or hardware hasn't changed somehow since I originally built it
and is causing some of my kernel compiles to miscompile or something.  If
that build turns out okay I'll try bisecting again and see if I get anywhere
different than before.

Despite it obviously leading off into wild goose chasing territory, I think
it's possible this could be illuminating for someone with more experience
with bisect than I, so I'm including the bisect log below.

git bisect start
# bad: [8eedd52017a07a5bae2aded2b5023bfba5971af9] Linux 3.2.38
git bisect bad 8eedd52017a07a5bae2aded2b5023bfba5971af9
# good: [2d18772602ba45629dfd4ffe1878ecb26fb3d3ed] Linux 3.2.37
git bisect good 2d18772602ba45629dfd4ffe1878ecb26fb3d3ed
# good: [157bb66c87286abc3dad2ed19a8cfb130ef24573] USB: option: add TP-LINK HSUPA Modem MA180
git bisect good 157bb66c87286abc3dad2ed19a8cfb130ef24573
# good: [6fad7bfb8aef9a8688d3d3b3ea917b3c7d1fc8b7] can: ti_hecc: fix invalid error codes
git bisect good 6fad7bfb8aef9a8688d3d3b3ea917b3c7d1fc8b7
# good: [8bdb5d1a2d352d58ac99be529bb8c006dfb9be83] sd: Reshuffle init_sd to avoid crash
git bisect good 8bdb5d1a2d352d58ac99be529bb8c006dfb9be83
# bad: [8a6d0db2f6a06c5fdfb7a208002d0f9961d1ad41] intel-iommu: Prevent devices with RMRRs from being placed into SI Domain
git bisect bad 8a6d0db2f6a06c5fdfb7a208002d0f9961d1ad41
# bad: [756a6d71c4f566f840cf4e04fe2540e6927d2613] x86: Use enum instead of literals for trap values
git bisect bad 756a6d71c4f566f840cf4e04fe2540e6927d2613
# good: [9a1f08a1a192f9177d7063d903773aed800b840f] drivers/firmware/dmi_scan.c: fetch dmi version from SMBIOS if it exists
git bisect good 9a1f08a1a192f9177d7063d903773aed800b840f
# bad: [a423a71dafbcd05bc263f9eb42c142e4b869ed95] drm/i915: Implement WaDisableHiZPlanesWhenMSAAEnabled
git bisect bad a423a71dafbcd05bc263f9eb42c142e4b869ed95

Now, here's the thing - that last bad entry is the one that bisect is
convinced is the bad patch. Problem is, I don't have that hardware, so it
strains belief that it could be the cause. I even went so far as to checkout
a clean copy of 3.2.38 and reverse apply that particular patch for testing
on top of it - and I still have the problem.

Any suggestions on how to proceed would be appreciated in case I've missed
some git magic that would make this easier.

Tim McGrath

Content of type "application/pgp-signature" skipped