From: Kees Cook <kees@kernel.org>
To: David Gow <davidgow@google.com>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
Gabriel Krisman Bertazi <gabriel@krisman.be>,
Pedro Orlando <porlando@lkcamp.dev>,
Danilo Pereira <dpereira@lkcamp.dev>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com,
Gabriela Bittencourt <gbittencourt@lkcamp.dev>,
Linux kernel regressions list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] unicode: kunit: change tests filename and path
Date: Wed, 12 Feb 2025 14:09:55 -0800 [thread overview]
Message-ID: <202502121409.864E362899@keescook> (raw)
In-Reply-To: <CABVgOS=36iRrpb+ND4M2awbZzgCKwudYxx5XNvEBEkgss+C-bw@mail.gmail.com>
On Wed, Feb 12, 2025 at 05:31:59PM +0800, David Gow wrote:
> On Wed, 12 Feb 2025 at 14:45, Thorsten Leemhuis <linux@leemhuis.info> wrote:
> >
> > On 04.10.24 21:00, Gabriel Krisman Bertazi wrote:
> > > Pedro Orlando <porlando@lkcamp.dev> writes:
> > >> From: Gabriela Bittencourt <gbittencourt@lkcamp.dev>
> > >>
> > >> Change utf8 kunit test filename and path to follow the style
> > >> convention on Documentation/dev-tools/kunit/style.rst
> > >>
> > >> Co-developed-by: Pedro Orlando <porlando@lkcamp.dev>
> > >> Signed-off-by: Pedro Orlando <porlando@lkcamp.dev>
> > >> Co-developed-by: Danilo Pereira <dpereira@lkcamp.dev>
> > >> Signed-off-by: Danilo Pereira <dpereira@lkcamp.dev>
> > >> Signed-off-by: Gabriela Bittencourt <gbittencourt@lkcamp.dev>
> > >> ---
> > >> fs/unicode/Makefile | 2 +-
> > >> fs/unicode/{ => tests}/.kunitconfig | 0
> > >> fs/unicode/{utf8-selftest.c => tests/utf8_kunit.c} | 0
> > >> 3 files changed, 1 insertion(+), 1 deletion(-)
> > >> rename fs/unicode/{ => tests}/.kunitconfig (100%)
> > >> rename fs/unicode/{utf8-selftest.c => tests/utf8_kunit.c} (100%)
> > >>
> > >> diff --git a/fs/unicode/Makefile b/fs/unicode/Makefile
> > >> index 37bbcbc628a1..d95be7fb9f6b 100644
> > >> --- a/fs/unicode/Makefile
> > >> +++ b/fs/unicode/Makefile
> > >> @@ -4,7 +4,7 @@ ifneq ($(CONFIG_UNICODE),)
> > >> obj-y += unicode.o
> > >> endif
> > >> obj-$(CONFIG_UNICODE) += utf8data.o
> > >> -obj-$(CONFIG_UNICODE_NORMALIZATION_KUNIT_TEST) += utf8-selftest.o
> > >> +obj-$(CONFIG_UNICODE_NORMALIZATION_KUNIT_TEST) += tests/utf8_kunit.o
> > >
> > > This breaks compilation for me.
> > >
> > > fs/unicode/tests/utf8_kunit.c:11:10: fatal error: utf8n.h: No such file or directory
> > > 11 | #include "utf8n.h"
> > > | ^~~~~~~~~
> >
> > I encountered the same error when building -next using the Fedora
> > rawhide config today. Given that this patch landed in -next today I
> > suspect it might be due to this change, but I'm on the road and unable
> > to verify that right now.
> >
> > Log:
> > https://download.copr.fedorainfracloud.org/results/@kernel-vanilla/next/fedora-rawhide-x86_64/08642966-next-next-all/builder-live.log.gz
> >
> > Cioa, Thorsten
> >
>
> Hmm... this definitely seems like a problem, but I haven't been able
> to reproduce it here (either under x86_64 or UML, both as a module and
> built-in). The suggested fix of changing the path to "../utf8n.h"
> doesn't seem to have broken it, though.
Thanks for the reports! I've squashed this path correction into my tree
and it should be fix in the next -next. :)
-Kees
--
Kees Cook
next prev parent reply other threads:[~2025-02-12 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 23:58 [PATCH v2 0/2] unicode: kunit: refactor selftest to kunit tests Pedro Orlando
2024-09-28 23:58 ` [PATCH v2 1/2] " Pedro Orlando
2024-10-03 6:53 ` David Gow
2024-10-04 19:02 ` Gabriel Krisman Bertazi
2024-09-28 23:58 ` [PATCH v2 2/2] unicode: kunit: change tests filename and path Pedro Orlando
2024-10-02 13:08 ` André Almeida
2024-10-03 6:54 ` David Gow
2024-10-04 19:00 ` Gabriel Krisman Bertazi
2025-02-12 6:45 ` Thorsten Leemhuis
2025-02-12 9:31 ` David Gow
2025-02-12 22:09 ` Kees Cook [this message]
2025-02-12 13:56 ` Thorsten Leemhuis
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=202502121409.864E362899@keescook \
--to=kees@kernel.org \
--cc=davidgow@google.com \
--cc=dpereira@lkcamp.dev \
--cc=gabriel@krisman.be \
--cc=gbittencourt@lkcamp.dev \
--cc=kunit-dev@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=porlando@lkcamp.dev \
--cc=regressions@lists.linux.dev \
--cc=skhan@linuxfoundation.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