From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: mcgrof@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, hare@suse.com,
p.raghav@samsung.com, da.gomez@samsung.com, djwong@kernel.org,
david@fromorbit.com, mcgrof@kernel.org, willy@infradead.org,
akpm@linux-foundation.org
Subject: Broken xarray testing in v6.9-rc1
Date: Tue, 23 Apr 2024 10:18:36 -0400 [thread overview]
Message-ID: <vm5b7c2jwmvptcnpgofwunjg4supq3snn63xqklidudnzlnhuv@kanproehzmdr> (raw)
Hello,
Testing of the xarray using the radix tree test suite is currently
broken in v6.9-rc1 and beyond. A bisect resulted in your commit failing
to build:
a60cc288a1a2604bd86d3df129f269887018c3cb is the first bad commit
commit a60cc288a1a2604bd86d3df129f269887018c3cb
Author: Luis Chamberlain <mcgrof@kernel.org>
...
Building in the test suite now fails in linux/tools/testing/radix-tree:
{bisect/bad(bisect)//radix-tree} $ make
cc -O2 -g -Wall -I. -I../../include -I../../../lib -g -Og -Wall -D_LGPL_SOURCE -fsanitize=address -fsanitize=undefined -c -o xarray.o xarray.c
In file included from xarray.c:18:
../../../lib/test_xarray.c: In function ‘test_get_entry’:
../../../lib/test_xarray.c:750:17: warning: implicit declaration of function ‘schedule’ [-Wimplicit-function-declaration]
750 | schedule();
| ^~~~~~~~
../../../lib/test_xarray.c: In function ‘check_xa_multi_store_adv’:
../../../lib/test_xarray.c:767:24: error: ‘PAGE_SHIFT’ undeclared (first use in this function)
767 | index = pos >> PAGE_SHIFT;
| ^~~~~~~~~~
../../../lib/test_xarray.c:767:24: note: each undeclared identifier is reported only once for each function it appears in
make: *** [<builtin>: xarray.o] Error 1
Can you please have a look?
Thanks,
Liam
next reply other threads:[~2024-04-23 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 14:18 Liam R. Howlett [this message]
2024-04-23 17:26 ` Luis Chamberlain
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=vm5b7c2jwmvptcnpgofwunjg4supq3snn63xqklidudnzlnhuv@kanproehzmdr \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=da.gomez@samsung.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hare@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=willy@infradead.org \
/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