All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Christian Brauner" <brauner@kernel.org>, "Jan Kara" <jack@suse.com>
Cc: "Al Viro" <viro@zeniv.linux.org.uk>,
	linux-ext4@vger.kernel.org, linux-mm@kvack.org,
	linux-efi@vger.kernel.org, linux-mtd@lists.infradead.org,
	dsterba@suse.cz, tytso@mit.edu, "Mark Fasheh" <mark@fasheh.com>,
	"Joel Becker" <jlbec@evilplan.org>,
	"Joseph Qi" <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH v3 17/33] ufs: don't set SB_RDONLY after filesystem errors
Date: Sat, 14 Nov 2026 12:03:35 +0000	[thread overview]
Message-ID: <sashiko-outbox-214468@kernel.org> (raw)
In-Reply-To: <20261113-work-fs-sb_rdonly-v3-17-0be92bb73709@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] ufs: cylinder group leak and SB_RDONLY clear in
  ufs_reconfigure()
--

commit eaf412f5390fa6f1c30001040b118660141a9bd6
Author: Christian Brauner <brauner@kernel.org>

ufs: don't set SB_RDONLY after filesystem errors

This commit switches ufs_error() and ufs_panic() from setting SB_RDONLY to
calling sb_set_emergency_ro(), and keeps cylinder group structures allocated
across read-only remounts after an error so inode eviction can still use
them.

> diff --git a/fs/ufs/super.c b/fs/ufs/super.c
> index 3569ac92b065b..d82cf73360a79 100644
> --- a/fs/ufs/super.c
> +++ b/fs/ufs/super.c

[ ... ]

> @@ -1265,14 +1281,20 @@ static int ufs_reconfigure(struct fs_context *fc)
>  	 * fs was mouted as rw, remounting ro
>  	 */
>  	if (fc->sb_flags & SB_RDONLY) {
> -		ufs_put_super_internal(sb);
> -		usb1->fs_time = ufs_get_seconds(sb);
> -		if ((flags & UFS_ST_MASK) == UFS_ST_SUN
> -		  || (flags & UFS_ST_MASK) == UFS_ST_SUNOS
> -		  || (flags & UFS_ST_MASK) == UFS_ST_SUNx86) 
> -			ufs_set_fs_state(sb, usb1, usb3,
> -				UFS_FSOK - fs32_to_cpu(sb, usb1->fs_time));
> -		ubh_mark_buffer_dirty (USPI_UBH(uspi));
> +		/*
> +		 * After an error leave the superblock alone and keep the
> +		 * cylinder groups, evict still needs them.
> +		 */
> +		if (!sb_emergency_ro(sb)) {
> +			ufs_put_super_internal(sb);
> +			usb1->fs_time = ufs_get_seconds(sb);
> +			if ((flags & UFS_ST_MASK) == UFS_ST_SUN
> +			  || (flags & UFS_ST_MASK) == UFS_ST_SUNOS
> +			  || (flags & UFS_ST_MASK) == UFS_ST_SUNx86)
> +				ufs_set_fs_state(sb, usb1, usb3,
> +					UFS_FSOK - fs32_to_cpu(sb, usb1->fs_time));
> +			ubh_mark_buffer_dirty (USPI_UBH(uspi));
> +		}
>  		sb->s_flags |= SB_RDONLY;
>  	} else {
>  	/*

[Severity: Medium]
Can reconfiguring via fspick() after an error and a read-only remount
leak the retained cylinder group structures and clear SB_RDONLY?

When a read-write mount hits an error and is then remounted read-only,
this branch skips ufs_put_super_internal() so sbi->s_csp, sbi->s_ucg, and
sbi->s_ucpi stay allocated while SB_RDONLY is set on sb->s_flags.

If userspace then reconfigures the mount via fspick() and fsconfig()
without specifying ro or rw (for example, changing onerror=), fc->sb_flags
and fc->sb_flags_mask are both 0.  reconfigure_super() only rejects
sb_emergency_ro(sb) when SB_RDONLY is in fc->sb_flags_mask, and
ufs_reconfigure() checks (bool)(fc->sb_flags & SB_RDONLY) == sb_rdonly(sb)
without consulting fc->sb_flags_mask.  Execution then falls into the else
branch, where ufs_read_cylinder_structures() overwrites the existing
sbi->s_csp, sbi->s_ucg, and sbi->s_ucpi pointers (leaking memory and
buffer_heads) and clears SB_RDONLY from sb->s_flags.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-work-fs-sb_rdonly-v3-0-0be92bb73709@kernel.org?part=17

WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Christian Brauner" <brauner@kernel.org>, "Jan Kara" <jack@suse.com>
Cc: "Al Viro" <viro@zeniv.linux.org.uk>,
	linux-ext4@vger.kernel.org, linux-mm@kvack.org,
	linux-efi@vger.kernel.org, linux-mtd@lists.infradead.org,
	dsterba@suse.cz, tytso@mit.edu, "Mark Fasheh" <mark@fasheh.com>,
	"Joel Becker" <jlbec@evilplan.org>,
	"Joseph Qi" <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH v3 17/33] ufs: don't set SB_RDONLY after filesystem errors
Date: Sat, 14 Nov 2026 12:03:35 +0000	[thread overview]
Message-ID: <sashiko-outbox-214468@kernel.org> (raw)
In-Reply-To: <20261113-work-fs-sb_rdonly-v3-17-0be92bb73709@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] ufs: cylinder group leak and SB_RDONLY clear in
  ufs_reconfigure()
--

commit eaf412f5390fa6f1c30001040b118660141a9bd6
Author: Christian Brauner <brauner@kernel.org>

ufs: don't set SB_RDONLY after filesystem errors

This commit switches ufs_error() and ufs_panic() from setting SB_RDONLY to
calling sb_set_emergency_ro(), and keeps cylinder group structures allocated
across read-only remounts after an error so inode eviction can still use
them.

> diff --git a/fs/ufs/super.c b/fs/ufs/super.c
> index 3569ac92b065b..d82cf73360a79 100644
> --- a/fs/ufs/super.c
> +++ b/fs/ufs/super.c

[ ... ]

> @@ -1265,14 +1281,20 @@ static int ufs_reconfigure(struct fs_context *fc)
>  	 * fs was mouted as rw, remounting ro
>  	 */
>  	if (fc->sb_flags & SB_RDONLY) {
> -		ufs_put_super_internal(sb);
> -		usb1->fs_time = ufs_get_seconds(sb);
> -		if ((flags & UFS_ST_MASK) == UFS_ST_SUN
> -		  || (flags & UFS_ST_MASK) == UFS_ST_SUNOS
> -		  || (flags & UFS_ST_MASK) == UFS_ST_SUNx86) 
> -			ufs_set_fs_state(sb, usb1, usb3,
> -				UFS_FSOK - fs32_to_cpu(sb, usb1->fs_time));
> -		ubh_mark_buffer_dirty (USPI_UBH(uspi));
> +		/*
> +		 * After an error leave the superblock alone and keep the
> +		 * cylinder groups, evict still needs them.
> +		 */
> +		if (!sb_emergency_ro(sb)) {
> +			ufs_put_super_internal(sb);
> +			usb1->fs_time = ufs_get_seconds(sb);
> +			if ((flags & UFS_ST_MASK) == UFS_ST_SUN
> +			  || (flags & UFS_ST_MASK) == UFS_ST_SUNOS
> +			  || (flags & UFS_ST_MASK) == UFS_ST_SUNx86)
> +				ufs_set_fs_state(sb, usb1, usb3,
> +					UFS_FSOK - fs32_to_cpu(sb, usb1->fs_time));
> +			ubh_mark_buffer_dirty (USPI_UBH(uspi));
> +		}
>  		sb->s_flags |= SB_RDONLY;
>  	} else {
>  	/*

[Severity: Medium]
Can reconfiguring via fspick() after an error and a read-only remount
leak the retained cylinder group structures and clear SB_RDONLY?

When a read-write mount hits an error and is then remounted read-only,
this branch skips ufs_put_super_internal() so sbi->s_csp, sbi->s_ucg, and
sbi->s_ucpi stay allocated while SB_RDONLY is set on sb->s_flags.

If userspace then reconfigures the mount via fspick() and fsconfig()
without specifying ro or rw (for example, changing onerror=), fc->sb_flags
and fc->sb_flags_mask are both 0.  reconfigure_super() only rejects
sb_emergency_ro(sb) when SB_RDONLY is in fc->sb_flags_mask, and
ufs_reconfigure() checks (bool)(fc->sb_flags & SB_RDONLY) == sb_rdonly(sb)
without consulting fc->sb_flags_mask.  Execution then falls into the else
branch, where ufs_read_cylinder_structures() overwrites the existing
sbi->s_csp, sbi->s_ucg, and sbi->s_ucpi pointers (leaking memory and
buffer_heads) and clears SB_RDONLY from sb->s_flags.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-work-fs-sb_rdonly-v3-0-0be92bb73709@kernel.org?part=17

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2026-11-14 12:03 UTC|newest]

Thread overview: 118+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 11:58 [PATCH v3 00/33] fs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:58 ` Christian Brauner
2026-11-13 11:58 ` [PATCH v3 01/33] jfs: free uncommitted anonymous tlocks when evicting an inode Christian Brauner
2026-11-13 11:58   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:58 ` [PATCH v3 02/33] jfs: use jfs_symlink_inode_operations in jfs_iget() Christian Brauner
2026-11-13 11:58   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:58 ` [PATCH v3 03/33] ecryptfs: don't leak the inode when a lookup can't open the lower file Christian Brauner
2026-11-13 11:58   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 04/33] ecryptfs: fall back to a read-only " Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 05/33] fs: add a generic emergency read-only state Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-13 14:53   ` Jan Kara
2026-11-13 14:53     ` Jan Kara
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 06/33] ext2: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-13 14:54   ` Jan Kara
2026-11-13 14:54     ` Jan Kara
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 07/33] jfs: " Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 08/33] nilfs2: " Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 09/33] fat: " Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 10/33] exfat: keep the current mount options on remount Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 11/33] exfat: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 12/33] exfat: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 13/33] hfs: don't set SB_RDONLY after MDB write errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 14/33] hfs: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 15/33] hfsplus: don't set SB_RDONLY when creating the attributes tree Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 16/33] affs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 17/33] ufs: " Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot [this message]
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 18/33] hpfs: " Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 19/33] ntfs: " Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 20/33] ntfs: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 21/33] ocfs2: keep the current mount options on remount Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 22/33] ocfs2: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 23/33] zonefs: don't set SB_RDONLY after I/O errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 24/33] zonefs: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 25/33] btrfs: check BTRFS_FS_STATE_RO instead of SB_RDONLY at runtime Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 26/33] btrfs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 27/33] gfs2: wait for a pending withdraw before remounting read-only Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 28/33] gfs2: don't set SB_RDONLY on withdraw Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 29/33] efivarfs: stop using SB_RDONLY for read-only efivar ops Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 30/33] ubifs: don't set SB_RDONLY after errors Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14  2:17   ` Zhihao Cheng
2026-11-14  2:17     ` Zhihao Cheng
2026-11-14 12:03   ` sashiko-bot
2026-11-14 12:03     ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 31/33] ext4: allow remounting read-only in the emergency state Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 32/33] ext4: use the generic emergency read-only state Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot
2026-11-13 11:59 ` [PATCH v3 33/33] xfs: allow remounting read-only after a shutdown Christian Brauner
2026-11-13 11:59   ` Christian Brauner
2026-11-14 12:03   ` sashiko-bot

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=sashiko-outbox-214468@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=brauner@kernel.org \
    --cc=dsterba@suse.cz \
    --cc=jack@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mark@fasheh.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.