From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>, Jan Stancek <jstancek@redhat.com>,
Cyril Hrubis <chrubis@suse.cz>,
Paulson Raja L <lpaulsonraja@gmail.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Added test for mmap() with MAP_SHARED_VALIDATE.
Date: Tue, 4 Apr 2023 13:15:07 +0200 [thread overview]
Message-ID: <20230404111507.GA1269544@pevik> (raw)
In-Reply-To: <20230404110751.GA1268429@pevik>
> Hi all,
> FYI test fails on ppc64le: mmap() with MAP_SHARED_VALIDATE | (1 << 7) is
> supposed to fail with EOPNOTSUPP, but on ppc64le it fails with EFAULT.
> Obviously (1 << 7) being expected as invalid flag is not working well at least
> on ppc64le. It might be something page size related or alignment. I was looking
> into SYSCALL_DEFINE6(mmap, ...) implementations. Although ppc64le implementation
> is not the same as most of implementations on other archs, in the end it also
> calls ksys_mmap_pgoff(addr, len, prot, flags, fd, off >> shift) as the other
> archs. Any idea what could be a problem?
OK, 1 << 7 defined as MAP_LOCKED on ppc64le and mips. 1 << 9 looks to be working
on more archs, I'll send a patch.
Kind regards,
Petr
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-04-04 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 12:13 [LTP] [PATCH] Added test for mmap() with MAP_SHARED_VALIDATE paulson
2023-03-24 10:33 ` Petr Vorel
2023-03-25 4:01 ` Paulson Raja L
2023-03-27 10:21 ` Petr Vorel
2023-03-28 3:14 ` Li Wang
2023-03-28 8:17 ` Petr Vorel
2023-03-28 8:30 ` Li Wang
2023-03-28 10:39 ` Petr Vorel
2023-04-04 11:07 ` Petr Vorel
2023-04-04 11:15 ` Petr Vorel [this message]
2023-03-27 10:51 ` Petr Vorel
2023-03-28 3:39 ` Li Wang
2023-03-28 8:11 ` Petr Vorel
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=20230404111507.GA1269544@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=liwang@redhat.com \
--cc=lpaulsonraja@gmail.com \
--cc=ltp@lists.linux.it \
/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