Received: by 10.213.65.68 with SMTP id h4csp38978imn; Mon, 19 Mar 2018 18:49:17 -0700 (PDT) X-Google-Smtp-Source: AG47ELskoKvESEz2u76iZXMNLU0wAARDRZqGTaZ7V00imNca69QKez51dhXRDCiH8QNXeEKtijQ0 X-Received: by 2002:a17:902:52e6:: with SMTP id a93-v6mr10127523pli.10.1521510557640; Mon, 19 Mar 2018 18:49:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521510557; cv=none; d=google.com; s=arc-20160816; b=bh77ovLfWoQat8fl20YqSfUUw9nwn1q0AqcWV4CGXxq9RuC3u8w1JIhkrf35JpNjZ7 dr4IlGfsbnOyuBEr5EexizY/CttJwhBm9LCxRfRKhQj2truKTDB7yGneeKdSJ9nDQnIW X2IMEiauIVelu+syqdVM17I5/v0+q/tZHHeh3Qc3rnyiKgUqR+I4dY/zY69Xtrk/c/u9 TGfyr13K/VUT3NJtUs7zAO0Z/UzZSggVY3lmDkns+BJd4zjqG6L9yOVvQ54ma/q08H8+ wac58USZNgwXB/Cf3Te1AuxzzQLMrWy1CbKmTCetG+4oA7hgfiRnBrsGGVGHGSG+be2s dJmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=nXRNjUwdaKTiDjFjgYjzeg8H861d6puwC/5H4CHI1BQ=; b=0lOMpxyH+BgG4/ZumqipW0nFfHOGke9QSWt7L0eOvW7O6pGMKOMtnqkoDjavINSxu0 BlzuFFV/8CLeE6CrFMUXGRgaCj/eu41zya4CRqHO94M3oaN4PH+Ch21F3NgmYz+xmPpG Y2N0w/MSiTf3zny9qLGyVStp/45VaSJNrFt7gMnsFG2r9T7Zt59UqthlhTR2Y82fA98B YqvX8BN1NlCNIfPU+G9NsHhOdYcz7aLmudNLXw74fQ/63rKOxM/YHMUw78TD3p5gAXmj v7dt4V5I5YW4dL8bbdSYmRhAHiI8/YoWioCKelvxpZA9YLdSyeAyrEMj78w0k/5muY1L qI8g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f12si414443pgq.64.2018.03.19.18.49.03; Mon, 19 Mar 2018 18:49:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030529AbeCST4f (ORCPT + 99 others); Mon, 19 Mar 2018 15:56:35 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:55924 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S969347AbeCST42 (ORCPT ); Mon, 19 Mar 2018 15:56:28 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CECD440006E6; Mon, 19 Mar 2018 19:56:27 +0000 (UTC) Received: from mguzik (ovpn-204-113.brq.redhat.com [10.40.204.113]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DE3EA2166BB2; Mon, 19 Mar 2018 19:56:26 +0000 (UTC) Date: Mon, 19 Mar 2018 20:56:24 +0100 From: Mateusz Guzik To: Stephen Rothwell Cc: Al Viro , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: build failure after merge of the vfs tree Message-ID: <20180319195623.o7h7munci7pixilo@mguzik> References: <20180319170627.04eae43b@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180319170627.04eae43b@canb.auug.org.au> User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 19 Mar 2018 19:56:27 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Mon, 19 Mar 2018 19:56:27 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'mguzik@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 19, 2018 at 05:06:27PM +1100, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/super.c: In function 'do_thaw_all_callback': > fs/super.c:942:3: error: implicit declaration of function 'emergency_thaw_bdev'; did you mean 'emergency_remount'? [-Werror=implicit-function-declaration] > emergency_thaw_bdev(sb); > ^~~~~~~~~~~~~~~~~~~ > emergency_remount > > Caused by commit > > 92afc556e622 ("buffer.c: call thaw_super during emergency thaw") > > I have reverted that commit for today. > Oops, did not test with CONFIG_BLOCK disabled. The sysrq func itself is guarded with it so imho the right fixup is to do the same thing: diff --git a/fs/super.c b/fs/super.c index 5fa9a8d..86b5575 100644 --- a/fs/super.c +++ b/fs/super.c @@ -935,6 +935,7 @@ void emergency_remount(void) } } +#ifdef CONFIG_BLOCK static void do_thaw_all_callback(struct super_block *sb) { down_write(&sb->s_umount); @@ -968,6 +969,7 @@ void emergency_thaw_all(void) schedule_work(work); } } +#endif /* * Unnamed block devices are dummy devices used by virtual -- Mateusz Guzik