From: Baokun Li <libaokun1@huawei.com>
To: Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: "Jan Kara" <jack@suse.cz>,
tytso@mit.edu, stable@vger.kernel.org,
"Andreas Dilger" <adilger.kernel@dilger.ca>,
"Stéphane Graber" <stgraber@stgraber.org>,
"Christian Brauner" <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
"Wesley Hershberger" <wesley.hershberger@canonical.com>,
"Yang Erkun" <yangerkun@huawei.com>
Subject: Re: [PATCH 1/1] ext4: fix crash on BUG_ON in ext4_alloc_group_tables
Date: Thu, 26 Sep 2024 17:28:11 +0800 [thread overview]
Message-ID: <52f055eb-a828-45cd-a06d-ca2006321926@huawei.com> (raw)
In-Reply-To: <CAEivzxc-b-QDx8AEdHEwa06Q2TYgZZkw2PWQ+K_Lyf+oyTM1Zg@mail.gmail.com>
On 2024/9/26 17:16, Aleksandr Mikhalitsyn wrote:
> On Thu, Sep 26, 2024 at 10:29 AM Baokun Li <libaokun1@huawei.com> wrote:
>> On 2024/9/25 23:57, Jan Kara wrote:
>>> On Wed 25-09-24 16:33:24, Alexander Mikhalitsyn wrote:
>>>> [ 33.882936] EXT4-fs (dm-5): mounted filesystem 8aaf41b2-6ac0-4fa8-b92b-77d10e1d16ca r/w with ordered data mode. Quota mode: none.
>>>> [ 33.888365] EXT4-fs (dm-5): resizing filesystem from 7168 to 786432 blocks
>>>> [ 33.888740] ------------[ cut here ]------------
>>>> [ 33.888742] kernel BUG at fs/ext4/resize.c:324!
>>> Ah, I was staring at this for a while before I understood what's going on
>>> (it would be great to explain this in the changelog BTW). As far as I
>>> understand commit 665d3e0af4d3 ("ext4: reduce unnecessary memory allocation
>>> in alloc_flex_gd()") can actually make flex_gd->resize_bg larger than
>>> flexbg_size (for example when ogroup = flexbg_size, ngroup = 2*flexbg_size
>>> - 1) which then confuses things. I think that was not really intended and
>>> instead of fixing up ext4_alloc_group_tables() we should really change
>>> the logic in alloc_flex_gd() to make sure flex_gd->resize_bg never exceeds
>>> flexbg size. Baokun?
>>>
>>> Honza
>> Hi Honza,
>>
>> Your analysis is absolutely correct. It's a bug!
>> Thank you for locating this issue!
>> An extra 1 should not be added when calculating resize_bg in
>> alloc_flex_gd().
>>
>>
>> Hi Aleksandr,
> Hi Baokun,
>
>> Could you help test if the following changes work?
> I can confirm that this patch helps.
>
> Tested-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
>
> Kind regards,
> Alex
Thank you for the test!
Cheers,
Baokun
>>
>> Thanks,
>> Baokun
>>
>> ---
>>
>> diff --git a/fs/ext4/resize.c b/fs/ext4/resize.c
>> index e04eb08b9060..1f01a7632149 100644
>> --- a/fs/ext4/resize.c
>> +++ b/fs/ext4/resize.c
>> @@ -253,10 +253,12 @@ static struct ext4_new_flex_group_data
>> *alloc_flex_gd(unsigned int flexbg_size,
>> /* Avoid allocating large 'groups' array if not needed */
>> last_group = o_group | (flex_gd->resize_bg - 1);
>> if (n_group <= last_group)
>> - flex_gd->resize_bg = 1 << fls(n_group - o_group + 1);
>> + flex_gd->resize_bg = 1 << fls(n_group - o_group);
>> else if (n_group - last_group < flex_gd->resize_bg)
>> - flex_gd->resize_bg = 1 << max(fls(last_group - o_group + 1),
>> + flex_gd->resize_bg = 1 << max(fls(last_group - o_group),
>> fls(n_group - last_group));
>>
>> flex_gd->groups = kmalloc_array(flex_gd->resize_bg,
>> sizeof(struct ext4_new_group_data),
>>
next prev parent reply other threads:[~2024-09-26 9:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 14:33 [PATCH 0/1] " Alexander Mikhalitsyn
2024-09-25 14:33 ` [PATCH 1/1] " Alexander Mikhalitsyn
2024-09-25 15:57 ` Jan Kara
2024-09-25 16:17 ` Aleksandr Mikhalitsyn
2024-09-26 8:50 ` Baokun Li
2024-09-26 9:23 ` Aleksandr Mikhalitsyn
2024-09-26 9:40 ` Baokun Li
2024-09-26 11:32 ` Aleksandr Mikhalitsyn
2024-09-26 13:58 ` Baokun Li
2024-09-26 14:19 ` Aleksandr Mikhalitsyn
2024-09-26 14:35 ` Baokun Li
2024-09-26 8:28 ` Baokun Li
2024-09-26 9:16 ` Aleksandr Mikhalitsyn
2024-09-26 9:28 ` Baokun Li [this message]
2024-09-26 16:04 ` Eric Sandeen
2024-09-26 16:29 ` Eric Sandeen
2024-09-27 1:51 ` Baokun Li
2024-09-27 2:39 ` Eric Sandeen
2024-09-27 1:43 ` Baokun Li
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=52f055eb-a828-45cd-a06d-ca2006321926@huawei.com \
--to=libaokun1@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stgraber@stgraber.org \
--cc=tytso@mit.edu \
--cc=wesley.hershberger@canonical.com \
--cc=yangerkun@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
all inboxes | Powered by JetHome®