Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp3038913ybg; Mon, 28 Oct 2019 06:31:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqw8AO9PPz3Btv+/9X3PgQuE9zPJKvp5LYYgUjDXqzxymSMsQ5zjghEEixdrS1/bGJCQh09Y X-Received: by 2002:a17:906:4056:: with SMTP id y22mr17059560ejj.188.1572269472090; Mon, 28 Oct 2019 06:31:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572269472; cv=none; d=google.com; s=arc-20160816; b=dis/h0VH7aBsYCJCMpMegWfP2V1/YDPsxKaeZAstT0xIBlPS6rzqwS1tKNabS+OfSg DsQ6znZAu/tS163yTT5TiJpN8RvhrzEAP0f2QqmwGDoVIdVj3nOm+8xrSEqj8zJb1i63 lRpviQBlsj2dM2yLaZcj2MjC9sowDXY1iI950YSJzkmAEJToS3L6/Svd4rm2XhQqEQ97 2CcRqYp4N1TLCrTGz+WT9lYCElmdVrn9wvfiGiEhZGMGoHn7SA5xcz8MOcB7VMD7AhPw 6NEMfyUYzxPB0OVxGMXEi4Jy0bx9CvJ32K7Gcb/MtKHFqQf757Bf/qmofoTysYX29A2n /CcA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=iuuv5uDzwQjuDzXqpsithGymUPeE73L3D0NeEzp8Q00=; b=PpItU/xKmjZe4KCu6JYqYvvbcr9H7mUFU02VNBQIfFQcFiFU4f1Jyel7pp8sRxmL91 +GVzvc84hno2PY2B5OGHZAouKc1o7mxJS5RHqjFDwBxJ110JdsgoGoGHDKdLzqO6TJaa LU2QsrREUQVnOKy0cTIgprmIIixA8gVpgQGkmbMxrbEbBEzZHD/dYrFdp5bTZE1sJ/SP 2/nmuLsX8mXaq023wQTwey8Lvf6P9opUEe0z0syQlEp7D1jPj4TUajXt0s6vxMGMTDxB QNMfo2uRaUn0BCKCKHCP+zsR9v7JS+Yyf4Vr+0KZk3Ck1uqs0g10uW+2OiqKV5JIh4Cv e1kg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=iqavAp5G; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v4si7675352edm.299.2019.10.28.06.30.48; Mon, 28 Oct 2019 06:31:12 -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; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=iqavAp5G; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729650AbfJ1DZM (ORCPT + 99 others); Sun, 27 Oct 2019 23:25:12 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:40343 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727119AbfJ1DZM (ORCPT ); Sun, 27 Oct 2019 23:25:12 -0400 Received: by mail-pg1-f195.google.com with SMTP id 15so5880679pgt.7 for ; Sun, 27 Oct 2019 20:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=iuuv5uDzwQjuDzXqpsithGymUPeE73L3D0NeEzp8Q00=; b=iqavAp5G7CGwQYt0MWbkcL6EzvmJ+n3PRBTotiKoMMZjLT6V4QFfwpTr+u+vwScKD3 KpVutZfM/P9dzi5rPohWCEOKxw/+MDYaZJ7evH+VuGZUyWFoNsa296gMKRSkhfQ51ZGR AgGsF8JqqNnY1CZn3OIIShlpQOZY41kmWdA5swBm3Mj+mwOVYEQVxC8p/7fdnD+0nr0T mVLJwZ+7g3Su4tEENVu3y3hcWGRx3/gSpmcsNFCFvVAmsLyoCH9a81g3aF+eE7vnrWtq FxT9W1WvQNEjC9uz3Tbv0Fk2rMA0MrGR5tpvAZB8w2SxwRGWp9rKcpiB8i4j5m1nSO8j 6xvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iuuv5uDzwQjuDzXqpsithGymUPeE73L3D0NeEzp8Q00=; b=dgcHDApJZZqMqKcwr9ILugcp+96Gci7l+zChGzK5kxaG2YyQXOwbkINxiXhK6RjGwS O5iglZQbIUPsEwaQ7wg/dHCBAUCaLK4OkpNvk2UuDefxwHRNH+HXKSJNF0kJImEi8Qqz Rszzb34756Djhe19cqfjQ8DWeaVbjRPuWvbiK2k+UrmC5ummb9RsRhhlZMgcU3gtAJhi WG9E3fHq2sKScUPqrQ4vXB5Q4WKgP6p9+eUt7gLkF6eLVdPp2FSfRq2j4NQBSSJ3iSP4 twfLCxZEThmXGIonZUb64eUC3P1+RdE4LybN4mfw9IJ+ThrWJndR250iBpkomlD5+QZW PyZQ== X-Gm-Message-State: APjAAAUHy54ew4vvY2Y94sUXOl6bgMLZ40y+qPN5AqWiU7czlPjv9onE dU6NsCk6FTeufP+cGYsiHtM/1NKUjtxvjA== X-Received: by 2002:a17:90a:4804:: with SMTP id a4mr3869284pjh.102.1572233109088; Sun, 27 Oct 2019 20:25:09 -0700 (PDT) Received: from [192.168.1.188] ([66.219.217.79]) by smtp.gmail.com with ESMTPSA id k124sm10106917pga.83.2019.10.27.20.25.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Oct 2019 20:25:07 -0700 (PDT) Subject: Re: linux-next: build failure after merge of the block tree To: Stephen Rothwell Cc: Linux Next Mailing List , Linux Kernel Mailing List References: <20191028135945.5b2ed0fa@canb.auug.org.au> From: Jens Axboe Message-ID: <27de542b-aa30-78e4-40ad-4a024e42e643@kernel.dk> Date: Sun, 27 Oct 2019 21:25:04 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20191028135945.5b2ed0fa@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/27/19 8:59 PM, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > fs/io_uring.c: In function '__io_sqe_files_unregister': > fs/io_uring.c:3010:12: error: invalid storage class for function 'io_sqe_files_unregister' > 3010 | static int io_sqe_files_unregister(struct io_ring_ctx *ctx) > | ^~~~~~~~~~~~~~~~~~~~~~~ > fs/io_uring.c:3010:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] > 3010 | static int io_sqe_files_unregister(struct io_ring_ctx *ctx) > | ^~~~~~ > > Caused by commit > > ed9e02e4bad1 ("io_uring: support for larger fixed file sets") > > I have used the block tree from next-20191025 for today. Ah shoot, forgot to update for-next, I did fix this silly error yesterday. If you're up for it, pull for-next again in 2 min and I'll have it updated. If not, I guess it'll be there in the next one. Usually doesn't matter, only asking because syzbot keeps flagging the same issue that is also fixed. -- Jens Axboe