linux-kernel - Re: [PATCH V3 06/49] compiler_types.h: Add __noinstr

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CANiq72kkk6-eN3hN7OfSA5r03df42j7pAueMZurY_rTvq518Dw@mail.gmail.com>
Date:   Mon, 18 Oct 2021 13:29:11 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Lai Jiangshan <laijs@...ux.alibaba.com>
Cc:     Nick Desaulniers <ndesaulniers@...gle.com>,
        Lai Jiangshan <jiangshanlai@...il.com>,
        Miguel Ojeda <ojeda@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
        Borislav Petkov <bp@...en8.de>,
        Kees Cook <keescook@...omium.org>,
        Nathan Chancellor <nathan@...nel.org>,
        "Peter Zijlstra (Intel)" <peterz@...radead.org>,
        Sami Tolvanen <samitolvanen@...gle.com>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Marco Elver <elver@...gle.com>, Arnd Bergmann <arnd@...db.de>,
        Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [PATCH V3 06/49] compiler_types.h: Add __noinstr_section() for noinstr

On Mon, Oct 18, 2021 at 11:16 AM Lai Jiangshan <laijs@...ux.alibaba.com> wrote:
>
> I will use __section(section) in the updated patch.
>
> I don't know whether it is worth for a new version for a relatively large patchset
> with almost 50 patches since the feedback becomes less or I should wait for more
> reviews from the x86 maintainers.  Especially the second half of the patchset which
> is all about IST exceptions has no feedback since V2.

Yeah, what I meant by independent patch is that you may avoid worrying
about that fix within the series, and send it as a completely
different patch (we can also do it for you, if you prefer). It is,
after all, not really related to either this commit nor the series.

Cheers,
Miguel