linux-kernel - Re: [staging: r8192ee] WARNING: CPU: 0 PID: 1 at net/mac80211/rate.c:43 ieee80211_rate_control

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

Date:	Tue, 27 May 2014 02:07:54 +0800
From:	Jet Chen <jet.chen@...el.com>
To:	Larry Finger <Larry.Finger@...inger.net>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	devel@...verdev.osuosl.org, Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [staging: r8192ee] WARNING: CPU: 0 PID: 1 at net/mac80211/rate.c:43
 ieee80211_rate_control_register()

On 05/27/2014 01:07 AM, Larry Finger wrote:
> On 05/26/2014 09:55 AM, Jet Chen wrote:
> 
> Jet,
> 
>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next
>> commit 0629f3b8c33899140b48d5897259eab8ebae78ca
>> Author:     Larry Finger <Larry.Finger@...inger.net>
>> AuthorDate: Wed May 21 16:25:36 2014 -0500
>> Commit:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> CommitDate: Fri May 23 11:33:56 2014 +0900
>>
>>      staging: r8192ee: Turn on build of the new driver
>>          In addition, this commit contains a TODO file for this driver
>>          Signed-off-by: Larry Finger <Larry.Finger@...inger.net>
>>      Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> 
> The splat comes from the driver trying to register a rate-control algorithm that 
> is already registered. That could happen because a driver is calling the 
> registration routine twice, or because more than one driver is using the same 
> routine name. As I think there is code to prevent the former, and I have never 
> seen that splat here, I suspect that more than one driver has used the name. On 
> my real hardware, I can only have one of these devices in the machine at a time.
> 
> Is if possible to test the attached patch to see if it fixes the problem? If 
> not, could you get a listing of the loaded modules at the time of the splat? If 
> this is not the fix, I will try to duplicate it here.
> 
> Thanks,
> 
> Larry
> 

That patch fixes the problem.

Tested-by: Jet Chen <jet.chen@...el.com>

Thanks,
Jet
--
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/