linux-kernel - Re: [PATCH] tick/broadcast: Remove redundant code in tick_check_new

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 14 Nov 2017 11:29:26 +0800
From:   Zhenzhong Duan <zhenzhong.duan@...cle.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     mingo@...nel.org, fweisbec@...il.com,
        Srinivas REDDY Eeda <srinivas.eeda@...cle.com>,
        Joe Jin <joe.jin@...cle.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tick/broadcast: Remove redundant code in
 tick_check_new_device()

On 2017/11/14 0:54, Thomas Gleixner wrote:

> On Wed, 8 Nov 2017, Zhenzhong Duan wrote:
>
>> There is no way a timer used as broadcast clockevent device is also used as
>> percpu tick clockevent device currently.
> Correct.
>
>> It's better to put related code in tick_install_broadcast_device(), but I feel
>> it's harmless to give it back to the clockevents layer. Pls correct me if I'm
>> wrong.
> You already established, that it _cannot_ be the broadcast device and the
> per cpu device at the same time. So that condition can never be true. What
> do you want to put into tick_install_broadcast_device()? This second
> paragraph doesn't make sense, unless I'm missing something.

I didn't find the reason in long history logs while the comments saying 'If the current device is the broadcast device, do not give it back to the clockevents layer !'

If it does, tick_install_broadcast_device() is a proper place. If not, I can resend the patch with fresh description, pls confirm.

-- 
thanks
zduan