lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ee3df746-901c-40bd-95b5-2a2b7340395f@huawei.com>
Date: Wed, 19 Jun 2024 11:53:30 +0800
From: Baokun Li <libaokun1@...wei.com>
To: <mikael@...rfeldt.com>
CC: <linux-ext4@...r.kernel.org>, Baokun Li <libaokun1@...wei.com>,
	<yangerkun@...wei.com>
Subject: Re: Kernel bug at fs/ext4/resize.c:324! (6.8.12-amd64 on Debian)

On 2024/6/19 3:17, Mikael Djurfeldt wrote:
> Hi,
>
> While trying to do a resize2fs to fill up an extended volume, I got
> the dump attached to this message.
>
> Best regards,
> MIkael Djurfeldt

[416875.741485] kernel BUG at fs/ext4/resize.c:324!

BUG_ON((flexbg_size > 1) && ((src_group & ~(flexbg_size - 1)) !=
         (last_group & ~(flexbg_size - 1))));


The src_group and last_group are not in the same flex_bg triggering
this BUG_ON(). It looks like flex_gd->count or flex_gd->resize_bg are
outliers? Could you use `dumpe2fs -h /dev/yourdevice` to get the
details of the disk that was resized in order to further locate the issue?

Regards,
Baokun


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ