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 77814C43461 for ; Tue, 8 Sep 2020 19:04:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3B23220757 for ; Tue, 8 Sep 2020 19:04:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1599591882; bh=4Tkg7KbvGrLsecIW/3tBZUo+ZWnQ0fnWGON/6Thj664=; h=Subject:To:Cc:From:Date:List-ID:From; b=pY/4j1HCh2XQ2ghM9dDy8Fb9RmVSzSNw/n7fxviNOXAd6X/I9BeB6VwfiKLjfwgg9 7f314Ouk8CSLPiMJzA8r4WrmmMGMKggtqCRCN557eT9hn8Y/eM8dUDZ8PI4PeJJaf1 CoFDd0Zy9Xw5C6ZjxhIxoE6ACQYGlbgQn+B+gG2M= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731421AbgIHTDM (ORCPT ); Tue, 8 Sep 2020 15:03:12 -0400 Received: from wforward3-smtp.messagingengine.com ([64.147.123.22]:45631 "EHLO wforward3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731278AbgIHQHx (ORCPT ); Tue, 8 Sep 2020 12:07:53 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id 613BCF66; Tue, 8 Sep 2020 08:27:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 08 Sep 2020 08:27:49 -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=4odmrf kmPz61Cq6VFogVCyBAzeimFahkzh0EkgebJ+0=; b=L/FkIBzZVzr/tmdStLh3J5 SHxdLlIkzNjZEe8Jk+mMKDQTUZTQV5i2m5qLK4QCULZQh4Xh0EiiHV0DPjUYHy3M 15imn9HwMBVMAQ47UZjki8MREHFgk9k4dBZDF855jP9q3SPffztyz7A91ItOFxbj /OYwxRHW8B3UOuC1/pXhi5POGUe059eiO+j68I2/j/LHSX+SwGo6CrPpc5KYc6La K+KSfIuaFBoUQCVfFEz+OCYhlY43qh1o9vqt6zPnsQCGFuxklcsg0MKZzQp+CKLl d760rl7wwiRU7DUCms2CXT0R6PnZF5ecEdUqpjc6wrtAu/QB8X4zGIfur/WdoJzg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudehfedgfeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvffhfffkgggtgfesthekredttd dtlfenucfhrhhomhepoehgrhgvghhkhheslhhinhhugihfohhunhgurghtihhonhdrohhr gheqnecuggftrfgrthhtvghrnhepieetveehuedvhfdtgfdvieeiheehfeelveevheejud etveeuveeludejjefgteehnecukfhppeekfedrkeeirdejgedrieegnecuvehluhhsthgv rhfuihiivgepudenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd 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 A12B33280065; Tue, 8 Sep 2020 08:27:48 -0400 (EDT) Subject: FAILED: patch "[PATCH] block: ensure bdi->io_pages is always initialized" failed to apply to 4.19-stable tree To: axboe@kernel.dk, hch@lst.de, hirofumi@mail.parknet.co.jp Cc: From: Date: Tue, 08 Sep 2020 14:27:54 +0200 Message-ID: <159956807487205@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.19-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;