linux-kernel - Re: [PATCH -lkmm] tools/memory-model/README: Update klitmus7 compat table

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: <20220506190431.GG1790663@paulmck-ThinkPad-P17-Gen-1>
Date:   Fri, 6 May 2022 12:04:31 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     Akira Yokosawa <akiyks@...il.com>
Cc:     Luc Maranget <luc.maranget@...ia.fr>,
        Jade Alglave <j.alglave@....ac.uk>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH -lkmm] tools/memory-model/README: Update klitmus7 compat
 table

On Fri, May 06, 2022 at 11:55:02AM +0900, Akira Yokosawa wrote:
> On Mon, 2 May 2022 09:50:58 -0700,
> Paul E. McKenney wrote:
> > On Mon, May 02, 2022 at 09:05:09PM +0900, Akira Yokosawa wrote:
> >> EXPORT_SYMBOL of do_exec() was removed in v5.17.  Unfortunately,
> >> kernel modules from klitmus7 7.56 have do_exec() at the end of
> >> each kthread.
> >>
> >> herdtools7 7.56.1 has addressed the issue.
> >>
> >> Update the compatibility table accordingly.
> >>
> >> Signed-off-by: Akira Yokosawa <akiyks@...il.com>
> >> Cc: Luc Maranget <luc.maranget@...ia.fr>
> >> Cc: Jade Alglave <j.alglave@....ac.uk>
> >> Cc: stable@...r.kernel.org # v5.17+
> >> ---
> >> Hi Paul,
> >>
> >> herdtools7 release 7.56.1 is available at
> >> https://github.com/herd/herdtools7/releases/tag/7.56.1,
> >> and "opam update/upgrade" should catch it soon.
> 
> With the help of Luc, opam repository has accepted 7.56.1.
> 
> > 
> > Good catch, thank you!
> > 
> >> I think this is worth for v5.18, albeit it is a minor update
> >> in documentation.
> > 
> > Good point, but let me give it some thought.
> 
> On the second thought, as v5.18-rc6 is expected this weekend,
> I'm OK if this update makes the next (v5.19) merge window.
> 
> This is more of a "news" type update and the "Cc: stable" tag
> should work either way.

Sounds like a plan!  I have this commit positioned to be the LKMM
pull request for the upcoming merge window.

							Thanx, Paul