linux-kernel - Re: [PATCH] usb hubc build fix.patch prefix

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: <Pine.LNX.4.44L0.0610021003330.6651-100000@iolanthe.rowland.org>
Date:	Mon, 2 Oct 2006 10:15:13 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Paul Jackson <pj@....com>
cc:	Andrew Morton <akpm@...l.org>, <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>
Subject: Re: [PATCH] usb hubc build fix.patch prefix

On Sun, 1 Oct 2006, Paul Jackson wrote:

> From: Paul Jackson <pj@....com>
> 
> The patch series 2.6.18-mm2-broken-out does not apply to 2.6.18,
> for me anyway.
> 
> The 'quilt push' of this series fails with:
> 
>     Applying patch usb-hubc-build-fix.patch
>     patching file drivers/usb/core/hub.c
>     Hunk #1 FAILED at 1831.
>     Hunk #2 succeeded at 1904 (offset -2 lines).
>     Hunk #3 FAILED at 1946.
>     2 out of 3 hunks FAILED -- rejects in file drivers/usb/core/hub.c
>     Patch usb-hubc-build-fix.patch does not apply (enforce with -f)

There is no patch labelled usb-hubc-build-fix.patch anywhere in 
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18/2.6.18-mm2/broken-out/
This suggests that the quilt archive is indeed messed up.

> If I apply the following patch *just before* the failing
> usb-hubc-build-fix.patch, everything applies cleanly from there on
> down the patch set.
> 
> I don't know what's right here.  I'm just blindly pushing code.
> 
> But it seems obvious to me that the 2.6.18-mm2 broken-out patch set
> is borked:
> 
>   The first patch in the series: origin.patch, definitely places these
>   two hub_* defines just before the usb_resume_root_hub() routine.

That is in fact where they belong.  Furthermore, that's where the 
origin.patch file from the URL above puts them.  It sounds like the 
contents of the archive don't match the contents of the directory.

>   But then the patch usb-hubc-build-fix.patch clearly expects to find
>   those two hub_* defines just before the hub_suspend() routine.

That is wrong.  The module won't compile properly when CONFIG_PM is set 
and CONFIG_USB_SUSPEND isn't if the defines are placed there.

Alan Stern

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