[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210525144654.e41cb942a2804d08127ad48f@linux-foundation.org>
Date: Tue, 25 May 2021 14:46:54 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Trent Piepho <tpiepho@...il.com>
Cc: linux-kernel@...r.kernel.org, andy@...nel.org, oskar@...ra.com,
Daniel Latypov <dlatypov@...gle.com>,
Yiyuan Guo <yguoaz@...il.com>
Subject: Re: [PATCH v2 1/2] lib/math/rational.c: Fix divide by zero
On Tue, 25 May 2021 07:42:49 -0700 Trent Piepho <tpiepho@...il.com> wrote:
> If the input is out of the range of the allowed values, either larger
> than the largest value or closer to zero than the smallest non-zero
> allowed value, then a division by zero would occur.
>
> In the case of input too large, the division by zero will occur on the
> first iteration. The best result (largest allowed value) will be found
> by always choosing the semi-convergent and excluding the denominator
> based limit when finding it.
>
> In the case of the input too small, the division by zero will occur on
> the second iteration. The numerator based semi-convergent should not be
> calculated to avoid the division by zero. But the semi-convergent vs
> previous convergent test is still needed, which effectively chooses
> between 0 (the previous convergent) vs the smallest allowed fraction
> (best semi-convergent) as the result.
Is there any known userspace workload which can trigger this?
IOW, should it be backported into -stable and fast-tracked into 5.13 or
will a 5.14 merge suffice?
Powered by blists - more mailing lists