All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: joe@perches.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6.24] introduce MAC_FMT/MAC_ARG
Date: Mon, 27 Aug 2007 13:41:31 -0700 (PDT)	[thread overview]
Message-ID: <20070827.134131.41639376.davem@davemloft.net> (raw)
In-Reply-To: <1188212049.6756.18.camel@johannes.berg>

From: Johannes Berg <johannes@sipsolutions.net>
Date: Mon, 27 Aug 2007 12:54:09 +0200

> -- change macros to --
> #define MAC_FMT "%s"
> #define MAC_ARG(a) ({char __buf[18]; print_mac(a, buf); __buf})
> 
> I'm not sure we'd want that, but at the time you said it made the kernel
> significantly smaller and I doubt there's a performance problem with it
> (who prints mac addresses regularly?)

I don't think this works.

The scope of the __buf[18] array is inside of that MAC_ARG()
expression, which will be fully evaluated before constructing
the argument to printk().

Therefore printk() will be passed what is essentially a stale stack
pointer.

You'd need something like a "MAC_BUF buf;" all the callers need
to declare, and a new "buf" argument to MAC_ARG().

If this was the goal, there are better approches to this, how
about just calling:

	print_mac(dev->dev_addr);

Sure, we'll have to split up printk() calls, but in the end it's
likely still smaller and better.  And I think it's much cleaner
than this macro stuff.


  parent reply	other threads:[~2007-08-27 20:41 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 [this message]
     [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
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=20070827.134131.41639376.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=joe@perches.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.