netdev - Re: Please pull 'fixes-jgarzik' branch of wireless-2.6

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: <4766D99D.5090507@garzik.org>
Date:	Mon, 17 Dec 2007 15:18:37 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	"John W. Linville" <linville@...driver.com>
CC:	netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
	davem@...emloft.net
Subject: Re: Please pull 'fixes-jgarzik' branch of wireless-2.6

John W. Linville wrote:
> On Sat, Dec 15, 2007 at 11:31:48PM -0500, John W. Linville wrote:
> 
>> Cyrill Gorcunov (2):
>>       ieee80211_rate: missed unlock
> 
>>  net/mac80211/ieee80211_rate.c                  |    1 +
> 
>> diff --git a/net/mac80211/ieee80211_rate.c b/net/mac80211/ieee80211_rate.c
>> index 7254bd6..3260a4a 100644
>> --- a/net/mac80211/ieee80211_rate.c
>> +++ b/net/mac80211/ieee80211_rate.c
>> @@ -33,6 +33,7 @@ int ieee80211_rate_control_register(struct rate_control_ops *ops)
>>  		if (!strcmp(alg->ops->name, ops->name)) {
>>  			/* don't register an algorithm twice */
>>  			WARN_ON(1);
>> +			mutex_unlock(&rate_ctrl_mutex);
>>  			return -EALREADY;
>>  		}
>>  	}
> 
> Crud...there is a one-line fix in here that should have gone to Dave.
> 
> Jeff, (assuming Dave ACKs it) would you mind just taking it your
> way along with the other posted patches?  Since this is intended for
> 2.6.24, there should be no great maintenance hardship if it goes to
> Linus through your tree instead of Dave's.

Will do...

	Jeff




--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html