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=-9.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 E2EDEC43461 for ; Tue, 8 Sep 2020 15:48:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9D1C523F5C for ; Tue, 8 Sep 2020 15:48:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1599580092; bh=PSqcgwFZujuE+CBpx9I7AFO8Lc677YLNdb+WT6UaS40=; h=Subject:To:Cc:From:Date:List-ID:From; b=XaKtTWWsQSPjSEqEHWfyOANNuhe5XVNuSFIFwUVe9Ym2pL1CEDooeNZj7T9ZYrlOp I9zm56yvn6WUiTACyONeXvJeTmkikGmhpsKTsnVnQ85SCmU0znHtG07/6BOvsVaqAm Xv1hoAXjpZfkLRueEax+46zdJnuvQ0QT6qH8KPtk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730481AbgIHPr7 (ORCPT ); Tue, 8 Sep 2020 11:47:59 -0400 Received: from wforward3-smtp.messagingengine.com ([64.147.123.22]:60649 "EHLO wforward3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730585AbgIHPrN (ORCPT ); Tue, 8 Sep 2020 11:47:13 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id EF460FC0; Tue, 8 Sep 2020 08:27:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 08 Sep 2020 08:27:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=F9Ps5Y whDRypAMLNAKuUKZVlnu7n+WCwSTptlNVDPzE=; b=OfBkhnZLfqepfBjwKAztvV 3cEGMHzF2zVG9dVQhB7aGroEbeWh4xFohaYh6VauVFAwQ6+VgVKx72vXMOtBA8T+ r0ld/31/IhM/mzwu8Q158SkvRInHVAdR06TC9gY8PMbj6m3BTPxJvRoKdw55+8/D KqHqouBl2ofJnRWZHKQt3ltI1ANZVrudiZTNCeI7NzhKfUwj5EtpEQZenOhFnaah 6RJkxLEOSzv7KmL0dgG4sYJlLX5QHYN8UPYtM5BGZMy/JqP//yqh0fwxrNQuzLhO zhpoapU+koI8wMSNS8P8SKTlhsYFmksdt3nJgSUX9UfG0U2H3wbDgrB+k8lH6pmQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudehfedgfeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvffhfffkgggtgfesthekredttd dtlfenucfhrhhomhepoehgrhgvghhkhheslhhinhhugihfohhunhgurghtihhonhdrohhr gheqnecuggftrfgrthhtvghrnhepieetveehuedvhfdtgfdvieeiheehfeelveevheejud etveeuveeludejjefgteehnecukfhppeekfedrkeeirdejgedrieegnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) by mail.messagingengine.com (Postfix) with ESMTPA id A49B2306467D; Tue, 8 Sep 2020 08:27:40 -0400 (EDT) Subject: FAILED: patch "[PATCH] block: ensure bdi->io_pages is always initialized" failed to apply to 4.14-stable tree To: axboe@kernel.dk, hch@lst.de, hirofumi@mail.parknet.co.jp Cc: From: Date: Tue, 08 Sep 2020 14:27:53 +0200 Message-ID: <15995680734215@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ANSI_X3.4-1968 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org The patch below does not apply to the 4.14-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . thanks, greg k-h ------------------ original commit in Linus's tree ------------------ >From de1b0ee490eafdf65fac9eef9925391a8369f2dc Mon Sep 17 00:00:00 2001 From: Jens Axboe Date: Mon, 31 Aug 2020 11:20:02 -0600 Subject: [PATCH] block: ensure bdi->io_pages is always initialized If a driver leaves the limit settings as the defaults, then we don't initialize bdi->io_pages. This means that file systems may need to work around bdi->io_pages == 0, which is somewhat messy. Initialize the default value just like we do for ->ra_pages. Cc: stable@vger.kernel.org Fixes: 9491ae4aade6 ("mm: don't cap request size based on read-ahead setting") Reported-by: OGAWA Hirofumi Reviewed-by: Christoph Hellwig Signed-off-by: Jens Axboe diff --git a/block/blk-core.c b/block/blk-core.c index d9d632639bd1..10c08ac50697 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -539,6 +539,7 @@ struct request_queue *blk_alloc_queue(int node_id) goto fail_stats; q->backing_dev_info->ra_pages = VM_READAHEAD_PAGES; + q->backing_dev_info->io_pages = VM_READAHEAD_PAGES; q->backing_dev_info->capabilities = BDI_CAP_CGROUP_WRITEBACK; q->node = node_id;