[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7re2pyy6jcqhqxvsrye7osbsoepmoumzsrlty6kjsrv2iqjt55@b4llca3qxoml>
Date: Mon, 1 Dec 2025 10:17:00 +0800
From: Heming Zhao <heming.zhao@...e.com>
To: Ahmet Eray Karadag <eraykrdg1@...il.com>
Cc: mark@...heh.com, jlbec@...lplan.org, joseph.qi@...ux.alibaba.com,
ocfs2-devel@...ts.linux.dev, linux-kernel@...r.kernel.org, david.hunter.linux@...il.com,
skhan@...uxfoundation.org, syzbot+55c40ae8a0e5f3659f2b@...kaller.appspotmail.com,
Albin Babu Varghese <albinbabuvarghese20@...il.com>
Subject: Re: [PATCH v3] ocfs2: Invalidate inode if i_mode is zero after block
read
On Fri, Nov 28, 2025 at 05:36:06PM +0300, Ahmet Eray Karadag wrote:
> Hi all,
>
> Just a kind reminder regarding this patch.
>
> Since We are participating in the Linux Kernel Mentorship Program and have
> a nearing deadline, your feedback would be incredibly helpful for us to
> move forward.
>
> Thanks,
> Ahmet Eray
I have provided my comment on the v3 patch. The sanity check is expensive,
costing about six lines of asm code for ocfs2_read_links_count() on a big-endian
architecture.
Also, since I'm not the maintainer, if Joseph agrees with your patch, he can
provide his Reviewed-by tag.
PS: Kindly note that the kernel mailing list generally discourages separate
emails for patch review threads.
Powered by blists - more mailing lists