[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99e12a04-d23f-f9e7-b02e-770e0012a794@redhat.com>
Date: Tue, 9 Dec 2025 22:05:25 +0100 (CET)
From: Sebastian Ott <sebott@...hat.com>
To: Robin Murphy <robin.murphy@....com>
cc: linux-nvme@...ts.infradead.org, iommu@...ts.linux.dev,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-xfs@...r.kernel.org, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>, Will Deacon <will@...nel.org>,
Carlos Maiolino <cem@...nel.org>
Subject: Re: WARNING: drivers/iommu/io-pgtable-arm.c:639
On Tue, 9 Dec 2025, Robin Murphy wrote:
> On 2025-12-09 11:43 am, Sebastian Ott wrote:
>> Hi,
>>
>> got the following warning after a kernel update on Thurstday, leading to a
>> panic and fs corruption. I didn't capture the first warning but I'm pretty
>> sure it was the same. It's reproducible but I didn't bisect since it
>> borked my fs. The only hint I can give is that v6.18 worked. Is this a
>> known issue? Anything I should try?
>
> nvme_unmap_data() is attempting to unmap an IOVA that was never mapped, or
> has already been unmapped by someone else. That's a usage bug.
OK, that's what I suspected - thanks for the confirmation!
I did another repro and tried:
good: 44fc84337b6e Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
bad: cc25df3e2e22 Merge tag 'for-6.19/block-20251201' of git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux
I'll start bisecting between these 2 - hoping it doesn't fork up my root
fs again...
Thanks,
Sebastian
Powered by blists - more mailing lists