From: Deepanshu Kartikey <kartikey406@gmail.com>
To: heming.zhao@suse.com, joseph.qi@linux.alibaba.com,
mark@fasheh.com, jlbec@evilplan.org
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
syzbot+6fdd8fa3380730a4b22c@syzkaller.appspotmail.com
Subject: Re: [PATCH] ocfs2: fix stale extent map cache during COW operations
Date: Sat, 11 Oct 2025 14:02:44 +0530 [thread overview]
Message-ID: <20251011083244.822985-1-kartikey406@gmail.com> (raw)
Hi Heming,
Thank you for the detailed analysis and feedback.
After further investigation, I discovered that the ioctl call in the reproducer
(0x40406f06) is NOT FITRIM as the syzbot comment suggested. Decoding the ioctl
number shows:
- Type: 'o' (0x6f)
- Number: 6
- This is OCFS2_IOC_MOVE_EXT (defined in fs/ocfs2/ocfs2_ioctl.h:222)
So the actual call path in the reproducer is:
1. copy_file_range() - creates reflinked extent with flags=0x2
2. ioctl(OCFS2_IOC_MOVE_EXT) - calls ocfs2_move_extents() ->
__ocfs2_move_extents_range()
3. write() - triggers BUG_ON
Inside __ocfs2_move_extents_range(), the while loop:
- Calls ocfs2_get_clusters() which caches the extent with flags=0x2
- Then calls ocfs2_move_extent() -> __ocfs2_move_extent()
- __ocfs2_move_extent() at line 50 clears the refcount flag on disk:
replace_rec.e_flags = ext_flags & ~OCFS2_EXT_REFCOUNTED;
- But the extent cache is not invalidated
This is exactly what my v2 patch fixes by adding ocfs2_extent_map_trunc()
after the move operation completes.
Thanks for your time!
Best regards,
Deepanshu
next reply other threads:[~2025-10-11 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 8:32 Deepanshu Kartikey [this message]
2025-10-11 12:27 ` Heming Zhao
-- strict thread matches above, loose matches on Subject: below --
2025-10-11 7:42 Deepanshu Kartikey
2025-10-09 14:29 Deepanshu Kartikey
2025-10-11 4:50 ` Heming Zhao
2025-10-08 4:23 Deepanshu Kartikey
2025-10-09 9:14 ` Joseph Qi
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=20251011083244.822985-1-kartikey406@gmail.com \
--to=kartikey406@gmail.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+6fdd8fa3380730a4b22c@syzkaller.appspotmail.com \
/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®