netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] bcm43xx: iw_priv_args names should be <16 characters
Date: Fri, 14 Apr 2006 11:35:03 +0200	[thread overview]
Message-ID: <20060414093503.GF20839@harddisk-recovery.com> (raw)
In-Reply-To: <20060413102919.5e0bdb2e@localhost.localdomain>

On Thu, Apr 13, 2006 at 10:29:19AM -0700, Stephen Hemminger wrote:
> On Thu, 13 Apr 2006 15:02:27 +0200
> Erik Mouw <erik@harddisk-recovery.com> wrote:
> 
> > The room for the names in bcm43xx_priv_wx_args[] are IFNAMSIZ long and
> > IFNAMSIZ is defined as 16, so the names in bcm43xx_priv_wx_args should
> > be 15 characters (16 including the trailing \0). This patch fixes that
> > for the "set_shortpreambl", "get_shortpreambl", "set_swencryption", and
> > "get_swencryption" private calls. Patch is against 2.6.17-rc1.
> > 
> > Signed-off-by: Erik Mouw <erik@harddisk-recovery.com>
> 
> Shouldn't compiler have gagged on this?

Apparently not. At least the compiler I use doesn't warn about it (gcc
version 3.3.5 (Debian 1:3.3.5-13)).

Linus, this might be be something for sparse to check:

  struct mystruct {
	char name[16];
  };

  mystruct ms = { .name = "muchlongerthan16characters" };


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2006-04-14  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 13:02 [PATCH] bcm43xx: iw_priv_args names should be <16 characters Erik Mouw
2006-04-13 17:29 ` Stephen Hemminger
2006-04-14  9:35   ` Erik Mouw [this message]
2006-04-14 10:33     ` Mitchell Blank Jr

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=20060414093503.GF20839@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=torvalds@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).