From: Baokun Li <libaokun1@huawei.com>
To: <linux-ext4@vger.kernel.org>
Cc: <tytso@mit.edu>, <adilger.kernel@dilger.ca>, <jack@suse.cz>,
<ritesh.list@gmail.com>, <linux-kernel@vger.kernel.org>,
<yi.zhang@huawei.com>, <yangerkun@huawei.com>,
<yukuai3@huawei.com>, Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH v3 0/2] ext4: fix quotas leak in __ext4_fill_super()
Date: Wed, 24 May 2023 14:18:40 +0800 [thread overview]
Message-ID: <0689edcf-8b7b-a86f-c672-3340c6e8e5e2@huawei.com> (raw)
In-Reply-To: <20230327141630.156875-1-libaokun1@huawei.com>
A gentle ping.
On 2023/3/27 22:16, Baokun Li wrote:
> V1->V2:
> Add judgment for CONFIG_QUOTA to avoid warning
> "label 'failed_mount9' defined but not used".
> (Reported-by: kernel test robot <lkp@intel.com>)
> V2->V3:
> By adding __maybe_unused to silence possible compilation
> complain in patch one, instead of adding the judgment.
> (Suggested by Jan Kara).
>
> Baokun Li (2):
> ext4: turning quotas off if mount failed after enable quotas
> ext4: refactoring to use the unified helper ext4_quotas_off()
>
> fs/ext4/super.c | 30 ++++++++++--------------------
> 1 file changed, 10 insertions(+), 20 deletions(-)
>
next prev parent reply other threads:[~2023-05-24 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:16 [PATCH v3 0/2] ext4: fix quotas leak in __ext4_fill_super() Baokun Li
2023-03-27 14:16 ` [PATCH v3 1/2] ext4: turning quotas off if mount failed after enable quotas Baokun Li
2023-03-28 9:15 ` Jan Kara
2023-03-27 14:16 ` [PATCH v3 2/2] ext4: refactoring to use the unified helper ext4_quotas_off() Baokun Li
2023-05-24 6:18 ` Baokun Li [this message]
2023-06-15 14:59 ` [PATCH v3 0/2] ext4: fix quotas leak in __ext4_fill_super() 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=0689edcf-8b7b-a86f-c672-3340c6e8e5e2@huawei.com \
--to=libaokun1@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox