From: Aleksa Sarai <cyphar@cyphar.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>,
shuah@kernel.org, Christian Brauner <christian@brauner.io>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: openat2: Fix testing failure for O_LARGEFILE flag
Date: Tue, 24 Aug 2021 21:21:29 +1000 [thread overview]
Message-ID: <20210824112129.2t6lzqyf2dxllw4a@senku> (raw)
In-Reply-To: <a9dc1616-61b9-c010-950c-521693c74247@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 2885 bytes --]
On 2021-08-23, Shuah Khan <skhan@linuxfoundation.org> wrote:
> Hi Baolin,
>
> On 8/22/21 8:40 PM, Baolin Wang wrote:
> > Hi Shuah,
> >
> > On 2021/7/28 20:32, Baolin Wang wrote:
> > > Hi,
> > >
> > > > When running the openat2 test suite on ARM64 platform, we got below failure,
> > > > since the definition of the O_LARGEFILE is different on ARM64. So we can
> > > > set the correct O_LARGEFILE definition on ARM64 to fix this issue.
> > >
> > > Sorry, I forgot to copy the failure log:
> > >
>
> Please cc everybody get_maintainers.pl suggests. You are missing
> key reviewers for this change.
>
> Adding Christian Brauner and Aleksa Sarai to the thread.
>
> > > # openat2 unexpectedly returned # 3['/lkp/benchmarks/kernel_selftests/tools/testing/selftests/openat2'] with 208000 (!= 208000)
>
> Not sure I understand this. 208000 (!= 208000) look sthe same to me.
>
> > > not ok 102 openat2 with incompatible flags (O_PATH | O_LARGEFILE) fails with -22 (Invalid argument)
> > >
> > > >
> > > > Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> >
> > Could you apply this patch if no objection from your side? Thanks.
> >
>
> Ideally this define should come from an include file.
The issue is that O_LARGEFILE is set to 0 by glibc because glibc appears
to hide the nuts and bolts of largefile support from userspace. I
couldn't find a nice way of doing a architecture-dependent includes of
include/uapi from kselftests, so I just went with this instead -- but I
agree that a proper include would be better if someone can figure out
how to do it.
> Christian, Aleksa,
>
> Can you review this patch and let me know if this approach looks right.
Reviewed-by: Aleksa Sarai <cyphar@cyphar.com>
It'd be nice to fix this for the other architectures I mention in the
comment (mips, parisc, powerpc, sparc) -- which are the ones that I
could find that had a custom O_LARGEFILE definition.
> > > > ---
> > > > tools/testing/selftests/openat2/openat2_test.c | 4 ++++
> > > > 1 file changed, 4 insertions(+)
> > > >
> > > > diff --git a/tools/testing/selftests/openat2/openat2_test.c b/tools/testing/selftests/openat2/openat2_test.c
> > > > index d7ec1e7..1bddbe9 100644
> > > > --- a/tools/testing/selftests/openat2/openat2_test.c
> > > > +++ b/tools/testing/selftests/openat2/openat2_test.c
> > > > @@ -22,7 +22,11 @@
> > > > * XXX: This is wrong on {mips, parisc, powerpc, sparc}.
> > > > */
> > > > #undef O_LARGEFILE
> > > > +#ifdef __aarch64__
> > > > +#define O_LARGEFILE 0x20000
> > > > +#else
> > > > #define O_LARGEFILE 0x8000
> > > > +#endif
> > > > struct open_how_ext {
> > > > struct open_how inner;
> > > >
> >
>
> thanks,
> -- Shuah
--
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
<https://www.cyphar.com/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-08-24 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 12:29 [PATCH] selftests: openat2: Fix testing failure for O_LARGEFILE flag Baolin Wang
2021-07-28 12:32 ` Baolin Wang
2021-08-23 2:40 ` Baolin Wang
2021-08-23 19:23 ` Shuah Khan
2021-08-24 5:26 ` Baolin Wang
2021-08-24 11:21 ` Aleksa Sarai [this message]
2021-08-24 11:36 ` Christian Brauner
2021-08-24 14:33 ` Shuah Khan
2021-08-24 16:50 ` Shuah Khan
2021-08-25 1:49 ` Baolin Wang
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=20210824112129.2t6lzqyf2dxllw4a@senku \
--to=cyphar@cyphar.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).