Re: [PATCH 1/2] mac80211: Adding HW flag IEEE80211_HW_CRYPTO_ENABLED

[Yogesh Ashok Powar <yogeshp@marvell.com>]

On Thu, Apr 21, 2011 at 05:33:56AM -0700, Johannes Berg wrote:
> On Thu, 2011-04-21 at 17:45 +0530, Yogesh Ashok Powar wrote:
> 
> > @@ -101,6 +101,9 @@ static int ieee80211_key_enable_hw_accel(struct ieee80211_key *key)
> >  
> >  	if (!ret) {
> >  		key->flags |= KEY_FLAG_UPLOADED_TO_HARDWARE;
> > +		if (key->conf.flags & IEEE80211_KEY_FLAG_GENERATE_MMIC)
> > +			key->local->crypto_tx_tailroom_needed_cnt++;
> > +
> >  		return 0;
> >  	}
> >  
> > @@ -117,6 +120,11 @@ static int ieee80211_key_enable_hw_accel(struct ieee80211_key *key)
> >  	case WLAN_CIPHER_SUITE_CCMP:
> >  	case WLAN_CIPHER_SUITE_AES_CMAC:
> >  		/* all of these we can do in software */
> > +
> > +		/* SW encryption need tailroom reservation */
> > +		BUG_ON(!key->local);
> 
> BUG_ON? Seriously? It was already dereferenced about 10 times here... In
> any case, this isn't right.
> 
> > @@ -156,6 +164,11 @@ static void ieee80211_key_disable_hw_accel(struct ieee80211_key *key)
> >  			  key->conf.keyidx, sta ? sta->addr : bcast_addr, ret);
> >  
> >  	key->flags &= ~KEY_FLAG_UPLOADED_TO_HARDWARE;
> > +
> > +	if ((key->conf.flags & IEEE80211_KEY_FLAG_GENERATE_MMIC)
> > +				&& key->local->crypto_tx_tailroom_needed_cnt)
> > +		key->local->crypto_tx_tailroom_needed_cnt--;
> 
> And that if (cnt) can't be right either.
> 
> 
> > +	if (key_sw_programmed && local->crypto_tx_tailroom_needed_cnt)
> > +		local->crypto_tx_tailroom_needed_cnt--;
> 
> So you're putting if (needed_cnt) everywhere because you have
> refcounting bugs? Better fix those bugs ....
I will address these comments.

> 
> 
> > +	local->crypto_tx_tailroom_needed_cnt = 0;
> 
> Not necessary, it's already 0.
> 
> 
> I don't think you understood what I said how it should work. You must
> increase the counter when the key is created, and then you can reduce it
> again when the key is uploaded and no mmic is needed.
I thought about this initially, but then realized that this will not
handle the scenario where we disable the key which needs tailroom space
reservation?  Once the last key, that needs tailroom reservation, is
disabled, we can skip the tailroom code again?

thanks
Yogesh