* Re: Re: [PATCH] sched: Fix implicit type conversion
@ 2021-10-25 10:00 Jiasheng Jiang
2021-10-25 10:24 ` Peter Zijlstra
0 siblings, 1 reply; 2+ messages in thread
From: Jiasheng Jiang @ 2021-10-25 10:00 UTC (permalink / raw)
To: mingo, peterz, juri.lelli, vincent.guittot, dietmar.eggemann,
rostedt, bsegall, mgorman, bristot
Cc: linux-kernel, Jiasheng Jiang
On Mon, Oct 25, 2021 at 08:57:31AM +0000, Peter Zijlstra wrote:
>> The variable 'n' is defined as ULONG. However in the cpumask_next(),
>> it is used as INT.
>> That is vulnerable and may cause overflow.
>> Therefore, it might be better to define 'n' as INT.
>-ENOPARSE
I don't understand the 'ENOPARSE'.
Please give me more details.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Re: [PATCH] sched: Fix implicit type conversion
2021-10-25 10:00 Re: [PATCH] sched: Fix implicit type conversion Jiasheng Jiang
@ 2021-10-25 10:24 ` Peter Zijlstra
0 siblings, 0 replies; 2+ messages in thread
From: Peter Zijlstra @ 2021-10-25 10:24 UTC (permalink / raw)
To: Jiasheng Jiang
Cc: mingo, juri.lelli, vincent.guittot, dietmar.eggemann, rostedt,
bsegall, mgorman, bristot, linux-kernel
On Mon, Oct 25, 2021 at 10:00:00AM +0000, Jiasheng Jiang wrote:
> On Mon, Oct 25, 2021 at 08:57:31AM +0000, Peter Zijlstra wrote:
> >> The variable 'n' is defined as ULONG. However in the cpumask_next(),
> >> it is used as INT.
> >> That is vulnerable and may cause overflow.
> >> Therefore, it might be better to define 'n' as INT.
>
> >-ENOPARSE
>
> I don't understand the 'ENOPARSE'.
> Please give me more details.
I've no idea what your changelog is trying to say, or how your patch
makes a difference.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-10-25 10:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-25 10:00 Re: [PATCH] sched: Fix implicit type conversion Jiasheng Jiang
2021-10-25 10:24 ` Peter Zijlstra
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®