From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, Baokun Li <libaokun1@huawei.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, enwlinux@gmail.com, jack@suse.cz,
lczerner@redhat.com, yukuai3@huawei.com, yi.zhang@huawei.com,
yebin10@huawei.com, ritesh.list@gmail.com,
adilger.kernel@dilger.ca
Subject: Re: [PATCH 0/2] ext4: fix a infinite loop in do_writepages after online resizing
Date: Tue, 29 Nov 2022 16:12:14 -0500 [thread overview]
Message-ID: <166975630697.2135297.7495422853696969304.b4-ty@mit.edu> (raw)
In-Reply-To: <20220817132701.3015912-1-libaokun1@huawei.com>
On Wed, 17 Aug 2022 21:26:59 +0800, Baokun Li wrote:
> We got a issue: the ext4 writeback process was stuck in do_writepages and
> do_writepages kept retrying. However, '-ENOMEM' is returned each time, even
> if there is still free memory on the current machine.
>
> We find that the direct cause of this issue is that the bg_inode_table_hi
> in the group descriptor is written to an incorrect value, which causes the
> inode block found through the inode table to exceed the end_ block。Then,
> sb_getblk always returns null, __ext4_get_inode_loc returns `-ENOMEM`,
> and do_writepages keeps retrying.
>
> [...]
Applied, thanks!
[1/2] ext4: fix GDT corruption after online resizing with bigalloc enable and blocksize is 1024
commit: 496fb12f8e236f303de6bc73a0334dd50c4eb64a
[2/2] ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite loop
commit: bfb0625e8e86f8797264b1c7d10e146afe243d23
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
next prev parent reply other threads:[~2022-11-29 21:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 13:26 [PATCH 0/2] ext4: fix a infinite loop in do_writepages after online resizing Baokun Li
2022-08-17 13:27 ` [PATCH 1/2] ext4: fix GDT corruption after online resizing with bigalloc enable and blocksize is 1024 Baokun Li
2022-08-17 13:27 ` [PATCH 2/2] ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite loop Baokun Li
2022-08-17 14:31 ` Jan Kara
2022-08-18 1:54 ` Baokun Li
2022-08-18 14:43 ` Ritesh Harjani (IBM)
2022-08-18 17:23 ` Jan Kara
2022-08-18 23:15 ` Ritesh Harjani (IBM)
2022-08-19 8:44 ` Jan Kara
2022-11-28 20:44 ` Theodore Ts'o
2022-11-29 8:54 ` Ritesh Harjani (IBM)
2022-11-29 21:12 ` Theodore Ts'o [this message]
2022-11-30 2:08 ` [PATCH 0/2] ext4: fix a infinite loop in do_writepages after online resizing Baokun Li
2022-12-01 3:42 ` Theodore Ts'o
2022-12-01 6:26 ` 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=166975630697.2135297.7495422853696969304.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=enwlinux@gmail.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=yebin10@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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 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.