From mboxrd@z Thu Jan 1 00:00:00 1970 From: "hch@lst.de" Subject: Re: ensure dma_alloc_coherent always returns zeroed memory Date: Thu, 20 Dec 2018 15:46:04 +0100 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 Return-path: Content-Disposition: inline In-Reply-To: <1545316759.14089.22.camel@synopsys.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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" 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?