Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp990977imu; Thu, 20 Dec 2018 08:23:49 -0800 (PST) X-Google-Smtp-Source: AFSGD/VDNi2HVjYI5sBapvxx1GTZ/InV5GQs342BIodomL/zCgccDLoXatJKuFxBAAJzeKnmCz2G X-Received: by 2002:a17:902:2969:: with SMTP id g96mr24616432plb.295.1545323028963; Thu, 20 Dec 2018 08:23:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545323028; cv=none; d=google.com; s=arc-20160816; b=cv9Tv8bKborjPuZ3oqhcmW50rms97Hkt2zoQXA25vW6M81UTxLEZg9cYOlpc6AfITU iaFV2HD5A9UlN4/YX1Iq7eOCYin0IvX3wrreyCMABnujIFpjXlHslY2SQ8eiX8XmSS86 nTYyn+YnReDKKXZk2u1Qm3FstxYrawQ+pO864+i17GZIXg9naS7QA8BggV0RxOhDEMHw XplYn55Noqvgs6SM0/l14CPXlWJiNN8FCAblbx/Icbg9bVIWZ+sD6NJhxLUXSVjl3DA9 Cz4KJ1xeWa+zpIuSvxikvNc3ZTgLSAadr7VCLLxW3DNWVVOyHVaZx+IeNrahMThmE4Ta r3Sw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=e2PXnrad67j/0+OFH2wgrOvpnTOQv5l+BQmKubb5lco=; b=SgJFtJpIsCW92H1ree0mJ5PU1rOte+dojsPRB6+4mYn+m6PbwY55iEZgpAW/i0trCq ALqcgZfW56ZUe6wcOy/2qN5flpMYmLFv1ZYN87eoYEhHz4cr/s92GHQ3Zbj2Q3nVi1Hc MpuI5hqWk//7yoQtSHBV7nDMVAJQzxNJ+QTh3wMqn06waMXFlnYjU+uv7hMMugNy68Dt K6LH/Dngkop+mgVwgVWcPMr+XA5l2hnOjeCE4twliQe1cZsfwG5cugS5aAWMdz3awdgp +Q1HeLatdRm6I46Sq/i2OtjQuIlRoG+dkPE6M2zrV3FmH/3yWAEpttxp8+GjO+SsiIZ4 M3og== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b6si3841504pgm.216.2018.12.20.08.23.30; Thu, 20 Dec 2018 08:23:48 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387727AbeLTOqG (ORCPT + 99 others); Thu, 20 Dec 2018 09:46:06 -0500 Received: from verein.lst.de ([213.95.11.211]:53607 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387667AbeLTOqG (ORCPT ); Thu, 20 Dec 2018 09:46:06 -0500 Received: by newverein.lst.de (Postfix, from userid 2407) id 485C368AA6; Thu, 20 Dec 2018 15:46:04 +0100 (CET) Date: Thu, 20 Dec 2018 15:46:04 +0100 From: "hch@lst.de" To: Eugeniy Paltsev Cc: "hch@lst.de" , "linux-kernel@vger.kernel.org" , "linux-s390@vger.kernel.org" , "linux-xtensa@linux-xtensa.org" , "linux-m68k@lists.linux-m68k.org" , "vineet.gupta1@synopsys.com" , "linux-alpha@vger.kernel.org" , "linux-snps-arc@lists.infradead.org" , "iommu@lists.linux-foundation.org" , "openrisc@lists.librecores.org" , "ashutosh.dixit@intel.com" , "linux-parisc@vger.kernel.org" , "linux-c6x-dev@linux-c6x.org" , "monstr@monstr.eu" , "sparclinux@vger.kernel.org" Subject: Re: ensure dma_alloc_coherent always returns zeroed memory Message-ID: <20181220144604.GA18034@lst.de> References: <20181214082515.14835-1-hch@lst.de> <20181219165939.GA26087@lst.de> <1545316369.14089.20.camel@synopsys.com> <20181220143415.GA17726@lst.de> <1545316759.14089.22.camel@synopsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1545316759.14089.22.camel@synopsys.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote: > > I would be really surprised if that is caused by the patch to add > > the zeroing. > Me too :) > > > Can you check which commit caused the issue by bisecting > > from a known good baseline? > > Yep. At least kernel build from v4.20-rc4 (which is base for your branch) > seems to work fine. Well, the branch has quite a few commits. Can you check the commit just before the zeroing to start, and if that is already broken (which I suspect) bisect the offending commit?