From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: syzbot <syzbot+74cc7d98ae5484c2744d@syzkaller.appspotmail.com>,
brauner@kernel.org, chao@kernel.org, dhavale@google.com,
djwong@kernel.org, huyue2@coolpad.com,
jefflexu@linux.alibaba.com, linux-erofs@lists.ozlabs.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiang@kernel.org
Subject: Re: [syzbot] [iomap?] WARNING in iomap_iter (3)
Date: Tue, 15 Oct 2024 18:39:02 +0800 [thread overview]
Message-ID: <62f54645-53cc-46d3-aaab-8583ed7f1a68@linux.alibaba.com> (raw)
In-Reply-To: <5f85c28d-5d06-4639-9453-41c38854173e@linux.alibaba.com>
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@linux.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
prev parent reply other threads:[~2024-10-15 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 9:03 syzbot
2024-10-15 9:10 ` Gao Xiang
2024-10-15 9:23 ` Gao Xiang
2024-10-15 9:45 ` syzbot
2024-10-15 9:46 ` Gao Xiang
2024-10-15 10:09 ` syzbot
2024-10-15 10:39 ` Gao Xiang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62f54645-53cc-46d3-aaab-8583ed7f1a68@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=dhavale@google.com \
--cc=djwong@kernel.org \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+74cc7d98ae5484c2744d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiang@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®