linux-kernel - Re: [REGRESSION] [nailed] USB boot failure: USB: EHCI: make ehci-pci a separate driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130213161353.GA17177@rhlx01.hs-esslingen.de>
Date:	Wed, 13 Feb 2013 17:13:53 +0100
From:	Andreas Mohr <andi@...as.de>
To:	Colin Guthrie <gmane@...in.guthr.ie>
Cc:	initramfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] [nailed] USB boot failure: USB: EHCI: make ehci-pci
 a separate driver

[not sure about CCs - I readded both initramfs-tools and lkml]

> I think you actually want both: ehci-pci and ehci-platform (tho' perhaps
> the module deps mean only the -pci one is needed)

Err, yeah, that's probably more precise.

> Either way I already posted a patch about this a while back:

> See: "[PATCH 6/6] kernel-modules: Add ehci support for kernel 3.8+"

OK, I've seen it, but:
which file does it touch?? That's a complete mystery to me
(the initramfs-tools git checkout here does not contain that path).

> (admittedly perhaps that should have been 3.7 rather than 3.8)!

Hmm, the patch was introduced in early moments from 3.7 prior to
3.8-rc1. Thus one could say that the non-covered window is only
a part of the small 3.8-rc1 step which is used by devel people only.
OTOH to retain the very important development property
of properly working regression bisects over all versions
(of regressions *other* than this USB boot effect, that is),
even that smallish window ought to be fully covered.
If it thus is decided to be a sizeable versioning issue,
then it really should be downgraded to 3.7 very soon,
in order to prevent a support window coverage issue.

Thanks,

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