linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Tsyvarev <tsyvarev@ispras.ru>
To: "Lukáš Czerner" <lczerner@redhat.com>
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: Tue, 13 May 2014 14:17:25 +0400	[thread overview]
Message-ID: <5371F135.7040409@ispras.ru> (raw)
In-Reply-To: <alpine.LFD.2.00.1405121707120.8008@localhost.localdomain>


12.05.2014 19:08, Lukáš Czerner пишет:
> 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.

Actually it was triggered by xfstests themselves but run with fault simulation.
The method of fault simulation is under development/evaluation now, we expect to publish a paper describing it in the near future.

BUG_ON() in get_groupinfo_cache() was firstly triggered by test generic/003, but actually it could be any other test, which uses a scratch device: xftests itself requires test device(TEST_DEV) mounted, so a fault simulated while mount scratch device causes the problem described.


> 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;
>>

--
Andrey Tsyvarev
Linux Verification Center, ISPRAS

  parent reply	other threads:[~2014-05-13 10:17 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
2014-05-12 16:49   ` Theodore Ts'o
2014-05-13 10:17   ` Andrey Tsyvarev [this message]
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=5371F135.7040409@ispras.ru \
    --to=tsyvarev@ispras.ru \
    --cc=adilger.kernel@dilger.ca \
    --cc=khoroshilov@ispras.ru \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).