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.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 00C50C48BD1 for ; Thu, 10 Jun 2021 12:35:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CFD5061407 for ; Thu, 10 Jun 2021 12:35:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230212AbhFJMh1 (ORCPT ); Thu, 10 Jun 2021 08:37:27 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:37054 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229937AbhFJMhZ (ORCPT ); Thu, 10 Jun 2021 08:37:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623328529; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0EePEBe0J7x4XGzeKViGuhBAvu3PhM1WpY8j8Rkd77s=; b=A7oK6AVI1u5bjJRY5lNiRMYTMGfhY8pL3Z6YwNKQ5PSe/aD27ahVgNS5dHXOM3kY2Kmv6I 21W4UXdXKeN/cmSI0bVAacs3YR7IWfCsP9c4yha14EKxQVXLnp5uTdCwzz8XHEgChIX+2J CNdNEwr5/kGvB4OEut83hyopNeHxu1M= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-400-D9hJgavJOc2nCd_GkHOg0A-1; Thu, 10 Jun 2021 08:35:27 -0400 X-MC-Unique: D9hJgavJOc2nCd_GkHOg0A-1 Received: by mail-wr1-f72.google.com with SMTP id z4-20020adfe5440000b0290114f89c9931so824107wrm.17 for ; Thu, 10 Jun 2021 05:35:27 -0700 (PDT) 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=0EePEBe0J7x4XGzeKViGuhBAvu3PhM1WpY8j8Rkd77s=; b=l+M8Ok46FK+0TaVIlymHXORGH4zRa4LY7IsnPaICHkTAQl6YMvSvhjSL97pvivotKz c4egXKosahv8a6jFefkf/hsk6ogSaqsJolZMizRppixQpAApUsQpOBOePGUN5r5ZkX0a eGao4Uf86C7nWeIML4p2DpMOxhp0cmezfFpWXJAIs5GoQvY6NGWyj0F5U/e0TCqriBF5 CuZpi/RQ68vP9fWinB+Yp/IzBn5lDLt2wP0htcPG78KAV2E1r9pSI1rx9yTf6x+HeCy4 3bp96KQMYE1Qa86nm+my7U1LS+J5mHqfRZwe3dVlNGYMPKqOuHS8oP03GoXs7DbRnpy+ toHw== X-Gm-Message-State: AOAM530F/DWGapVcIlW0OhNjfTAeIzBzjnU1JHirzGgHmqRZLEw0YVGV KwR8DuH9yNAQyKJoI8sbxnocE2ofTQ9MqcG4t/58dpqJY/osYAsnqYjdLVTnvNJ0lM+QgvSx0+o vGVB0f4mzxCJqdwbcnHFPzf2ExyD4G1v3Hnddn22d X-Received: by 2002:adf:fb92:: with SMTP id a18mr2096809wrr.182.1623328526531; Thu, 10 Jun 2021 05:35:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxk79cdEnN+HNQ14JBR884eFY8g4LPsuyRY4eWVEaflAO1UbCjo7GdVjSUVhHywO+MOTDo9Bo6HgZMRkI4aRMU= X-Received: by 2002:adf:fb92:: with SMTP id a18mr2096799wrr.182.1623328526404; Thu, 10 Jun 2021 05:35:26 -0700 (PDT) MIME-Version: 1.0 References: <20210609130751.38a409a8@canb.auug.org.au> In-Reply-To: <20210609130751.38a409a8@canb.auug.org.au> From: Andreas Gruenbacher Date: Thu, 10 Jun 2021 14:35:15 +0200 Message-ID: Subject: Re: linux-next: build failure after merge of the gfs2 tree To: Stephen Rothwell Cc: Steven Whitehouse , Bob Peterson , Al Viro , Linux Kernel Mailing List , Linux Next Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Wed, Jun 9, 2021 at 5:08 AM Stephen Rothwell wrote: > Hi all, > > After merging the gfs2 tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > Caused by commit > > f8524fce6a88 ("iov_iter: Add iov_iter_fault_in_writeable()") > > interacting with commits > > e59c7577f5d6 ("iov_iter: separate direction from flavour") > 30da2b24a3ed ("iov_iter: make the amount already copied available to iterator callbacks") > > from the vfs tree. > > I have applied the following fix up patch (I think it is mostly right?) yes, that looks correct. I've updated the gfs2 for-next branch with a version that merges in the vfs bits, so the conflict should be gone now. Thanks, Andreas