From: "Lukáš Czerner" <lczerner@redhat.com>
To: Andrey Tsyvarev <tsyvarev@ispras.ru>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexey Khoroshilov <khoroshilov@ispras.ru>
Subject: Re: [PATCH] ext4: Do not destroy ext4_groupinfo_caches if ext4_mb_init() fails
Date: Mon, 12 May 2014 17:08:41 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1405121707120.8008@localhost.localdomain> (raw)
In-Reply-To: <1399883039-2978-1-git-send-email-tsyvarev@ispras.ru>
On Mon, 12 May 2014, Andrey Tsyvarev wrote:
> Date: Mon, 12 May 2014 12:23:59 +0400
> From: Andrey Tsyvarev <tsyvarev@ispras.ru>
> To: Theodore Ts'o <tytso@mit.edu>
> Cc: Andrey Tsyvarev <tsyvarev@ispras.ru>,
> Andreas Dilger <adilger.kernel@dilger.ca>, linux-ext4@vger.kernel.org,
> linux-kernel@vger.kernel.org, Alexey Khoroshilov <khoroshilov@ispras.ru>
> Subject: [PATCH] ext4: Do not destroy ext4_groupinfo_caches if ext4_mb_init()
> fails
>
> Caches from 'ext4_groupinfo_caches' may be in use by other mounts, which have already existed.
> So, it is incorrect to destroy them when newly requested mount fails.
>
> Found by Linux File System Verification project (linuxtesting.org).
Makes sense, thanks! Can you please share the test case which
triggered this ? It might be worth including in xfstests.
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
>
> Signed-off-by: Andrey Tsyvarev <tsyvarev@ispras.ru>
> ---
> fs/ext4/mballoc.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 04a5c75..becea1d 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -2607,7 +2607,7 @@ int ext4_mb_init(struct super_block *sb)
> sbi->s_locality_groups = alloc_percpu(struct ext4_locality_group);
> if (sbi->s_locality_groups == NULL) {
> ret = -ENOMEM;
> - goto out_free_groupinfo_slab;
> + goto out;
> }
> for_each_possible_cpu(i) {
> struct ext4_locality_group *lg;
> @@ -2632,8 +2632,6 @@ int ext4_mb_init(struct super_block *sb)
> out_free_locality_groups:
> free_percpu(sbi->s_locality_groups);
> sbi->s_locality_groups = NULL;
> -out_free_groupinfo_slab:
> - ext4_groupinfo_destroy_slabs();
> out:
> kfree(sbi->s_mb_offsets);
> sbi->s_mb_offsets = NULL;
>
next prev parent reply other threads:[~2014-05-12 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 8:23 [PATCH] ext4: Do not destroy ext4_groupinfo_caches if ext4_mb_init() fails Andrey Tsyvarev
2014-05-12 15:08 ` Lukáš Czerner [this message]
2014-05-12 16:49 ` Theodore Ts'o
2014-05-13 10:17 ` Andrey Tsyvarev
2014-05-13 10:25 ` Lukáš Czerner
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=alpine.LFD.2.00.1405121707120.8008@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=khoroshilov@ispras.ru \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tsyvarev@ispras.ru \
--cc=tytso@mit.edu \
/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