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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 C068FC433F5 for ; Fri, 3 Sep 2021 15:52:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AC4D9610E5 for ; Fri, 3 Sep 2021 15:52:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349756AbhICPxV (ORCPT ); Fri, 3 Sep 2021 11:53:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57696 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235629AbhICPxT (ORCPT ); Fri, 3 Sep 2021 11:53:19 -0400 Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D406C061575 for ; Fri, 3 Sep 2021 08:52:19 -0700 (PDT) Received: by mail-lf1-x136.google.com with SMTP id l10so12609314lfg.4 for ; Fri, 03 Sep 2021 08:52:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Kr5rIfOe6Hwe2+y+jDes91fVUZ+f9S7J89384UtJgA8=; b=N8R50bKnZffPltj2pL6sAt/boekXEIz4AQ9Z/o/XuD4vPBxfG3r/2QGNeC3Td8/XlQ R0kZIgMPO8AoZ5aHXt7NM2HAmls86mjYLAHi42E+wudU8oKf8/JE6qalzvKuxXxORS9D NAlDdP45oLxOK+MFKC/0wdIbO7rTVRb8fcucQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Kr5rIfOe6Hwe2+y+jDes91fVUZ+f9S7J89384UtJgA8=; b=sg8C9V25fmhlgh5PI5SZ++W5KCo8JUdJw5CKGNbQhfBQX+rO1OLp3Ldsjg90w84+DE aRvgEXtLVqjkOzgH6aJFIjUe1ngQ0ecoxnNAh1Wu4UuoOFDta/Wdu1C0bE+4hE0lBPOg v9GEFlyLTVH9KRtijTs4s9A7T8tUY/s7yPy0u5Mlszlp2TE5KT3jORO6XWUtfXSil1io wTNVxNyfL6AikJFS9QibqzfqvzTROIthMDCDhzm5As05MKGXCMjaYGGX3SRkcgyU0fh2 PG8rTemdR5LEcx/hqSb6+T+Lzm+c4FenGJniYjhFtORc/wQxvx2rNyC4QbmTH2ZR+ywT SgQQ== X-Gm-Message-State: AOAM530EpALil6mnp/sofYs9anMS12AxU+qoJs47y67ZEcbxcfXIQ7NI dvu9d7InwOcNV16Xax1KGlc+BSWNSNNO9ChS53o= X-Google-Smtp-Source: ABdhPJyVDcCLxufizkt9s76MangxkOFfzatuQ/IIQosvROTVvmqAXu5fBHjy3TbHu3PJWuzIfxx67w== X-Received: by 2002:ac2:4e62:: with SMTP id y2mr3366732lfs.9.1630684337333; Fri, 03 Sep 2021 08:52:17 -0700 (PDT) Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com. [209.85.167.48]) by smtp.gmail.com with ESMTPSA id c19sm625234ljn.75.2021.09.03.08.52.16 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Sep 2021 08:52:16 -0700 (PDT) Received: by mail-lf1-f48.google.com with SMTP id bq28so12590519lfb.7 for ; Fri, 03 Sep 2021 08:52:16 -0700 (PDT) X-Received: by 2002:a05:6512:3da5:: with SMTP id k37mr3415205lfv.655.1630684336092; Fri, 03 Sep 2021 08:52:16 -0700 (PDT) MIME-Version: 1.0 References: <20210827164926.1726765-1-agruenba@redhat.com> In-Reply-To: From: Linus Torvalds Date: Fri, 3 Sep 2021 08:52:00 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 00/19] gfs2: Fix mmap + page fault deadlocks To: Andreas Gruenbacher Cc: Alexander Viro , Christoph Hellwig , "Darrick J. Wong" , Paul Mackerras , Jan Kara , Matthew Wilcox , cluster-devel , linux-fsdevel , Linux Kernel Mailing List , ocfs2-devel@oss.oracle.com, kvm-ppc@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 1, 2021 at 12:53 PM Andreas Gruenbacher wrote: > > So there's a minor merge conflict between Christoph's iomap_iter > conversion and this patch queue now, and I should probably clarify the > description of "iomap: Add done_before argument to iomap_dio_rw" that > Darrick ran into. Then there are the user copy issues that Al has > pointed out. Fixing those will create superficial conflicts with this > patch queue, but probably nothing serious. > > So how should I proceed: do you expect a v8 of this patch queue on top > of the current mainline? So if you rebase for fixes, it's going to be a "next merge window" thing again. Personally, I'm ok with the series as is, and the conflict isn't an issue. So I'd take it as is, and then people can fix up niggling issues later. But if somebody screams loudly.. Linus