linux-kernel - Re: Query on skip_onerr field in struct cpuhp

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1808252025590.1195@nanos.tec.linutronix.de>
Date:   Sat, 25 Aug 2018 20:27:58 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Mukesh Ojha <mojha@...eaurora.org>
cc:     lkml <linux-kernel@...r.kernel.org>
Subject: Re: Query on skip_onerr field in struct cpuhp_step

On Tue, 21 Aug 2018, Mukesh Ojha wrote:
> On 8/21/2018 7:27 PM, Thomas Gleixner wrote:
> > > If it is specifically was dependent on notifiers, did we missed to remove
> > > it as the notifiers are gone or the usecase still there?
> > As the comment says....
> 
> Thanks for your reply
> Sorry, for further question but i did not get the comment ..did you mean, we
> can remove this from the structure as notifier are not their now. ?

Yes, that's why the comment for that member says: Remove after conversion.

> Also if you are aware with the history, can you tell , why would i want to
> avoid a call in undo_cpu_up path?

Because the notifiers worked completely differently. Go back in the
git history where the initial conversion from notifiers to the state
machine happened.

Thanks,

	tglx