All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	netdev@vger.kernel.org, Jouni Malinen <jkm@devicescape.com>
Subject: Re: Problem authenticating using WPA with bcm43xx-softmac
Date: Wed, 07 Jun 2006 15:36:27 -0400	[thread overview]
Message-ID: <1149708987.2625.114.camel@localhost.localdomain> (raw)
In-Reply-To: <44871723.3040803@lwfinger.net>

On Wed, 2006-06-07 at 13:12 -0500, Larry Finger wrote:
> Dan Williams wrote:
> > 
> > from ieee80211softmac_wx.c: ieee80211softmac_wx_set_genie()
> > 
> >                 memcpy(mac->wpa.IE, extra, wrqu->data.length);
> >                 dprintk(KERN_INFO PFX "generic IE set to ");
> >                 for (i=0;i<wrqu->data.length;i++)
> >                         dprintk("%.2x", mac->wpa.IE[i]);
> >                 dprintk("\n");
> > 
> > the dprintk code isn't doing the right thing here, given an array of
> > bytes.  You probably want:
> > 
> >                         dprintk("%.2hhx", mac->wpa.IE[i]);
> > 
> > (ie, add the "hh" before the x to tell the print that it's a char)
> > 
> That doesn't work - the result is

Weird, does the kernel not do something that fprintf() _does_ do here?
I tested with a short C program that mimics the behavior of this chunk
of code, and "%.2x" didn't work, but "%.2hhx" certainly did.  "hh" is
supposed to mean "A following integer conversion corresponds to a signed
char or unsigned char argument".  The original conversion was converting
stuff from la-la land after the first 4 bytes (in both softmac and my
testcase), and "hh" solved it in the testcase.  I did try casting to
char, but glibc pretty much ignored that.

Dan

> %hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx%hx
> 
> I changed the line to cast the output byte as a u8 as follows:
> 
>                          dprintk("%.2x", (u8)mac->wpa.IE[i]);
> 
> This produces the line
> 
> generic IE set to dd160050f20101000050f20201000050f20201000050f202
> 
> This is the WPA IE supplied by wpa_supplicant and it matches the one used in the ndiswrapper case. 
> One mystery solved, but why doesn't it work?
> 
> Johannes - should I submit the patch to fix this printout, or would you like to do it?
> 
> Larry


  reply	other threads:[~2006-06-07 19:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 19:24 Problem authenticating using WPA with bcm43xx-softmac Larry Finger
2006-06-07 12:10 ` Johannes Berg
2006-06-07 15:47   ` Larry Finger
2006-06-07 15:51     ` Johannes Berg
2006-06-07 15:57       ` Johannes Berg
2006-06-07 17:29         ` Dan Williams
2006-06-07 18:12           ` Larry Finger
2006-06-07 19:36             ` Dan Williams [this message]
2006-06-07 19:46               ` Larry Finger
2006-06-09 11:44             ` Johannes Berg
2006-06-09 15:31               ` Larry Finger
2006-06-09 15:34                 ` Johannes Berg
2006-06-09 16:24                   ` Larry Finger
2006-06-12  1:11                   ` Larry Finger
2006-06-13  8:40                     ` Johannes Berg
2006-06-07 16:01       ` Sam Leffler
2006-06-07 16:06         ` Johannes Berg
2006-06-07 16:30           ` Larry Finger
2006-06-07 17:07           ` Larry Finger
2006-06-07 16:09         ` 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=1149708987.2625.114.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jkm@devicescape.com \
    --cc=johannes@sipsolutions.net \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.