[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <62f54645-53cc-46d3-aaab-8583ed7f1a68@linux.alibaba.com>
Date: Tue, 15 Oct 2024 18:39:02 +0800
From: Gao Xiang <hsiangkao@...ux.alibaba.com>
To: syzbot <syzbot+74cc7d98ae5484c2744d@...kaller.appspotmail.com>,
brauner@...nel.org, chao@...nel.org, dhavale@...gle.com, djwong@...nel.org,
huyue2@...lpad.com, jefflexu@...ux.alibaba.com,
linux-erofs@...ts.ozlabs.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org,
syzkaller-bugs@...glegroups.com, xiang@...nel.org
Subject: Re: [syzbot] [iomap?] WARNING in iomap_iter (3)
On 2024/10/15 17:10, Gao Xiang wrote:
> Hi,
>
> On 2024/10/15 17:03, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: d61a00525464 Add linux-next specific files for 20241011
>> git tree: linux-next
..
>>
>> commit 56bd565ea59192bbc7d5bbcea155e861a20393f4
>> Author: Gao Xiang <hsiangkao@...ux.alibaba.com>
>> Date: Thu Oct 10 09:04:20 2024 +0000
>>
>> erofs: get rid of kaddr in `struct z_erofs_maprecorder`
>
> I will look into that, but it seems it's just a trivial cleanup,
> not quite sure what happens here...
It seems that it's only caused by an outdated version in
next-20241011, which doesn't impact to upstream or the
latest -next:
https://lore.kernel.org/r/670e399e.050a0220.d9b66.014e.GAE@google.com
https://lore.kernel.org/r/670e3f3f.050a0220.f16b.000b.GAE@google.com
so
#syz set subsystems: erofs
#syz invalid
Powered by blists - more mailing lists