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 <>
To:     Marco Elver <>
Cc:     "Paul E. McKenney" <>,
        Andrew Morton <>,
        Masami Hiramatsu <>,
        "Steven Rostedt (VMware)" <>,
        Kees Cook <>,
        Mike Rapoport <>,
        Arvind Sankar <>,
        Dominik Brodowski <>,
        Alexander Potapenko <>,
        LKML <>,
        clang-built-linux <>,
        Will Deacon <>
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
<> wrote:
> On Tue, 5 May 2020 at 16:11, Arnd Bergmann <> 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:
> For reference, Will's series:

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.


Powered by blists - more mailing lists