From: Zhang Yi <yi.zhang@huaweicloud.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
achill@achill.org, qemu-devel@nongnu.org,
"Alex Bennée" <alex.bennee@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Ben Copeland" <benjamin.copeland@linaro.org>,
"LTP List" <ltp@lists.linux.it>, chrubis <chrubis@suse.cz>,
"Petr Vorel" <pvorel@suse.cz>, "Ian Rogers" <irogers@google.com>,
linux-perf-users@vger.kernel.org,
"Joseph Qi" <jiangqi903@gmail.com>, "Jan Kara" <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Zhang Yi" <yi.zhang@huawei.com>, "Theodore Ts'o" <tytso@mit.edu>,
"Baokun Li" <libaokun1@huawei.com>
Subject: Re: [PATCH 6.16 000/627] 6.16.1-rc1 review
Date: Thu, 14 Aug 2025 09:27:49 +0800 [thread overview]
Message-ID: <42aace87-1b89-4b17-96f1-3efbabc4acf3@huaweicloud.com> (raw)
In-Reply-To: <2025081311-purifier-reviver-aeb2@gregkh>
On 2025/8/13 22:53, Greg Kroah-Hartman wrote:
> On Wed, Aug 13, 2025 at 08:01:51PM +0530, Naresh Kamboju wrote:
>> Hi Greg,
>>
>>>> 2)
>>>>
>>>> The following list of LTP syscalls failure noticed on qemu-arm64 with
>>>> stable-rc 6.16.1-rc1 with CONFIG_ARM64_64K_PAGES=y build configuration.
>>>>
>>>> Most failures report ENOSPC (28) or mkswap errors, which may be related
>>>> to disk space handling in the 64K page configuration on qemu-arm64.
>>>>
>>>> The issue is reproducible on multiple runs.
>>>>
>>>> * qemu-arm64, ltp-syscalls - 64K page size test failures list,
>>>>
>>>> - fallocate04
>>>> - fallocate05
>>>> - fdatasync03
>>>> - fsync01
>>>> - fsync04
>>>> - ioctl_fiemap01
>>>> - swapoff01
>>>> - swapoff02
>>>> - swapon01
>>>> - swapon02
>>>> - swapon03
>>>> - sync01
>>>> - sync_file_range02
>>>> - syncfs01
>>>>
>>>> Reproducibility:
>>>> - 64K config above listed test fails
>>>> - 4K config above listed test pass.
>>>>
>>>> Regression Analysis:
>>>> - New regression? yes
>>>
>>> Regression from 6.16? Or just from 6.15.y?
>>
>> Based on available data, the issue is not present in v6.16 or v6.15.
>>
>> Anders, bisected this regression and found,
>>
>> ext4: correct the reserved credits for extent conversion
>> [ Upstream commit 95ad8ee45cdbc321c135a2db895d48b374ef0f87 ]
>>
>> Report lore link,
>>
>> https://lore.kernel.org/stable/CA+G9fYtBnCSa2zkaCn-oZKYz8jz5FZj0HS7DjSfMeamq3AXqNg@mail.gmail.com/
>
> Great, and that's also affecting 6.17-rc1 so we are "bug compatible"?
> :)
>
Hi,
This issue has already fixed in 6.17-rc1 through this series:
https://lore.kernel.org/linux-ext4/20250707140814.542883-1-yi.zhang@huaweicloud.com/
To fix this issue in 6.16, it's necessary to backport the whole series
instead of just pick 5137d6c8906b ("ext4: fix insufficient credits
calculation in ext4_meta_trans_blocks()") and 95ad8ee45cdb {"ext4: correct
the reserved credits for extent conversion"). Otherwise, this will make
the problem more likely to occur.
Thanks,
Yi.
next prev parent reply other threads:[~2025-08-14 1:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250812173419.303046420@linuxfoundation.org>
2025-08-13 12:16 ` [PATCH 6.16 000/627] 6.16.1-rc1 review Naresh Kamboju
2025-08-13 12:50 ` Greg Kroah-Hartman
2025-08-13 14:31 ` Naresh Kamboju
2025-08-13 14:53 ` Greg Kroah-Hartman
2025-08-13 15:58 ` Dan Carpenter
2025-08-14 1:27 ` Zhang Yi [this message]
2025-08-14 15:30 ` Greg Kroah-Hartman
2025-08-14 20:19 ` Namhyung Kim
2025-08-15 5:33 ` Greg Kroah-Hartman
2025-08-15 16:24 ` Namhyung Kim
2025-08-13 12:51 ` Mark Brown
2025-08-13 13:41 ` Naresh Kamboju
2025-08-14 15:35 ` Greg Kroah-Hartman
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=42aace87-1b89-4b17-96f1-3efbabc4acf3@huaweicloud.com \
--to=yi.zhang@huaweicloud.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=broonie@kernel.org \
--cc=chrubis@suse.cz \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=irogers@google.com \
--cc=jack@suse.cz \
--cc=jiangqi903@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=pvorel@suse.cz \
--cc=qemu-devel@nongnu.org \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@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;
as well as URLs for NNTP newsgroup(s).