[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZkXdXO4Xb83270V7@smile.fi.intel.com>
Date: Thu, 16 May 2024 13:18:04 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: NĂcolas F. R. A. Prado <nfraprado@...labora.com>
Cc: Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/1] spi: Remove unneded check for orig_nents
On Wed, May 15, 2024 at 05:09:33PM -0400, NĂcolas F. R. A. Prado wrote:
> On Tue, May 07, 2024 at 11:10:27PM +0300, Andy Shevchenko wrote:
> > Both dma_unmap_sgtable() and sg_free_table() in spi_unmap_buf_attrs()
> > have checks for orig_nents against 0. No need to duplicate this.
> > All the same applies to other DMA mapping API calls.
> >
> > Also note, there is no other user in the kernel that does this kind of
> > checks.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>
> this commit caused a regression which I reported here:
>
> https://lore.kernel.org/all/d3679496-2e4e-4a7c-97ed-f193bd53af1d@notapiano
>
> along with some thoughts on the cause and a possible solution, though I'm not
> familiar with this code base at all and would really appreciate any feedback you
> may have.
Thanks for the report and preliminary analysis!
I'll look at it hopefully sooner than later.
But at least what I think now is that my change revealed a problem somewhere
else, because that's how DMA mapping / streaming APIs designed, it's extremely
rare to check orig_nents field.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists