Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp582584img; Thu, 28 Feb 2019 04:41:28 -0800 (PST) X-Google-Smtp-Source: AHgI3IZjjIO0jIindVikdh5k+9Nn1HoYQluzBOgDBWhUqrTYPGWhg2hqeHMWSWq9ad31v/znpbZ5 X-Received: by 2002:a63:3087:: with SMTP id w129mr6486031pgw.199.1551357688260; Thu, 28 Feb 2019 04:41:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551357688; cv=none; d=google.com; s=arc-20160816; b=XfA5ZnY2WBvWmzMw7ASkkjNeMKG0HI2uMIpstTB0nkSuRnMm3WZtc1RJKJZd5Em0X0 +k7QO+FQ/a2WMmyaQ1QLP6c25WxP+3P8Ao97UAJR5mOY7OpPXieNSgmtOi5znc/T9sbC Dxla2H+fWUHG/7dehDNzYpfW7wU8ozLawgyQt1XE8l8rZ88UxUnHBraaCcBAcjpxd17M AE8yg1YmXt7nPMuNVwtdk5dYaFU93H+bnREfzHTVzo2H27Iu4RZb12yHg6bXGdYqFhqp LUOCqRCuBtszv0UGGDSEaYKj4HspHMw9GoTNoGfK2T3t5jxMaCFPzIu9LFTBSHyfWiTQ XZRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=kyaLnB1yS2uNDTq/sCdbM9/derGqD4nWTMhtRkekS5s=; b=MONvdAYSECKeAZJY+wRNUh4B5td5ArzPpHRpmOUcb9Lwx6JG3TO3bcuKRIYdszhVbS sB/uQLRNdjjTYdaQYjNs8z1YKvC35oUqH+k3N2NhE0DZN3Q3C4UxF+NQJBbYPAmvgRvf QpIvso+4NR85uGofEDqov/cvhOtwn5kC5h4Zup7gJtWLmqaU/W1EtCRW8of42AkgHHrC C0aX/UybK8PBePM2W+H4SPaxjLWJYTQWKFwFF9WomaMnUAJlH7w9w2N1qoSLtOry2ZbV jk3yqj5p4Zq49CrLcZQD2kgEA80jvrG3/uL7avh3ZxlBo/sD6yDcVzyotK0URqnfbcAI RVqA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=IbMr9pBJ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 128si17249692pgb.373.2019.02.28.04.41.12; Thu, 28 Feb 2019 04:41:28 -0800 (PST) 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=@nvidia.com header.s=n1 header.b=IbMr9pBJ; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732355AbfB1MjX (ORCPT + 99 others); Thu, 28 Feb 2019 07:39:23 -0500 Received: from hqemgate15.nvidia.com ([216.228.121.64]:15242 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731179AbfB1MjW (ORCPT ); Thu, 28 Feb 2019 07:39:22 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate15.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Thu, 28 Feb 2019 04:39:13 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Thu, 28 Feb 2019 04:39:18 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 28 Feb 2019 04:39:18 -0800 Received: from [10.21.132.148] (10.124.1.5) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 28 Feb 2019 12:39:11 +0000 Subject: Re: [PATCH V15 14/18] block: enable multipage bvecs To: Marek Szyprowski , Ming Lei CC: Jens Axboe , , , , Theodore Ts'o , Omar Sandoval , Sagi Grimberg , Dave Chinner , Kent Overstreet , Mike Snitzer , , Alexander Viro , , , David Sterba , , "Darrick J . Wong" , , Gao Xiang , Christoph Hellwig , , Coly Li , , Boaz Harrosh , Bob Peterson , , Ulf Hansson , "linux-mmc@vger.kernel.org" , 'Linux Samsung SOC' , Krzysztof Kozlowski , Adrian Hunter , Bartlomiej Zolnierkiewicz , linux-tegra References: <20190215111324.30129-1-ming.lei@redhat.com> <20190215111324.30129-15-ming.lei@redhat.com> <6c9ae4de-c56f-a2b3-2542-da7d8b95601d@samsung.com> <0dbbee64-5c6b-0374-4360-6dc218c70d58@nvidia.com> <20190227232940.GA13319@ming.t460p> <01155e88-f021-fbe2-d048-42e303fe2935@samsung.com> From: Jon Hunter Message-ID: <83c1e25b-4aab-4374-e160-b506eea9e68f@nvidia.com> Date: Thu, 28 Feb 2019 12:39:10 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <01155e88-f021-fbe2-d048-42e303fe2935@samsung.com> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL104.nvidia.com (172.18.146.11) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1551357553; bh=kyaLnB1yS2uNDTq/sCdbM9/derGqD4nWTMhtRkekS5s=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=IbMr9pBJuBI/5AbD0dC5l3dawgXept/qlylzk0GIjWO3kmfIarTR/gWqLma/G6QW7 QA1IecDz5AXvEeEa1vA8ApQJcym13C8r5dqcQJFUMSda6+U4j4lZ0V6gU4W7aamSrX m+JRZW58fX6DtULpWLS9BsSfa4PjeWfP/3xcaEB3c22HZyi7lEpqH4l8AWCCiQl0D7 g8u2jtc3u01z33ZlZnGhXxk8gfT8LjZKgnLHRyeI+MxQUVwCBl4wHHBT/S1/WwV1cO e8wdRmwYaz3kMXRbC2iR1CDKeIJRnxvt4wP6qPVIH0DtIGLgbocKla2k/F6gPPwt7J oVQzg1220HnDQ== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/02/2019 07:51, Marek Szyprowski wrote: > Hi Ming, > > On 2019-02-28 00:29, Ming Lei wrote: >> On Wed, Feb 27, 2019 at 08:47:09PM +0000, Jon Hunter wrote: >>> On 21/02/2019 08:42, Marek Szyprowski wrote: >>>> On 2019-02-15 12:13, Ming Lei wrote: >>>>> This patch pulls the trigger for multi-page bvecs. >>>>> >>>>> Reviewed-by: Omar Sandoval >>>>> Signed-off-by: Ming Lei >>>> Since Linux next-20190218 I've observed problems with block layer on one >>>> of my test devices (Odroid U3 with EXT4 rootfs on SD card). Bisecting >>>> this issue led me to this change. This is also the first linux-next >>>> release with this change merged. The issue is fully reproducible and can >>>> be observed in the following kernel log: >>>> >>>> sdhci: Secure Digital Host Controller Interface driver >>>> sdhci: Copyright(c) Pierre Ossman >>>> s3c-sdhci 12530000.sdhci: clock source 2: mmc_busclk.2 (100000000 Hz) >>>> s3c-sdhci 12530000.sdhci: Got CD GPIO >>>> mmc0: SDHCI controller on samsung-hsmmc [12530000.sdhci] using ADMA >>>> mmc0: new high speed SDHC card at address aaaa >>>> mmcblk0: mmc0:aaaa SL16G 14.8 GiB >>> I have also noticed some failures when writing to an eMMC device on one >>> of our Tegra boards. We have a simple eMMC write/read test and it is >>> currently failing because the data written does not match the source. >>> >>> I did not seem the same crash as reported here, however, in our case the >>> rootfs is NFS mounted and so probably would not. However, the bisect >>> points to this commit and reverting on top of -next fixes the issues. >> It is sdhci, probably related with max segment size, could you test the >> following patch: >> >> https://marc.info/?l=linux-mmc&m=155128334122951&w=2 > > This seems to be fixing my issue too! Thanks! Thanks, I can confirm this fixes the issue for Tegra. So feel free to add my ... Tested-by: Jon Hunter Cheers! Jon -- nvpublic