All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH] staging: kernel.h: Prevent macro expantion bug in container_of_safe()
Date: Thu, 26 Apr 2018 16:14:10 +1000	[thread overview]
Message-ID: <87bme6mr4d.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20180426055827.GA18346@mwanda>

On Thu, Apr 26 2018, Dan Carpenter wrote:

> There aren't many users of this so it doesn't cause a problem, but we
> obviously want to use "__mptr" here instead of "ptr" to prevent the
> parameter from being executed twice.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> index b5a8e78c6c75..593fb8d250a2 100644
> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -978,7 +978,7 @@ static inline void ftrace_dump(enum ftrace_dump_mode oops_dump_mode) { }
>  	BUILD_BUG_ON_MSG(!__same_type(*(ptr), ((type *)0)->member) &&	\
>  			 !__same_type(*(ptr), void),			\
>  			 "pointer type mismatch in container_of()");	\
> -	IS_ERR_OR_NULL(ptr) ? ERR_CAST(ptr) :				\
> +	IS_ERR_OR_NULL(__mptr) ? ERR_CAST(__mptr) :			\
>  		((type *)(__mptr - offsetof(type, member))); })
>  
>  /* Rebuild everything on CONFIG_FTRACE_MCOUNT_RECORD */

Arg, of course.  Thanks.
Acked-by: NeilBrown <neilb@suse.com>

Thanks,
NeilBrown
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20180426/374eb610/attachment.sig>

      reply	other threads:[~2018-04-26  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26  5:58 [lustre-devel] [PATCH] staging: kernel.h: Prevent macro expantion bug in container_of_safe() Dan Carpenter
2018-04-26  6:14 ` NeilBrown [this message]

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=87bme6mr4d.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=lustre-devel@lists.lustre.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.