From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
linux-ext4 <linux-ext4@vger.kernel.org>,
LTP List <ltp@lists.linux.it>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>
Subject: Re: next: kernel BUG at fs/ext4/mballoc.c:4369!
Date: Tue, 18 Jul 2023 07:27:16 +0530 [thread overview]
Message-ID: <87h6q2nfr7.fsf@doe.com> (raw)
In-Reply-To: <20230717213424.GB3842864@mit.edu>
"Theodore Ts'o" <tytso@mit.edu> writes:
> On Mon, Jul 17, 2023 at 08:04:54PM +0530, Ritesh Harjani wrote:
>>
>> These can basically trigger in extremely low memory space and only when
>> such ranges exist in the PA rbtree. Hence, I guess it is a little hard
>> to tigger race.
>
> Ritesh, thanks for looking into this!
>
> Naresh, how easy is it for you to trigger the BUG when using LTP? I
> did two xfstests runs using "gce-xfstests -c ext2/default -g auto",
> one on the ext4 dev branch, and one on linux-next 20230717, and I
> wasn't able to trigger the BUG.
>
> If you can trivially trigger it using LTP (perhaps with a low memory
> configuration in your test setup?), that would be useful to know.
Hi Ted,
Sorry for wrong choice of words. By low memory space I meant low disk
space i.e. ENOSPC test (fs_fill). I reproduced it like this -
root@ubuntu:/opt/ltp# while [ 1 ]; do ./runltp -s fs_fill; sleep 1; done
For me it took around ~1-2 hours for it to reproduce when I tried again.
I am hoping if we run generic/269 (fsstress ENOSPC) in a while loop like
this maybe it can hit this bug. But I didn't give it a shot.
-ritesh
WARNING: multiple messages have this Message-ID (diff)
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Arnd Bergmann <arnd@arndb.de>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, linux-mm <linux-mm@kvack.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Dan Carpenter <dan.carpenter@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
LTP List <ltp@lists.linux.it>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>
Subject: Re: [LTP] next: kernel BUG at fs/ext4/mballoc.c:4369!
Date: Tue, 18 Jul 2023 07:27:16 +0530 [thread overview]
Message-ID: <87h6q2nfr7.fsf@doe.com> (raw)
In-Reply-To: <20230717213424.GB3842864@mit.edu>
"Theodore Ts'o" <tytso@mit.edu> writes:
> On Mon, Jul 17, 2023 at 08:04:54PM +0530, Ritesh Harjani wrote:
>>
>> These can basically trigger in extremely low memory space and only when
>> such ranges exist in the PA rbtree. Hence, I guess it is a little hard
>> to tigger race.
>
> Ritesh, thanks for looking into this!
>
> Naresh, how easy is it for you to trigger the BUG when using LTP? I
> did two xfstests runs using "gce-xfstests -c ext2/default -g auto",
> one on the ext4 dev branch, and one on linux-next 20230717, and I
> wasn't able to trigger the BUG.
>
> If you can trivially trigger it using LTP (perhaps with a low memory
> configuration in your test setup?), that would be useful to know.
Hi Ted,
Sorry for wrong choice of words. By low memory space I meant low disk
space i.e. ENOSPC test (fs_fill). I reproduced it like this -
root@ubuntu:/opt/ltp# while [ 1 ]; do ./runltp -s fs_fill; sleep 1; done
For me it took around ~1-2 hours for it to reproduce when I tried again.
I am hoping if we run generic/269 (fsstress ENOSPC) in a while loop like
this maybe it can hit this bug. But I didn't give it a shot.
-ritesh
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-07-18 1:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 6:02 next: kernel BUG at fs/ext4/mballoc.c:4369! Naresh Kamboju
2023-07-16 6:02 ` [LTP] " Naresh Kamboju
2023-07-17 4:31 ` Theodore Ts'o
2023-07-17 4:31 ` [LTP] " Theodore Ts'o
2023-07-17 5:06 ` Naresh Kamboju
2023-07-17 5:06 ` [LTP] " Naresh Kamboju
2023-07-17 5:43 ` Ritesh Harjani
2023-07-17 5:43 ` [LTP] " Ritesh Harjani
2023-07-17 7:12 ` Ojaswin Mujoo
2023-07-17 7:12 ` [LTP] " Ojaswin Mujoo
2023-07-17 7:43 ` Ritesh Harjani
2023-07-17 7:43 ` Ritesh Harjani
2023-07-17 14:34 ` Ritesh Harjani
2023-07-17 14:34 ` [LTP] " Ritesh Harjani
2023-07-17 21:34 ` Theodore Ts'o
2023-07-17 21:34 ` [LTP] " Theodore Ts'o
2023-07-18 1:57 ` Ritesh Harjani [this message]
2023-07-18 1:57 ` Ritesh Harjani
2023-07-18 9:10 ` Petr Vorel
2023-07-18 9:10 ` Petr Vorel
2023-07-18 11:47 ` Naresh Kamboju
2023-07-18 11:47 ` [LTP] " Naresh Kamboju
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=87h6q2nfr7.fsf@doe.com \
--to=ritesh.list@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=ojaswin@linux.ibm.com \
--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 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.