From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] pkeys: Fix uclibc build caused by conflicting signature
Date: Wed, 2 Oct 2019 04:03:14 -0400 (EDT) [thread overview]
Message-ID: <1944770230.3074247.1570003394396.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191001184750.20995-1-petr.vorel@gmail.com>
----- Original Message -----
> Removing static fixes the problem.
I'd prefer we rename test functions:
#ifndef HAVE_PKEY_MPROTECT
static inline int my_pkey_alloc()
#else
#define my_pkey_alloc pkey_alloc
#endif
my_pkey_alloc()
>
> uClibc defines pkey_{alloc,free,mprotect} signatures in
> <bits/mman-shared.h>, which is included by <bits/mman-linux.h>. Because
> it does not implement them, our implementation signature conflicts, as
> it uses static.
>
> Fixed build error:
> In file included from pkey01.c:32:0:
> pkey.h:18:19: error: static declaration of ?pkey_mprotect? follows non-static
> declaration
> static inline int pkey_mprotect(void *addr, size_t len, int prot, int pkey)
> ^
> In file included from
> /opt/br-test-pkg/br-arm-full/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/bits/mman-linux.h:115:0,
> from
> /opt/br-test-pkg/br-arm-full/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/bits/mman.h:40,
> from
> /opt/br-test-pkg/br-arm-full/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/sys/mman.h:41,
> from pkey01.c:29:
> /opt/br-test-pkg/br-arm-full/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/bits/mman-shared.h:73:5:
> note: previous declaration of ?pkey_mprotect? was here
> int pkey_mprotect (void *__addr, size_t __len, int __prot, int __pkey)
> __THROW;
> ^
> In file included from pkey01.c:32:0:
>
> Found with test-pkg tool from Buildroot distribution.
>
> Fixes: 90c2dc89f ("pkey: add test for memory protection keys")
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> testcases/kernel/syscalls/pkeys/pkey.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/pkeys/pkey.h
> b/testcases/kernel/syscalls/pkeys/pkey.h
> index d623244eb..19c8447eb 100644
> --- a/testcases/kernel/syscalls/pkeys/pkey.h
> +++ b/testcases/kernel/syscalls/pkeys/pkey.h
> @@ -15,17 +15,17 @@
> #endif
>
> #ifndef HAVE_PKEY_MPROTECT
> -static inline int pkey_mprotect(void *addr, size_t len, int prot, int pkey)
> +inline int pkey_mprotect(void *addr, size_t len, int prot, int pkey)
> {
> return tst_syscall(__NR_pkey_mprotect, addr, len, prot, pkey);
> }
>
> -static inline int pkey_alloc(unsigned int flags, unsigned int access_rights)
> +inline int pkey_alloc(unsigned int flags, unsigned int access_rights)
> {
> return tst_syscall(__NR_pkey_alloc, flags, access_rights);
> }
>
> -static inline int pkey_free(int pkey)
> +inline int pkey_free(int pkey)
> {
> return tst_syscall(__NR_pkey_free, pkey);
> }
> --
> 2.23.0
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
next prev parent reply other threads:[~2019-10-02 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 18:47 [LTP] [PATCH] pkeys: Fix uclibc build caused by conflicting signature Petr Vorel
2019-10-02 8:03 ` Jan Stancek [this message]
2019-10-02 10:36 ` 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=1944770230.3074247.1570003394396.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.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