From: Dan Carpenter <dan.carpenter@oracle.com>
To: "antoni.przybylik@wp.pl" <antoni.przybylik@wp.pl>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: Fwd: Re: [PATCH] staging: gdm724x: gdm_tty: corrected macro by adding brackets
Date: Tue, 1 Sep 2020 15:21:58 +0300 [thread overview]
Message-ID: <20200901122158.GX8299@kadam> (raw)
In-Reply-To: <15764d01-0602-18c6-e2b1-089b71a2061d@wp.pl>
On Tue, Sep 01, 2020 at 02:06:23PM +0200, antoni.przybylik@wp.pl wrote:
> On 01.09.2020 13:08, Greg KH wrote:
> > On Tue, Sep 01, 2020 at 12:43:11PM +0200, antoniprzybylik wrote:
> > > 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.
> > This is for a pointer, no one would ever do that :)
>
> Nobody adds a pointer to a pointer, but it's common to add to it some value
> like that:
>
> GDM_TTY_READY(myptr + 0x1000)
That won't compile at all, because it expands to "gdm + 0x1000->tty_dev".
>
> > But, if you really worry about this, turn it into an inline function,
> > that way you get the proper typedef safety, which is what something like
> > this should really be, not a macro.
>
> How to do it? Do I need to send another patch?
Yeah. If you want. Or you could just find something else to patch.
Probably just find a different bug and fix that instead... If at first
you don't succeed, there are tons of other stuff to work on and maybe
you will succeed there. ;)
regards,
dan carpenter
next prev parent reply other threads:[~2020-09-01 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e11b8f5e-1b85-fe24-36d5-c8d707ce4e66@wp.pl>
2020-09-01 12:06 ` Fwd: Re: [PATCH] staging: gdm724x: gdm_tty: corrected macro by adding brackets antoni.przybylik
2020-09-01 12:21 ` Dan Carpenter [this message]
2020-09-01 13:10 ` Greg KH
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=20200901122158.GX8299@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