linux-kernel - Re: [PATCH RT 19/25] userfaultfd: Use a seqlock instead of seqcount

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: <1582557257.12738.19.camel@kernel.org>
Date:   Mon, 24 Feb 2020 09:14:17 -0600
From:   Tom Zanussi <zanussi@...nel.org>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        linux-rt-users <linux-rt-users@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Carsten Emde <C.Emde@...dl.org>,
        John Kacur <jkacur@...hat.com>, Daniel Wagner <wagi@...om.org>
Subject: Re: [PATCH RT 19/25] userfaultfd: Use a seqlock instead of seqcount

On Mon, 2020-02-24 at 10:03 +0100, Sebastian Andrzej Siewior wrote:
> On 2020-02-21 15:24:47 [-0600], zanussi@...nel.org wrote:
> > From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> > 
> > v4.14.170-rt75-rc1 stable review patch.
> > If anyone has any objections, please let me know.
> 
> This is required but it is not part of the next "higher" tree
> (v4.19-RT). Which means if someone moves from v4.14-RT to the next
> tree
> (v4.19-RT in this case) that someone would have the bug again.
> 
> Could you please wait with such patches or did the I miss the v4.19-
> RT
> tree with this change?
> 

No, you didn't miss the 4.19 tree with this change - I got a little
ahead of 4.19 this time.  Will drop all the patches ahead of 4.19.

Thanks,

Tom

> Sebastian