linux-kernel - Re: [PATCH] Staging: gdm724x: tty: Fix macro argument reuse that could cause side-effects.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180217121741.GC10940@kroah.com>
Date:   Sat, 17 Feb 2018 13:17:41 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Quytelda Kahja <quytelda@...alin.org>
Cc:     gs051095@...il.com, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: gdm724x: tty: Fix macro argument reuse that
 could cause side-effects.

On Fri, Feb 16, 2018 at 02:26:55PM -0800, Quytelda Kahja wrote:
> Fix a coding style warning from checkpatch.pl.  Use GNU extensions to create
> references to the results of problem macro arguments when they are evaluated so
> that they can be used safely multiple times.
> 
> Signed-off-by: Quytelda Kahja <quytelda@...alin.org>
> ---
>  drivers/staging/gdm724x/gdm_tty.c | 24 ++++++++++++++++--------
>  1 file changed, 16 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/staging/gdm724x/gdm_tty.c b/drivers/staging/gdm724x/gdm_tty.c
> index fc7682c18f20..73d39fa86d10 100644
> --- a/drivers/staging/gdm724x/gdm_tty.c
> +++ b/drivers/staging/gdm724x/gdm_tty.c
> @@ -37,14 +37,22 @@
>  
>  #define MUX_TX_MAX_SIZE 2048
>  
> -#define gdm_tty_send(n, d, l, i, c, b) (\
> -	n->tty_dev->send_func(n->tty_dev->priv_dev, d, l, i, c, b))
> -#define gdm_tty_recv(n, c) (\
> -	n->tty_dev->recv_func(n->tty_dev->priv_dev, c))
> -#define gdm_tty_send_control(n, r, v, d, l) (\
> -	n->tty_dev->send_control(n->tty_dev->priv_dev, r, v, d, l))
> -
> -#define GDM_TTY_READY(gdm) (gdm && gdm->tty_dev && gdm->port.count)
> +#define gdm_tty_send(n, d, l, i, c, b)					\
> +	({ typeof(n) n_ = (n);						\
> +		void *priv_dev = n_->tty_dev->priv_dev;			\
> +		n_->tty_dev->send_func(priv_dev, d, l, i, c, b); })
> +#define gdm_tty_recv(n, c)					\
> +	({ typeof(n) n_ = (n);					\
> +		void *priv_dev = n_->tty_dev->priv_dev;		\
> +		n_->tty_dev->recv_func(priv_dev, c); })
> +#define gdm_tty_send_control(n, r, v, d, l)				\
> +	({ typeof(n) n_ = (n);						\
> +		void *priv_dev = n_->tty_dev->priv_dev;			\
> +		n_->tty_dev->send_control(priv_dev, r, v, d, l); })
> +
> +#define GDM_TTY_READY(gdm)						\
> +	({ typeof(gdm) gdm_ = gdm;					\
> +		gdm_ && gdm_->tty_dev && gdm_->port.count; })

Ugh, that's a mess.  How about just replacing the use of these odd
macros with the "real" call instead?  The fact that they are messing
around with the tty_dev call directly is really strange and should be
made a lot more obvious, as that probably needs to be fixed up.

thanks,

greg k-h