All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6.24] introduce MAC_FMT/MAC_ARG
Date: Fri, 31 Aug 2007 15:39:21 -0700	[thread overview]
Message-ID: <1188599961.6062.198.camel@localhost> (raw)
In-Reply-To: <1188599575.7585.62.camel@johannes.berg>

On Sat, 2007-09-01 at 00:32 +0200, Johannes Berg wrote:
> I think you got a bit too trigger-happy:
>         p += sprintf(p, "key[%d] alg=CCMP key_set=%d "
> -                    "tx_pn=%02x%02x%02x%02x%02x%02x "
> -                    "rx_pn=%02x%02x%02x%02x%02x%02x "
> +                    "tx_pn=%s "
> +                    "rx_pn=%s "
>                      "format_errors=%d replays=%d decrypt_errors=%d\n",
>                      ccmp->key_idx, ccmp->key_set,
> -                    MAC_ARG(ccmp->tx_pn), MAC_ARG(ccmp->rx_pn),
> +                    print_mac(mac, ccmp->tx_pn), print_mac(mac2, ccmp->rx_pn),
> 
> the PN is a number, not a MAC address :) The fact that it used MAC_ARG,
> was, I guess, just laziness of the original author since the PN is also
> 6 bytes long. That said, I can live with it being printed this way too,
> it's just a bit weird.

Yes, that was one of the dodgy ones.
I didn't actually realize it wasn't a MAC address though.

I think all of the sprintf/seq_foo changes should be inspected.
I broke ipv6 once doing something similar to v6 addresses.

> Going to be fun to merge with my 70 outstanding patches though :)

That's a cheery definition of fun.


  reply	other threads:[~2007-08-31 22:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 18:46 [PATCH net-2.6.24] introduce MAC_FMT/MAC_ARG Johannes Berg
2007-08-23 16:01 ` Joe Perches
2007-08-23 16:12   ` Johannes Berg
2007-08-23 17:08     ` John W. Linville
2007-08-25  6:14       ` David Miller
2007-08-26  0:09 ` Joe Perches
2007-08-27 10:54   ` Johannes Berg
2007-08-27 15:44     ` Joe Perches
2007-08-27 20:41     ` David Miller
     [not found]       ` <1188248263.18004.131.camel@localhost>
2007-08-27 21:09         ` Stephen Hemminger
2007-08-27 21:11         ` David Miller
     [not found]         ` <200708281648.44352.mb@bu3sch.de>
     [not found]           ` <20070828.155419.74563234.davem@davemloft.net>
2007-08-29 17:46             ` Michael Buesch
2007-08-27 21:26       ` Joe Perches
2007-08-27 21:37         ` David Miller
     [not found]           ` <1188335521.6062.56.camel@localhost>
     [not found]             ` <20070828.142216.99461544.davem@davemloft.net>
2007-08-31 22:16               ` Joe Perches
2007-08-31 22:21                 ` Johannes Berg
2007-08-31 22:24                   ` Joe Perches
2007-08-31 22:27                     ` Johannes Berg
2007-08-31 22:32                     ` Johannes Berg
2007-08-31 22:39                       ` Joe Perches [this message]
2007-09-14 19:41                 ` Joe Perches
2007-09-14 19:48                   ` David Miller
2007-09-18  2:05                   ` David Miller
2007-09-18  2:14                     ` Joe Perches
2007-09-19  4:50                       ` Joe Perches
2007-09-19 18:11                         ` David Miller
2007-09-19 18:50                           ` Joe Perches
2007-09-19 19:54                             ` David Miller
2007-09-24 17:28                               ` Joe Perches

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=1188599961.6062.198.camel@localhost \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --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.