linux-kernel - 2.6.18-git9

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-next>] [day] [month] [year] [list]

Message-ID: <451B94AA.3090100@shadowen.org>
Date:	Thu, 28 Sep 2006 10:23:54 +0100
From:	Andy Whitcroft <apw@...dowen.org>
To:	Alan Stern <stern@...land.harvard.edu>
CC:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: 2.6.18-git9

I have a couple of power boxes which no longer seem to be able to
compile mainline as of 2.6.18-git9.  The build fails as below:

  CC      drivers/usb/core/driver.o
drivers/usb/core/driver.c: In function `usb_probe_device':
drivers/usb/core/driver.c:168: error: structure has no member named
`pm_usage_cnt'
drivers/usb/core/driver.c: In function `usb_driver_claim_interface':
drivers/usb/core/driver.c:305: error: structure has no member named
`pm_mutex'
drivers/usb/core/driver.c:309: error: structure has no member named
`pm_mutex'
drivers/usb/core/driver.c: In function `usb_driver_release_interface':
drivers/usb/core/driver.c:358: error: structure has no member named
`pm_mutex'
drivers/usb/core/driver.c:362: error: structure has no member named
`pm_mutex'
make[3]: *** [drivers/usb/core/driver.o] Error 1
make[2]: *** [drivers/usb/core] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2

This seems to be realated to the changes in this commit:

	commit 645daaab0b6adc35c1838df2a82f9d729fdb1767
    	usbcore: add autosuspend/autoresume infrastructure

The machines in question do not have CONFIG_PM set.  It seems that the
definition of pm_mutex et al in struct usb_device are contingent on that
defined, but the use of it in usb_driver_release_interface() are not.

Its not clear to me if suspending in this context is quite the same as
full suspend to disk that I associate with PM so I am unsure which bit
is in error.  Will retest with those references under CONFIG_PM.

Alan?

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