Date:   Thu, 23 Dec 2021 10:41:50 -0500
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     yebin <yebin10@huawei.com>
Cc:     Lukas Czerner <lczerner@redhat.com>, adilger.kernel@dilger.ca,
        linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
        jack@suse.cz
Subject: Re: [PATCH -next] ext4: Fix remount with 'abort' option isn't
 effective
Message-ID: <YcSYvk5DdGjjB9q/@mit.edu>
References: <20211221123214.2410593-1-yebin10@huawei.com>
 <20211221144305.nlryh7q2cgdbpmi5@work>
 <61C27A0E.9050900@huawei.com>
 <20211222091947.chmg6mcetocrmygd@work>
 <61C3D3CB.1010106@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <61C3D3CB.1010106@huawei.com>
Precedence: bulk

On Thu, Dec 23, 2021 at 09:41:31AM +0800, yebin wrote:
> 
> On 2021/12/22 17:19, Lukas Czerner wrote:
> > On Wed, Dec 22, 2021 at 09:06:22AM +0800, yebin wrote:
> > > 
> > > On 2021/12/21 22:43, Lukas Czerner wrote:
> > > > Hi,
> > > > 
> > > > nice catch. This is a bug indeed. However I am currently in a process of
> > > > changing the ctx_set/clear/test_ helpers because currently it generates
> > > > functions that are unused.
> > > > 
> > > > While I am at it I can just create a custom ctx_set_mount_flags()
> > > > helper that would behave as expected so that we won't have to specify
> > > > "1 < EXT4_MF_FS_ABORTED" which is not really obvious and hence error
> > > > prone.
> > > Actually, I fixed the first version as follows:
> > Allright, this looks better.

Was there an update to this patch?  I can't seem to find it in my
inbox or in patchwork....

Thanks,

					- Ted