From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f197.google.com (mail-pg1-f197.google.com [209.85.215.197]) by kanga.kvack.org (Postfix) with ESMTP id 5B65A6B502C for ; Wed, 28 Nov 2018 21:20:58 -0500 (EST) Received: by mail-pg1-f197.google.com with SMTP id h10so254508pgv.20 for ; Wed, 28 Nov 2018 18:20:58 -0800 (PST) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id a83sor495299pfj.39.2018.11.28.18.20.56 for (Google Transport Security); Wed, 28 Nov 2018 18:20:57 -0800 (PST) Subject: Re: [PATCH V12 00/20] block: support multi-page bvec References: <20181126021720.19471-1-ming.lei@redhat.com> <7096bc4e-0617-29d0-a90d-ae7caf09a16d@kernel.dk> <20181129012959.GC23249@ming.t460p> From: Jens Axboe Message-ID: <1983a2f5-07be-4102-fedc-54e2ad2e16dc@kernel.dk> Date: Wed, 28 Nov 2018 19:20:51 -0700 MIME-Version: 1.0 In-Reply-To: <20181129012959.GC23249@ming.t460p> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Ming Lei , Mike Snitzer , "Ewan D. Milne" Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Theodore Ts'o , Omar Sandoval , Sagi Grimberg , Dave Chinner , Kent Overstreet , dm-devel@redhat.com, Alexander Viro , linux-fsdevel@vger.kernel.org, Shaohua Li , linux-raid@vger.kernel.org, David Sterba , linux-btrfs@vger.kernel.org, "Darrick J . Wong" , linux-xfs@vger.kernel.org, Gao Xiang , Christoph Hellwig , linux-ext4@vger.kernel.org, Coly Li , linux-bcache@vger.kernel.org, Boaz Harrosh , Bob Peterson , cluster-devel@redhat.com On 11/28/18 6:30 PM, Ming Lei wrote: >> I'm going back and forth on those one a bit. Any concerns with >> pushing this to 4.22? > > My only one concern is about the warning of > "blk_cloned_rq_check_limits: over max segments limit" on dm multipath, > and seems Ewan and Mike is waiting for this fix. Not familiar with this issue, can you post a link to it? I'd be fine working around anything until 4.22, it's not going to be a new issue. -- Jens Axboe