From: Sergey Organov <sorganov@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] soc: aspeed: fix a ternary sign expansion bug
Date: Fri, 23 Apr 2021 13:45:40 +0300 [thread overview]
Message-ID: <877dktuvmz.fsf@osv.gnss.ru> (raw)
In-Reply-To: <59596244622c4a15ac8cc0747332d0be@AcuMS.aculab.com> (David Laight's message of "Thu, 22 Apr 2021 16:21:40 +0000")
David Laight <David.Laight@ACULAB.COM> writes:
> From: Dan Carpenter
>> Sent: 22 April 2021 10:12
>>
>> The intent here was to return negative error codes but it actually
>> returns positive values. The problem is that type promotion with
>> ternary operations is quite complicated.
>>
>> "ret" is an int. "copied" is a u32. And the snoop_file_read() function
>> returns long. What happens is that "ret" is cast to u32 and becomes
>> positive then it's cast to long and it's still positive.
>>
>> Fix this by removing the ternary so that "ret" is type promoted directly
>> to long.
>>
>> Fixes: 3772e5da4454 ("drivers/misc: Aspeed LPC snoop output using misc chardev")
>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>> ---
>> drivers/soc/aspeed/aspeed-lpc-snoop.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/soc/aspeed/aspeed-lpc-snoop.c b/drivers/soc/aspeed/aspeed-lpc-snoop.c
>> index 210455efb321..eceeaf8dfbeb 100644
>> --- a/drivers/soc/aspeed/aspeed-lpc-snoop.c
>> +++ b/drivers/soc/aspeed/aspeed-lpc-snoop.c
>> @@ -94,8 +94,10 @@ static ssize_t snoop_file_read(struct file *file, char __user *buffer,
>> return -EINTR;
>> }
>> ret = kfifo_to_user(&chan->fifo, buffer, count, &copied);
>> + if (ret)
>> + return ret;
>>
>> - return ret ? ret : copied;
>> + return copied;
>
> I wonder if changing it to:
> return ret ? ret + 0L : copied;
>
> Might make people think in the future and not convert it back
> as an 'optimisation'.
It rather made me think: "what the heck is going on here?!"
Shouldn't it better be:
return ret ? ret : (long)copied;
or even:
return ret ?: (long)copied;
?
-- Sergey Organov
next prev parent reply other threads:[~2021-04-23 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 9:11 [PATCH] soc: aspeed: fix a ternary sign expansion bug Dan Carpenter
2021-04-22 9:24 ` Al Viro
2021-04-22 9:26 ` Al Viro
2021-04-22 14:56 ` Patrick Venture
2021-04-22 16:21 ` David Laight
2021-04-23 0:07 ` Joel Stanley
2021-04-23 7:43 ` Dan Carpenter
2021-04-23 10:45 ` Sergey Organov [this message]
2021-04-23 10:54 ` David Laight
2021-04-23 11:03 ` AW: " Walter Harms
2021-04-23 14:40 ` Sergey Organov
2021-04-23 14:55 ` David Laight
2021-04-23 15:24 ` Dan Carpenter
2021-04-23 11:14 ` Dan Carpenter
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=877dktuvmz.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=linux-aspeed@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).