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=-11.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,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 9A99FC43387 for ; Thu, 10 Jan 2019 19:56:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 699DA20879 for ; Thu, 10 Jan 2019 19:56:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547150198; bh=DsZ49SFzViLStyOM8dw36ADAg4w5gB97YTl9jZdJtA4=; h=Subject:To:Cc:From:Date:List-ID:From; b=T13OvHPu4psD8VkB8a/0zWXtQIT71HzLwTy9gNSexmN0cpt55wTC1dzSYimAYDODq g3dYPmAR+H5tlwHJGIlKNrtx9y4KB1F2fkXvwX0sRFHK12aLRAlb6/CX5tY17hqnBL ygYHiT7sTXhF7p48+rtBBTaifir9ezF0uO8UesRU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729048AbfAJT4h (ORCPT ); Thu, 10 Jan 2019 14:56:37 -0500 Received: from wnew4-smtp.messagingengine.com ([64.147.123.18]:42701 "EHLO wnew4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728382AbfAJT4f (ORCPT ); Thu, 10 Jan 2019 14:56:35 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.west.internal (Postfix) with ESMTP id 5B7DE1684; Thu, 10 Jan 2019 14:56:34 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Thu, 10 Jan 2019 14:56:34 -0500 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=fm1; bh=DZMZhp RCbR58SPJZ2KTtG2z9hWYe/0spEHdLtuuT+JU=; b=d6hdG2s1COJ7Afjtcp5LDY 6AQZk9r+I0dGzzkCPSIuPYjMu1yfM5++VKnqvhpJdgS2j60/MWPT0jo5kFhUHvBZ +d3egPUa+llR+n0i3EY1I6FRQCHLn0ldh//nikruNv0jU8j/6PkvgQW1z9pai2lP QIyuoSQYBwlPSHLz7+b0ZdiTdKQ5PKewoS2hRn7nZ8NHtPPXVI0Eyzby9yXK/2EH gMsgSyZHsDoHj7rfHJZmA+j4OIkN8S7UyosWbF+2BUWU8mL7inqQmzjqZ9BvxveM qOgS/ONUSL5DNr8ryBLKnqJKnzzSeBky7wpX4I+ny0wTERy0nZjNx7SrYXJGwQ0w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrfeefgddufeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecuogfuphgrmhfkphculdeftddtmdenucfjughrpefuvffhfffkgggtgfesthekre dttddtlfenucfhrhhomhepoehgrhgvghhkhheslhhinhhugihfohhunhgurghtihhonhdr ohhrgheqnecukfhppeekfedrkeeirdekledruddtjeenucfrrghrrghmpehmrghilhhfrh homhepghhrvghgsehkrhhorghhrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (5356596b.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id A3BCAE4693; Thu, 10 Jan 2019 14:56:32 -0500 (EST) Subject: FAILED: patch "[PATCH] dm: do not allow readahead to limit IO size" failed to apply to 4.19-stable tree To: jaegeuk@kernel.org, axboe@kernel.dk, snitzer@redhat.com Cc: From: Date: Thu, 10 Jan 2019 20:56:30 +0100 Message-ID: <154715019085246@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 c6d6e9b0f6b4201c77f2cea3964dd122697e3543 Mon Sep 17 00:00:00 2001 From: Jaegeuk Kim Date: Tue, 18 Dec 2018 09:25:37 -0800 Subject: [PATCH] dm: do not allow readahead to limit IO size Update DM to set the bdi's io_pages. This fixes reads to be capped at the device's max request size (even if user's read IO exceeds the established readahead setting). Fixes: 9491ae4a ("mm: don't cap request size based on read-ahead setting") Cc: stable@vger.kernel.org Reviewed-by: Jens Axboe Signed-off-by: Jaegeuk Kim Signed-off-by: Mike Snitzer diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c index 844f7d0f2ef8..4b1be754cc41 100644 --- a/drivers/md/dm-table.c +++ b/drivers/md/dm-table.c @@ -1927,6 +1927,9 @@ void dm_table_set_restrictions(struct dm_table *t, struct request_queue *q, */ if (blk_queue_is_zoned(q)) blk_revalidate_disk_zones(t->md->disk); + + /* Allow reads to exceed readahead limits */ + q->backing_dev_info->io_pages = limits->max_sectors >> (PAGE_SHIFT - 9); } unsigned int dm_table_get_num_targets(struct dm_table *t)