[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220714082212.GA30886@lst.de>
Date: Thu, 14 Jul 2022 10:22:12 +0200
From: Christoph Hellwig <hch@....de>
To: Anshuman Khandual <anshuman.khandual@....com>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org, regressions@...ts.linux.dev,
linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Christoph Hellwig <hch@....de>,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
Tom Lendacky <thomas.lendacky@....com>, conor@...nel.org,
Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>
Subject: Re: [next] Kernel panic - not syncing: swiotlb_init_remap: nslabs
= 0 too small
On Thu, Jul 14, 2022 at 01:50:02PM +0530, Anshuman Khandual wrote:
> 26ffb91fa5e0fb282e8 ("swiotlb: split up the global swiotlb lock")
This has been replace with 20347fca71a387a3751f7bb270062616ddc5317a
that should fix the issue.
Powered by blists - more mailing lists