linux-kernel - Re: [PATCH] kernel: cpu: send CPU_UP

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]

Message-ID: <20170715063811.GA10435@kroah.com>
Date:   Sat, 15 Jul 2017 08:38:11 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Channagoud Kadabi <ckadabi@...eaurora.org>
Cc:     tglx@...uxtronix.de, rusty@...tcorp.com.au, tj@...nel.org,
        akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org
Subject: Re: [PATCH] kernel: cpu: send CPU_UP_CANCELLED notification

On Fri, Jul 14, 2017 at 02:50:28PM -0700, Channagoud Kadabi wrote:
> If any of the callbacks during cpu up fail undo_cpu_up calls the
> teardown call backs to rollback states but does not send
> CPU_UP_CANCELLED. As on 4.9 kernel some drivers still use the
> notification mechanism for cpu hotplug we need to send
> CPU_UP_CANCELLED notification so drivers can rollback whatever
> they did during cpu up.
> 
> Signed-off-by: Channagoud Kadabi <ckadabi@...eaurora.org>
> ---
>  kernel/cpu.c | 1 +
>  1 file changed, 1 insertion(+)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>