From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Roman Smirnov <r.smirnov@omp.ru>, <linux-kernel@vger.kernel.org>
Cc: <lvc-project@linuxtesting.org>
Subject: Re: [PATCH] fixp-arith: prevent division by zero in fixp_sin32_rad()
Date: Sat, 31 Jan 2026 22:26:44 +0300 [thread overview]
Message-ID: <e8efff03-0c77-412c-b95d-4979a0b6f3ca@omp.ru> (raw)
In-Reply-To: <ef045b6e-14cd-a2a8-f89f-35d38776ed8b@omp.ru>
On 3/13/24 9:23 PM, Sergey Shtylyov wrote:
[...]
>> The parameter twopi can have a zero value. It is necessary
>> to prevent division by zero.
>>
>> Found by Linux Verification Center (linuxtesting.org) with Svace.
>>
>> Signed-off-by: Roman Smirnov <r.smirnov@omp.ru>
>> ---
>> include/linux/fixp-arith.h | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/linux/fixp-arith.h b/include/linux/fixp-arith.h
>> index e485fb0c1201..434eee8bd9ef 100644
>> --- a/include/linux/fixp-arith.h
>> +++ b/include/linux/fixp-arith.h
>> @@ -118,8 +118,9 @@ static inline s32 fixp_sin32_rad(u32 radians, u32 twopi)
>>
>> /*
>> * Avoid too large values for twopi, as we don't want overflows.
>> + * Also prevent division by zero.
>> */
>> - BUG_ON(twopi > 1 << 18);
>> + BUG_ON(!twopi || twopi > 1 << 18);
>
> Not really sure ATM that BUG_ON() is better than division by 0
> (which should cause exception 0 on x86 but I'm not sure about e.g.
> ARM32/64)...
Now I know what happens there: on arch/arm/ an pr_err() will be called
followed by dump_stack(); on arch/arm64/ division instruction will silently
yield 0 result...
>>
>> degrees = (radians * 360) / twopi;
>> tmp = radians - (degrees * twopi) / 360;
>>
>
> Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>
The patch does seem legitimate...
]...]
MBR, Sergey
prev parent reply other threads:[~2026-01-31 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 9:48 Roman Smirnov
2024-03-13 18:23 ` Sergey Shtylyov
2026-01-31 19:26 ` Sergey Shtylyov [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=e8efff03-0c77-412c-b95d-4979a0b6f3ca@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=r.smirnov@omp.ru \
/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®