linux-kernel - Re: [PATCH 1/3] jump_label: Warn on failed jump

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: <20180216123158.2ab0c159@gandalf.local.home>
Date:   Fri, 16 Feb 2018 12:31:58 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     Jason Baron <jbaron@...mai.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Borislav Petkov <bp@...e.de>, Juergen Gross <jgross@...e.com>,
        Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH 1/3] jump_label: Warn on failed jump_label patch

On Thu, 15 Feb 2018 16:35:58 -0600
Josh Poimboeuf <jpoimboe@...hat.com> wrote:


> > Interesting idea.  The static key's entries (i.e. tracepoint sites) are
> > in a static array.  Maybe we could rewrite the affected arrays when init
> > memory is freed.  I'm not sure whether that would be overkill though.  I
> > can tinker with it and see how it compares to the current solution.  
> 
> It turns out that something like this is already done for module init
> code.  It doesn't *remove* the entry, but it does disable it by setting
> entry->code to zero.  I'll just do the same thing right before initmem
> is freed.

Yes, I was actually going to mention to do it like the module code does.

Thanks!

-- Steve