From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Edward Adam Davis <eadavis@qq.com>,
syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com
Cc: brauner@kernel.org, chao@kernel.org, djwong@kernel.org,
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: [PATCH] erofs: confirm big pcluster before setting extents
Date: Sun, 15 Jun 2025 13:49:49 +0800 [thread overview]
Message-ID: <54e69067-1696-453a-b8a3-3a6967e03b24@linux.alibaba.com> (raw)
In-Reply-To: <tencent_15B5C44A7766B77466C6B36CE367297EA305@qq.com>
Hi Edward,
On 2025/6/15 13:05, Edward Adam Davis wrote:
> In this case, advise contains Z_EROFS_ADVISE_EXTENTS,
> Z_EROFS_ADVISE_BIG_PCLUSTER_1, Z_EROFS_ADVISE_BIG_PCLUSTER_2 at the same
> time, and following 1 and 2 are met, WARN_ON_ONCE(iter->iomap.offset >
> iter->pos) in iomap_iter_done() is triggered.
>
> 1. When Z_EROFS_ADVISE_EXTENTS exists, z_erofs_fill_inode_lazy() is exited
> after z_extents is set, which skips the check of big pcluster;
> 2. When the condition "lstart < lend" is met in z_erofs_map_blocks_ext(),
> m_la is updated, and m_la is used to update iomap->offset in
> z_erofs_iomap_begin_report();
>
> Fixes: 1d191b4ca51d ("erofs: implement encoded extent metadata")
> Reported-by: syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=d8f000c609f05f52d9b5
> Tested-by: syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
Z_EROFS_ADVISE_BIG_PCLUSTER_1 and Z_EROFS_ADVISE_BIG_PCLUSTER_2 are
valid only for !Z_EROFS_ADVISE_EXTENTS, so I don't think this change
is a proper solution.
From the commit message above, I don't get the root cause either.
Anyway, I will seek time to look into this issue later.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2025-06-15 5:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 23:30 [syzbot] [iomap?] [erofs?] WARNING in iomap_iter (5) syzbot
2025-06-14 3:06 ` Edward Adam Davis
2025-06-14 3:54 ` syzbot
2025-06-14 9:46 ` syzbot
2025-06-15 5:05 ` [PATCH] erofs: confirm big pcluster before setting extents Edward Adam Davis
2025-06-15 5:49 ` Gao Xiang [this message]
2025-06-19 3:53 ` [syzbot] [iomap?] [erofs?] WARNING in iomap_iter (5) Gao Xiang
2025-06-19 4:29 ` syzbot
2025-06-15 3:26 ` Edward Adam Davis
2025-06-15 4:02 ` syzbot
2025-06-15 3:56 ` Edward Adam Davis
2025-06-15 4:24 ` syzbot
2025-06-19 3:28 ` [PATCH] erofs: refuse crafted out-of-file-range encoded extents Gao Xiang
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=54e69067-1696-453a-b8a3-3a6967e03b24@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=eadavis@qq.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+d8f000c609f05f52d9b5@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®