public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>,
	Florian Weimer <fw@deneb.enyo.de>
Cc: libc-alpha@sourceware.org
Subject: Re: failures on Raspberry Pi
Date: Tue, 2 Feb 2021 09:17:35 -0300	[thread overview]
Message-ID: <a68630ac-5c7c-7671-4da0-47a85aaf8475@linaro.org> (raw)
In-Reply-To: <mw35yfpk9k.fsf@tomate.loria.fr>



On 01/02/2021 18:09, Paul Zimmermann wrote:
>        Florian,
> 
>>> I can provide more details if needed. For the tests with "timed out", is there
>>> a way to increase the default timeout threshold?
>>
>> There is TIMEOUTFACTOR for that.
> 
> thank you, with TIMEOUTFACTOR=1000 I still get 3 failures:
> 
> FAIL: elf/tst-glibc-hwcaps-prepend-cache
> FAIL: localedata/sort-test
> FAIL: misc/tst-sysvshm-linux
> 
> $ cat elf/tst-glibc-hwcaps-prepend-cache.out
> tst-glibc-hwcaps-prepend-cache.c:109: numeric comparison failure
>    left: 2 (0x2); from: marker1 ()
>   right: 3 (0x3); from: 3
> error: tst-glibc-hwcaps-prepend-cache.c:118: not true: dlopen (SONAME, RTLD_NOW) == NULL
> error: 2 test failures
> running post-clean rsync

I think this is the missing ld.so.cache for cross-compiling which
should be fixed by a50a080f6b0f958eb30d7520212f25f946ed7f8f.

> 
> $ grep FAIL localedata/sort-test.out
> cmn_TW.UTF-8 xfrm-test FAIL

I am not sure about this one.

> 
> $ cat misc/tst-sysvshm-linux.out
> ../sysdeps/unix/sysv/linux/tst-sysvshm-linux.c:155: numeric comparison failure
>    left: 4278190079 (0xfeffffff); from: ipcinfo.shmmax
>   right: 2147483647 (0x7fffffff); from: tipcinfo.shmmax
> error: 1 test failures

I noticed it on some 32-bit architectures running on 32-bit kernels.  The issue 
is shmctl (IPC_INFO) clamps shmmax on for:

  1. Compat symbols with IPC_64, i.e, 32-bit binaries running on 64-bit kernels.

1246 static int copy_compat_shminfo_to_user(void __user *buf, struct shminfo64 *in,
1247                                         int version)
1248 {
1249         if (in->shmmax > INT_MAX)
1250                 in->shmmax = INT_MAX;

  2. Default symbol with IPC_OLD and glibc always use IPC_64 now. It means that
     32-bit binaries running on 32-bit kernels will not see shmmax being clamped
     anymore.

 801 static inline unsigned long copy_shminfo_to_user(void __user *buf, struct shminfo64 *in, int version)
 802 {
 803         switch (version) {
 804         case IPC_64:
 805                 return copy_to_user(buf, in, sizeof(*in));
 806         case IPC_OLD:
 807             {
 808                 struct shminfo out;
 809 
 810                 if (in->shmmax > INT_MAX)
 811                         out.shmmax = INT_MAX;
 812                 else
 813                         out.shmmax = (int)in->shmmax;

It means that we will need to check if whether the kernel will use the compat
symbols to properly handle on tst-sysvshm-linux.  I am more inclined in just
remove the shmmax tests and add a comment why it is complicated to do a proper
check.

> 
> Are those expected?
> 
> Paul
> 

  reply	other threads:[~2021-02-02 12:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  7:33 Paul Zimmermann
2021-01-31 11:17 ` Florian Weimer
2021-02-01 21:09   ` Paul Zimmermann
2021-02-02 12:17     ` Adhemerval Zanella [this message]
2021-02-03  5:16       ` Paul Zimmermann
2021-02-03  6:14       ` Paul Zimmermann
2021-02-02 18:19     ` Joseph Myers
2021-02-02 18:32 ` Carlos O'Donell
2021-02-02 19:30   ` Florian Weimer
2021-02-02 20:32     ` H.J. Lu
2021-02-03  4:50       ` Paul Zimmermann
2021-02-03  5:22     ` Paul Zimmermann

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=a68630ac-5c7c-7671-4da0-47a85aaf8475@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=Paul.Zimmermann@inria.fr \
    --cc=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).