linux-kernel - Re: [PATCH] kcsan: select CONFIG

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: <20230216183626.GR2948950@paulmck-ThinkPad-P17-Gen-1>
Date:   Thu, 16 Feb 2023 10:36:26 -0800
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     Marco Elver <elver@...gle.com>
Cc:     Arnd Bergmann <arnd@...db.de>, Arnd Bergmann <arnd@...nel.org>,
        Kees Cook <keescook@...omium.org>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Josh Poimboeuf <jpoimboe@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Miroslav Benes <mbenes@...e.cz>, kasan-dev@...glegroups.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kcsan: select CONFIG_CONSTRUCTORS

On Thu, Feb 16, 2023 at 08:00:00AM +0100, Marco Elver wrote:
> On Wed, 15 Feb 2023 at 23:42, Paul E. McKenney <paulmck@...nel.org> wrote:
> >
> > On Wed, Feb 15, 2023 at 10:48:11AM +0100, Arnd Bergmann wrote:
> > > On Wed, Feb 15, 2023, at 10:25, Marco Elver wrote:
> > > > On Wed, 15 Feb 2023 at 10:15, Arnd Bergmann <arnd@...nel.org> wrote:
> > >
> > > > Looks like KASAN does select CONSTRUCTORS already, so KCSAN should as well.
> > > >
> > > > Do you have a tree to take this through, or should it go through -rcu
> > > > as usual for KCSAN patches?
> > >
> > > I don't have a tree for taking these build fixes, so it would be good if you could forward it as appropriate.
> >
> > Queued and pushed, thank you both!
> >
> > Is this ready for the upcoming merge window, or would you rather that
> > I hold off until the v6.4 merge window?  (I am tempted to treat this
> > as a bug fix, thus sending it earlier rather than later, but figured I
> > should ask.)
> 
> I'd consider it a bug fix. If it survives the usual -next exposure, no
> harm in sending it as a fix.

It passed overnight tests, so I have sent it along to -next.  If there
are no issues, I will push it by the end of this coming week (which is
the first weke of the merge window).

							Thanx, Paul