From: Dan Carpenter <dan.carpenter@oracle.com>
To: antoniprzybylik <antoni.przybylik@wp.pl>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gdm724x: gdm_tty: corrected macro by adding brackets
Date: Tue, 1 Sep 2020 16:33:32 +0300 [thread overview]
Message-ID: <20200901133332.GY8299@kadam> (raw)
In-Reply-To: <20200901104311.17270-1-antoni.przybylik@wp.pl>
On Tue, Sep 01, 2020 at 12:43:11PM +0200, antoniprzybylik wrote:
^^^^^^^^^^^^^^^
Please, fix your From: header so that it says "Antoni Przybylik".
> Such macros are dangerous. Consider following example:
> #define GDM_TTY_READY(gdm) (gdm && gdm->tty_dev && gdm->port.count)
> GDM_TTY_READY(a + b)
> This macro will be expanded in such a way:
> (a + b && a + b->tty_dev && a + b->port.count)
> And it will lead to errors.
>
> Signed-off-by: Antoni Przybylik <antoni.przybylik@wp.pl>
> ---
> drivers/staging/gdm724x/gdm_tty.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/gdm724x/gdm_tty.c b/drivers/staging/gdm724x/gdm_tty.c
> index 6e813693a766..eab5c75ee5b1 100644
> --- a/drivers/staging/gdm724x/gdm_tty.c
> +++ b/drivers/staging/gdm724x/gdm_tty.c
> @@ -27,7 +27,7 @@
>
> #define MUX_TX_MAX_SIZE 2048
>
> -#define GDM_TTY_READY(gdm) (gdm && gdm->tty_dev && gdm->port.count)
> +#define GDM_TTY_READY(gdm) ((gdm) && (gdm)->tty_dev && (gdm)->port.count)
I cannot imagine a real life example where adding these parentheses will
prevent a bug. One idea it to silence this by making dereference ops
like this a special case where checkpatch.pl doesn't suggest adding
parentheses.
regards,
dan carpenter
prev parent reply other threads:[~2020-09-01 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 10:43 antoniprzybylik
2020-09-01 11:08 ` Greg KH
2020-09-01 13:33 ` Dan Carpenter [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=20200901133332.GY8299@kadam \
--to=dan.carpenter@oracle.com \
--cc=antoni.przybylik@wp.pl \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®