linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFT][RFC][PATCH] p54: utilize cryptographic accelerator
Date: Thu, 27 Nov 2008 12:26:05 +0100	[thread overview]
Message-ID: <200811271226.05700.chunkeey@web.de> (raw)
In-Reply-To: <492DE6BD.5060206@lwfinger.net>

On Thursday 27 November 2008 01:15:57 Larry Finger wrote:
> > diff -Nurp a/drivers/net/wireless/p54/p54common.c b/drivers/net/wireless/p54/p54common.c
> > --- a/drivers/net/wireless/p54/p54common.c	2008-11-24 21:05:42.590287518 +0100
> > +++ b/drivers/net/wireless/p54/p54common.c	2008-11-24 22:06:13.951266225 +0100
> > @@ -843,6 +863,8 @@ static int p54_assign_address(struct iee
> >  
> >  	spin_lock_irqsave(&priv->tx_queue.lock, flags);
> >  	left = skb_queue_len(&priv->tx_queue);
> > +	if (left > 30)
> > +		return -ENOMEM;
> 
> The above returns with tx_queue.lock still set.
Oops, this piece should be in another patch.
So, ok it's gone now.

> --snip--
> > +		}
> > +	}
> > +
> > +	mutex_lock(&priv->conf_mutex);
> > +	skb = p54_alloc_skb(dev, P54_HDR_FLAG_CONTROL_OPSET, sizeof(*rxkey) +
> > +			sizeof(struct p54_hdr),	P54_CONTROL_TYPE_RX_KEYCACHE,
> > +			GFP_ATOMIC);
> > +	if (!skb) {
> > +		mutex_unlock(&priv->conf_mutex);
> > +		return -ENOMEM;
> > +	}
> > +
> > +	rxkey = (struct p54_keycache *)skb_put(skb, sizeof(*rxkey));
> > +	rxkey->entry = cpu_to_le16(key->keyidx);
> > +	rxkey->key_id = cpu_to_le16(key->keyidx);
> 
> Sparse objects to the above two statments because key->keyidx is of type s8, and
> both rxkey->entry and rxkey->key_id are of type u8. A conversion to le16 is not
> needed.
> 
> A patch for both problems is below:
Thanks... I guess the final RFT/RFC will be ready on friday/saturday.
there are a two outstanding issues:
	- do we need to swap CCMP's IV as well?
	- does MIC failure & replay detection work?
		(or did you test that, when you were working with TKIP?)

Regards,
	Chr

  reply	other threads:[~2008-11-27 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 21:15 [RFT][RFC][PATCH] p54: utilize cryptographic accelerator Christian Lamparter
2008-11-25  3:52 ` Larry Finger
2008-11-27  0:15 ` Larry Finger
2008-11-27 11:26   ` Christian Lamparter [this message]
2008-11-27 14:37     ` Larry Finger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200811271226.05700.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).