netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <jkmaline@cc.hut.fi>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: James Ketrenos <jketreno@linux.intel.com>, netdev@oss.sgi.com
Subject: Re: [PATCH] ieee80211 subsystem
Date: Mon, 7 Feb 2005 19:57:44 -0800	[thread overview]
Message-ID: <20050208035744.GC8366@jm.kir.nu> (raw)
In-Reply-To: <420462BC.6010903@osdl.org>

On Fri, Feb 04, 2005 at 10:07:56PM -0800, Randy.Dunlap wrote:

> 6.  +struct ieee80211_ccmp_data {
> 
> +	u32 dot11RSNAStatsCCMPFormatErrors;
> +	u32 dot11RSNAStatsCCMPReplays;
> +	u32 dot11RSNAStatsCCMPDecryptErrors;
> 
> Are these MIB-mandated names?  otherwise the studlyCaps should go.

Well, I don't know whether it would be fair to say these are mandated as
variable names here, but yes, these are indeed the exact names used in
IEEE 802.11i MIB definition which is the reason for the variable names
here.

> 8.  What calls the .print_stats functions?
> static char * ieee80211_ccmp_print_stats()
> 
> Is it possible to use seq_file there instead of sprintf(),
> or is this in /sysfs (so seq_file is not possible)?

I used these for getting key information into procfs files. Conversion
to seq_file should be possible for procfs. This is of course assuming
that someone else has not used these for something else than procfs.

> Are there any overflow possibilities?

Should not be, these are used to create a procfs file of less than 500
bytes and the available buffer is at least a page. I did not yet look
how these are used in this patch or ipw2100/ipw2200 drivers, so this is
based on how I implemented this with Host AP driver.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2005-02-08  3:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 18:47 [PATCH] ieee80211 subsystem James Ketrenos
2005-02-04 22:48 ` Jeff Garzik
2005-02-05  6:07 ` Randy.Dunlap
2005-02-08  3:57   ` Jouni Malinen [this message]
2005-02-08  9:41     ` James Ketrenos
2005-02-05  8:13 ` Christoph Hellwig
2005-02-08  2:49 ` Randy.Dunlap
2005-02-08  8:24   ` James Ketrenos
2005-02-10  4:36     ` Randy.Dunlap
2005-02-08  4:29 ` Jouni Malinen
2005-02-08  9:26   ` James Ketrenos
2005-02-08 23:25     ` Jeff Garzik
2005-02-08 23:33       ` James Ketrenos
2005-02-11  0:49       ` James Ketrenos
2005-02-11 21:44         ` Jeff Garzik
2005-02-08  4:45 ` Randy.Dunlap
2005-02-08 19:13   ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2005-02-08 21:45 Jean Tourrilhes

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=20050208035744.GC8366@jm.kir.nu \
    --to=jkmaline@cc.hut.fi \
    --cc=jketreno@linux.intel.com \
    --cc=netdev@oss.sgi.com \
    --cc=rddunlap@osdl.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).