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: <20110629140619.744da8ea.rdunlap@xenotime.net>
Date:	Wed, 29 Jun 2011 14:06:19 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Mikael Starvik <starvik@...s.com>,
	Jesper Nilsson <jesper.nilsson@...s.com>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-cris-kernel@...s.com
Subject: Re: Build regressions/improvements in v3.0-rc5 (arch/cris)

On Wed, 29 Jun 2011 10:13:17 +0200 (CEST) Geert Uytterhoeven wrote:

> *** ERRORS ***
> 
> 698 regressions:

>   + net/mac80211/led.c: error: 'struct led_classdev' has no member named 'trig_list':  => 213, 277
>   + net/mac80211/led.c: error: dereferencing pointer to incomplete type:  => 73, 91, 100, 82
>   + net/mac80211/led.c: error: implicit declaration of function 'led_trigger_register':  => 74
>   + net/mac80211/led.c: error: implicit declaration of function 'led_trigger_unregister':  => 118
>   + net/mac80211/led.c: error: invalid application of 'sizeof' to incomplete type 'struct led_trigger' :  => 98, 71, 89, 80


I think that this is what Andrew would call a cockup, or at least I would.

These errors shouldn't be possible since net/mac80211/Kconfig says:

config MAC80211_LEDS
	bool "Enable LED triggers"
	depends on MAC80211
	depends on LEDS_CLASS
	select LEDS_TRIGGERS



Preferably arch/cris/Kconfig would source drivers/Kconfig instead of sourcing
individual drivers/foobar/Kconfig.

Second option is for arch/cris/Kconfig to source drivers/leds/Kconfig
unless there is some reason to avoid this (?).

Or we should just prevent this particular driver from being built,
but that's the least desirable choice here.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ