From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Ahmet Eray Karadag <eraykrdg1@gmail.com>,
mark@fasheh.com, jlbec@evilplan.org,
akpm <akpm@linux-foundation.org>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
david.hunter.linux@gmail.com, skhan@linuxfoundation.org,
syzbot+b93b65ee321c97861072@syzkaller.appspotmail.com,
Heming Zhao <heming.zhao@suse.com>,
Albin Babu Varghese <albinbabuvarghese20@gmail.com>
Subject: Re: [PATCH] ocfs2: Mark inode bad upon validation failure during read
Date: Wed, 19 Nov 2025 14:21:03 +0800 [thread overview]
Message-ID: <58e5f4bb-0288-4d65-b38c-34dfe569098e@linux.alibaba.com> (raw)
In-Reply-To: <20251118001833.423470-2-eraykrdg1@gmail.com>
On 2025/11/18 08:18, Ahmet Eray Karadag wrote:
> A VFS cache inconsistency, potentially triggered by sequences like
> buffered writes followed by open(O_DIRECT), can result in an invalid
> on-disk inode block (e.g., bad signature). OCFS2 detects this corruption
> when reading the inode block via ocfs2_validate_inode_block(), logs
> "Invalid dinode", and often switches the filesystem to read-only mode.
>
> The VFS open(O_DIRECT) operation appears to incorrectly clear the inode's
> I_DIRTY flag without ensuring the dirty metadata (reflecting the earlier
> buffered write, e.g., an updated i_size) is flushed to disk. This leaves
> the in-memory VFS inode object "in limbo" with an updated size (e.g., 38639
> from the write) but marked clean, while its on-disk counterpart remains
> stale (e.g., size 0) or invalid.
>
> Currently, the function reading the inode block (ocfs2_read_inode_block_full())
> fails to call make_bad_inode() upon detecting the validation error.
> Because the in-memory inode is not marked bad, subsequent operations
> (like ftruncate) proceed erroneously. They eventually reach code
> (e.g., ocfs2_truncate_file()) that compares the inconsistent
> in-memory size (38639) against the invalid/stale on-disk size (0), leading
> to kernel crashes via BUG_ON.
>
> Fix this by calling make_bad_inode(inode) within the error handling path of
> ocfs2_read_inode_block_full() immediately after a block read or validation
> error occurs. This ensures VFS is properly notified about the
> corrupt inode at the point of detection. Marking the inode bad allows VFS
> to correctly fail subsequent operations targeting this inode early,
> preventing kernel panics caused by operating on known inconsistent inode states.
>
> Reported-by: syzbot+b93b65ee321c97861072@syzkaller.appspotmail.com
> Link: https://syzkaller.appspot.com/bug?extid=b93b65ee321c97861072
> Reviewed-by: Heming Zhao <heming.zhao@suse.com>
> Co-developed-by: Albin Babu Varghese <albinbabuvarghese20@gmail.com>
> Signed-off-by: Albin Babu Varghese <albinbabuvarghese20@gmail.com>
> Signed-off-by: Ahmet Eray Karadag <eraykrdg1@gmail.com>
> Previous-link: https://lore.kernel.org/all/20251029225748.11361-2-eraykrdg1@gmail.com/T/
Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/inode.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
> index fcc89856ab95..415ad29ec758 100644
> --- a/fs/ocfs2/inode.c
> +++ b/fs/ocfs2/inode.c
> @@ -1690,6 +1690,8 @@ int ocfs2_read_inode_block_full(struct inode *inode, struct buffer_head **bh,
> rc = ocfs2_read_blocks(INODE_CACHE(inode), OCFS2_I(inode)->ip_blkno,
> 1, &tmp, flags, ocfs2_validate_inode_block);
>
> + if (rc < 0)
> + make_bad_inode(inode);
> /* If ocfs2_read_blocks() got us a new bh, pass it up. */
> if (!rc && !*bh)
> *bh = tmp;
prev parent reply other threads:[~2025-11-19 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 0:18 Ahmet Eray Karadag
2025-11-19 6:21 ` Joseph Qi [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=58e5f4bb-0288-4d65-b38c-34dfe569098e@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=albinbabuvarghese20@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=eraykrdg1@gmail.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+b93b65ee321c97861072@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®