From: Guenter Roeck <linux@roeck-us.net>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
daniel.diaz@linaro.org, vmartensson@google.com
Subject: Re: [PATCH v2 2/5] ext4: Add unit test of ext4_mb_generate_buddy
Date: Wed, 20 Mar 2024 11:42:29 -0700 [thread overview]
Message-ID: <b814135f-83cb-4e8b-8b9e-c1be8a7ac597@roeck-us.net> (raw)
In-Reply-To: <30a8ce01-84d1-48ef-a93d-d14cc61723e3@roeck-us.net>
[ Adding more interested parties]
On Wed, Mar 20, 2024 at 09:23:24AM -0700, Guenter Roeck wrote:
> Hi,
>
> On Wed, Jan 03, 2024 at 06:48:57PM +0800, Kemeng Shi wrote:
> > Add unit test of ext4_mb_generate_buddy
> >
> > Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
>
> With this and other new ext4 tests test in the tree, I see a variety
> of backtraces in the upstream kernel if debug options are enabled.
> An example is
>
> [ 6.821447] KTAP version 1
> [ 6.821769] # Subtest: test_mb_generate_buddy
> [ 6.824787] =============================================================================
> [ 6.825568] BUG inode_cache (Tainted: G N): Padding overwritten. 0xfffff80006223f68-0xfffff80006223f6f @offset=16232
> ...
> [ 6.894341] ok 7 ext4_inode_test
> [ 6.895411] =============================================================================
> [ 6.895777] BUG inode_cache (Tainted: G B N): Padding overwritten. 0xfffff80006223f68-0xfffff80006223f6f @offset=16232
>
> Another example, from another test run, is
>
> [ 3.938551] # Subtest: test_new_blocks_simple
> [ 3.947171] ok 1 block_bits=10 cluster_bits=3 blocks_per_group=8192 group_count=4 desc_size=64
> [ 3.952988] ok 2 block_bits=12 cluster_bits=3 blocks_per_group=8192 group_count=4 desc_size=64
> [ 3.958403] ok 3 block_bits=16 cluster_bits=3 blocks_per_group=8192 group_count=4 desc_size=64
> [ 3.958890] =============================================================================
> [ 3.959159] BUG inode_cache (Tainted: G N): Padding overwritten. 0xffff8de881adbf68-0xffff8de881adbf6f @offset=16232
>
> Another one:
>
> [ 18.730473] # Subtest: test_new_blocks_simple
> [ 18.760547] ok 1 block_bits=10 cluster_bits=3 blocks_per_group=8192 group_count=4 desc_size=64
> [ 18.778477] ==================================================================
> [ 18.778950] BUG: KFENCE: out-of-bounds write in ext4_mb_init+0x5d7/0xa60
>
> This is just a sample, taken from a quick look at test results.
>
> Are those backtraces expected ? If so, would it be possible to execute the
> tests without generating such backtraces ? The backtraces, if intentional,
> hide real problems in the noise.
>
> Thanks,
> Guenter
next prev parent reply other threads:[~2024-03-20 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 10:48 [PATCH v2 0/5] More unit test for mballoc Kemeng Shi
2024-01-03 10:48 ` [PATCH v2 1/5] ext4: Add unit test for test_free_blocks_simple Kemeng Shi
2024-01-03 10:48 ` [PATCH v2 2/5] ext4: Add unit test of ext4_mb_generate_buddy Kemeng Shi
2024-03-20 16:23 ` Guenter Roeck
2024-03-20 18:42 ` Guenter Roeck [this message]
2024-03-21 7:16 ` Kemeng Shi
2024-03-22 9:27 ` Kemeng Shi
2024-03-22 14:49 ` Guenter Roeck
2024-03-26 13:09 ` Kemeng Shi
2024-01-03 10:48 ` [PATCH v2 3/5] ext4: Add unit test for mb_mark_used Kemeng Shi
2024-01-03 10:48 ` [PATCH v2 4/5] ext4: Add unit test for mb_free_blocks Kemeng Shi
2024-01-03 10:49 ` [PATCH v2 5/5] ext4: Add unit test for ext4_mb_mark_diskspace_used Kemeng Shi
2024-02-22 15:54 ` [PATCH v2 0/5] More unit test for mballoc Theodore Ts'o
2024-02-25 16:07 ` Guenter Roeck
2024-02-26 13:42 ` Kemeng Shi
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=b814135f-83cb-4e8b-8b9e-c1be8a7ac597@roeck-us.net \
--to=linux@roeck-us.net \
--cc=adilger.kernel@dilger.ca \
--cc=daniel.diaz@linaro.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shikemeng@huaweicloud.com \
--cc=tytso@mit.edu \
--cc=vmartensson@google.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®