From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Ahmet Eray Karadag <eraykrdg1@gmail.com>,
mark@fasheh.com, jlbec@evilplan.org
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
david.hunter.linux@gmail.com, skhan@linuxfoundation.org,
Heming Zhao <heming.zhao@suse.com>,
Albin Babu Varghese <albinbabuvarghese20@gmail.com>
Subject: Re: [PATCH v3 1/2] ocfs2: Add ocfs2_emergency_state helper and apply to setattr
Date: Tue, 2 Dec 2025 15:31:55 +0800 [thread overview]
Message-ID: <250d0d54-a6b0-42b2-a8d3-ebd806316a5c@linux.alibaba.com> (raw)
In-Reply-To: <8a26b007729e3f3f813f754eda6eed59431502e1.1764643790.git.eraykrdg1@gmail.com>
On 2025/12/2 10:54, Ahmet Eray Karadag wrote:
> To centralize error checking, follow the pattern of other filesystems
> like ext4 (which uses `ext4_emergency_state()`), and prepare for
> future enhancements, this patch introduces a new helper function:
> `ocfs2_emergency_state()`.
>
> The purpose of this helper is to provide a single, unified location
> for checking all filesystem-level emergency conditions. In this
> initial implementation, the function only checks for the existing
> hard and soft read-only modes, returning -EROFS if either is set.
>
> This provides a foundation where future checks (e.g., for fatal error
> states returning -EIO, or shutdown states) can be easily added in
> one place.
>
> This patch also adds this new check to the beginning of
> `ocfs2_setattr()`. This ensures that operations like `ftruncate`
> (which triggered the original BUG) fail-fast with -EROFS when the
> filesystem is already in a read-only state.
>
> Suggested-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>
> ---
> v2:
> - Introducing new function `ocfs2_is_readonly` to lower the cost
> - Using unlikely for status check
> ---
> v3:
> - Fix compilation error (missing semicolon).
> ---
> fs/ocfs2/file.c | 6 ++++++
> fs/ocfs2/ocfs2.h | 18 ++++++++++++++++++
> 2 files changed, 24 insertions(+)
>
> diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
> index 21d797ccccd0..253b4f300127 100644
> --- a/fs/ocfs2/file.c
> +++ b/fs/ocfs2/file.c
> @@ -1137,6 +1137,12 @@ int ocfs2_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> from_kgid(&init_user_ns, attr->ia_gid) : 0);
>
> /* ensuring we don't even attempt to truncate a symlink */
The above comments is for "if (S_ISLNK(inode->i_mode))".
So it should be move down just before symlink check.
> + status = ocfs2_emergency_state(osb);
> + if (unlikely(status)) {
> + mlog_errno(status);
> + goto bail;
> + }
> +
> if (S_ISLNK(inode->i_mode))
> attr->ia_valid &= ~ATTR_SIZE;
>
> diff --git a/fs/ocfs2/ocfs2.h b/fs/ocfs2/ocfs2.h
> index 6aaa94c554c1..91a861babf74 100644
> --- a/fs/ocfs2/ocfs2.h
> +++ b/fs/ocfs2/ocfs2.h
> @@ -680,6 +680,24 @@ static inline int ocfs2_is_soft_readonly(struct ocfs2_super *osb)
> return ret;
> }
>
> +static inline int ocfs2_is_readonly(struct ocfs2_super *osb)
> +{
> + int ret;
> + spin_lock(&osb->osb_lock);
> + ret = osb->osb_flags & (OCFS2_OSB_SOFT_RO | OCFS2_OSB_HARD_RO);
> + spin_unlock(&osb->osb_lock);
> +
> + return ret;
> +}
> +
> +static inline int ocfs2_emergency_state(struct ocfs2_super *osb)
> +{
> + if (ocfs2_is_readonly(osb)) {
The '{' can be eliminated.
Joseph
> + return -EROFS;
> + }
> + return 0;
> +}
> +
> static inline int ocfs2_clusterinfo_valid(struct ocfs2_super *osb)
> {
> return (osb->s_feature_incompat &
next prev parent reply other threads:[~2025-12-02 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 2:54 [PATCH v3 0/2] ocfs2: Refactor read-only checks to use ocfs2_emergency_state Ahmet Eray Karadag
2025-12-02 2:54 ` [PATCH v3 1/2] ocfs2: Add ocfs2_emergency_state helper and apply to setattr Ahmet Eray Karadag
2025-12-02 3:16 ` Heming Zhao
2025-12-02 7:31 ` Joseph Qi [this message]
2025-12-02 2:54 ` [PATCH v3 2/2] ocfs2: Convert remaining read-only checks to ocfs2_emergency_state Ahmet Eray Karadag
2025-12-02 3:16 ` Heming Zhao
2025-12-02 7:39 ` Joseph Qi
2025-12-03 0:46 ` Ahmet Eray Karadag
2025-12-03 1:00 ` 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=250d0d54-a6b0-42b2-a8d3-ebd806316a5c@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--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 \
/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®