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  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, 5 May 2020 17:05:36 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Marco Elver <elver@...gle.com>
Cc:     "Paul E. McKenney" <paulmck@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        "Steven Rostedt (VMware)" <rostedt@...dmis.org>,
        Kees Cook <keescook@...omium.org>,
        Mike Rapoport <rppt@...ux.ibm.com>,
        Arvind Sankar <nivedita@...m.mit.edu>,
        Dominik Brodowski <linux@...inikbrodowski.net>,
        Alexander Potapenko <glider@...gle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        clang-built-linux <clang-built-linux@...glegroups.com>,
        Will Deacon <will@...nel.org>
Subject: Re: [PATCH] kcsan: fix section mismatch for __write_once_size/blacklisted_initcalls

On Tue, May 5, 2020 at 4:17 PM 'Marco Elver' via Clang Built Linux
<clang-built-linux@...glegroups.com> wrote:
> On Tue, 5 May 2020 at 16:11, Arnd Bergmann <arnd@...db.de> wrote:
> > So far, my randconfig checks found two such instances, one for read_once
> > and one for write_once. There are probably a couple more in random
> > configurations, but I guess they are rare enough that we can just work
> > around them like this.
>
> [+Cc Will]
>
> Thanks for testing and fixing this. Note that this may no longer be
> necessary once Will's patches land. Also noted here:
> https://lkml.kernel.org/r/CANpmjNNw6M9Gqj6WGTHH4Cegu8roTVu5x6Vqs_tCBxX3gPwL4A@mail.gmail.com
>
> For reference, Will's series:
> https://lore.kernel.org/lkml/20200421151537.19241-1-will@kernel.org/

Right, good point. If that is going to get merged for the same release, we don't
need my workarounds and I'll just keep them applied locally in my linux-next
randconfig tree for the moment.

      Arnd

Powered by blists - more mailing lists