Received-SPF: softfail (google.com: domain of transitioning linux-ext4-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     Lukas Czerner <lczerner@redhat.com>
Cc:     "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org,
        Ye Bin <yebin10@huawei.com>
Subject: Re: [PATCH] ext4: fix remount with 'abort' option
Date:   Wed,  2 Mar 2022 19:41:23 -0500
Message-Id: <164626805478.621144.15168980198456730624.b4-ty@mit.edu>
In-Reply-To: <20220201131345.77591-1-lczerner@redhat.com>
References: <YcSYvk5DdGjjB9q/@mit.edu> <20220201131345.77591-1-lczerner@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 1 Feb 2022 14:13:45 +0100, Lukas Czerner wrote:
> After commit 6e47a3cc68fc ("ext4: get rid of super block and sbi from
> handle_mount_ops()") the 'abort' options stopped working. This is
> because we're using ctx_set_mount_flags() helper that's expecting an
> argument with the appropriate bit set, but instead got
> EXT4_MF_FS_ABORTED which is a bit position. ext4_set_mount_flag() is
> using set_bit() while ctx_set_mount_flags() was using bitwise OR.
> 
> [...]

Applied, thanks!

[1/1] ext4: fix remount with 'abort' option
      commit: e3952fcce1aad934f1322843b564ff86256444b2

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>