[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7054f182-2648-983d-3602-e69ea36f90f6@lge.com>
Date: Fri, 1 Jun 2018 10:42:10 +0900
From: Byungchul Park <byungchul.park@....com>
To: paulmck@...ux.vnet.ibm.com
Cc: jiangshanlai@...il.com, josh@...htriplett.org, rostedt@...dmis.org,
mathieu.desnoyers@...icios.com, linux-kernel@...r.kernel.org,
kernel-team@....com, joel@...lfernandes.org
Subject: Re: [RFC] rcu: Check the range of jiffies_till_xxx_fqs on setting
them
On 2018-05-31 20:17, Paul E. McKenney wrote:
> On Thu, May 31, 2018 at 11:51:40AM +0900, Byungchul Park wrote:
>> On 2018-05-31 11:18, Byungchul Park wrote:
>>> On 2018-05-29 21:01, Paul E. McKenney wrote:
>>>
>>>> One approach would be to embed the kernel_params_ops structure inside
>>>> another structure containing the limits, then just have two structures.
>>>> Perhaps something like this already exists? I don't see it right off,
>>>> but then again, I am not exactly an expert on module_param.
>>>>
>>>> Thoughts?
>>>
>>> Unfortunately, I couldn't find it. There might be no way to verify
>>> range of a variable except the way I did. Could you give your opinion
>>> about whether I should go on it?
>>
>> Like..
>
> This looks reasonable to me. Although you could make something that took
> ranges, that would be more code than what you have below, so what you
Exactly.
> have below is good. Could you please resend as a patch with Signed-off-by
> and commit log?
Sure, I will. Thanks a lot Paul.
--
Thanks,
Byungchul
Powered by blists - more mailing lists