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
Date: Thu, 23 Dec 2021 10:41:50 -0500 [thread overview]
Message-ID: <YcSYvk5DdGjjB9q/@mit.edu> (raw)
In-Reply-To: <61C3D3CB.1010106@huawei.com>
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
next prev parent reply other threads:[~2021-12-23 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 12:32 [PATCH -next] ext4: Fix remount with 'abort' option isn't effective Ye Bin
2021-12-21 14:43 ` Lukas Czerner
2021-12-22 1:06 ` yebin
2021-12-22 9:19 ` Lukas Czerner
2021-12-23 1:41 ` yebin
2021-12-23 15:41 ` Theodore Ts'o [this message]
2022-02-01 13:13 ` [PATCH] ext4: fix remount with 'abort' option Lukas Czerner
2022-02-02 16:42 ` Gabriel Krisman Bertazi
2022-02-02 19:00 ` Eric Sandeen
2022-03-02 9:43 ` Lukas Czerner
2022-03-03 0:40 ` Theodore Ts'o
2022-03-03 0:41 ` Theodore Ts'o
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=YcSYvk5DdGjjB9q/@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yebin10@huawei.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 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.