From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 87887C35679 for ; Mon, 24 Feb 2020 09:03:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5EE1A2082E for ; Mon, 24 Feb 2020 09:03:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727240AbgBXJDV (ORCPT ); Mon, 24 Feb 2020 04:03:21 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:48794 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726509AbgBXJDU (ORCPT ); Mon, 24 Feb 2020 04:03:20 -0500 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1j69e1-0005kF-R7; Mon, 24 Feb 2020 10:03:17 +0100 Date: Mon, 24 Feb 2020 10:03:17 +0100 From: Sebastian Andrzej Siewior To: zanussi@kernel.org Cc: LKML , linux-rt-users , Steven Rostedt , Thomas Gleixner , Carsten Emde , John Kacur , Daniel Wagner Subject: Re: [PATCH RT 19/25] userfaultfd: Use a seqlock instead of seqcount Message-ID: <20200224090317.shfeuxfukkvxvqaf@linutronix.de> References: <889f5b989b28eb7b29f21092432948cd12d97c48.1582320278.git.zanussi@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <889f5b989b28eb7b29f21092432948cd12d97c48.1582320278.git.zanussi@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-02-21 15:24:47 [-0600], zanussi@kernel.org wrote: > From: Sebastian Andrzej Siewior > > 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? Sebastian