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=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 05FD6C5B57D for ; Wed, 3 Jul 2019 00:39:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D8895218AD for ; Wed, 3 Jul 2019 00:39:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727087AbfGCAjZ (ORCPT ); Tue, 2 Jul 2019 20:39:25 -0400 Received: from verein.lst.de ([213.95.11.211]:46642 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727069AbfGCAjZ (ORCPT ); Tue, 2 Jul 2019 20:39:25 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 7744268C7B; Wed, 3 Jul 2019 02:00:55 +0200 (CEST) Date: Wed, 3 Jul 2019 02:00:55 +0200 From: Christoph Hellwig To: Jens Axboe Cc: Christoph Hellwig , Matias Bjorling , linux-block@vger.kernel.org Subject: Re: remove bi_phys_segments and related cleanups Message-ID: <20190703000055.GA28981@lst.de> References: <20190606102904.4024-1-hch@lst.de> <20190702133406.GC15874@lst.de> <20190702182934.GA20763@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Tue, Jul 02, 2019 at 12:37:59PM -0600, Jens Axboe wrote: > > I couldn't get that to boot in my test systems even with mainline, > > but that seems to be do to systemd waiting for some crap not supported > > in the config. > > > > But with my usual test config I've just completed a test run with > > KASAN enabled on a VWC=1 driver with no issues, so this keeps puzzling > > me. > > Let me know what you want me to try. I can't reproduce it in qemu, but > it's 100% on my laptop. My qemu drives also have VWC=1, so it's not > (just) that. I seriously have no idea unfortunately. It works fine for me both on qemu and on a real WD SN720 drive on my laptop. Just for curiosity you could try to pad the bio structure and see if bloating it to the old size makes any difference. The other things that comes to mind is that when Johannes removed BIO_SEG_VALID there also were some unexplainable side effects, I'll look into seeing if there was any similarity.