public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Holidays and LTP release
Date: Fri, 15 Jan 2021 15:27:58 +0100	[thread overview]
Message-ID: <YAGmbrmtAtyI8zQ4@yuki.lan> (raw)
In-Reply-To: <YAGgEcFEN8/ElosC@yuki.lan>

Hi!
> > > > getrlimit03.c:168: TPASS: __NR_prlimit64(0) and __NR_ugetrlimit(0)
> > > > gave consistent results
> > > > tst_test.c:1313: TBROK: Test killed by SIGILL!
> > >
> > > Can we have a backtrace here? It's impossible to say what happened here
> > > without further debugging.
> > 
> > I do not have backtrace log for this now.
> > Let me share strace output log in this link,
> > # strace -f ./getrlimit03
> > https://lkft.validation.linaro.org/scheduler/job/2145166#L2569
> 
> Thanks.
> 
> I've managed to reproduce as well but I have no idea what happens there,
> it looks like something gets corrupted and the processor attempts to
> execute invalid code.
> 
> Maybe we pass wrong size of the rlim structure somewhere and kernel
> writes over a stack.

This is really strange it looks like glibc has wrong syscall number for
getrlimit.

On 32bit ARM I do have in /usr/include/asm-generic/unistd.h

#define __NR_getrlimit 163

While the getrlimit should be 191. It looks like x86-64 syscall
definitions are installed on the system for some strange reason, even
the header says that it's for x86-64.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2021-01-15 14:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 12:18 [LTP] Holidays and LTP release Cyril Hrubis
2021-01-06 12:19 ` Cyril Hrubis
2021-01-07 11:51   ` Cyril Hrubis
2021-01-08  1:23     ` Yang Xu
2021-01-08 13:28       ` Cyril Hrubis
2021-01-11 14:38     ` Cyril Hrubis
2021-01-12 10:29       ` Petr Vorel
2021-01-13  8:57   ` =?unknown-8bit?q?K=C3=B6ry?= Maincent
2021-01-14 11:12     ` Naresh Kamboju
2021-01-14 14:14       ` Martin Doucha
2021-01-20  9:31         ` Naresh Kamboju
2021-01-20 10:26           ` Cyril Hrubis
2021-01-20 13:33             ` Cyril Hrubis
2021-01-14 14:36       ` Cyril Hrubis
2021-01-15  8:27         ` Naresh Kamboju
2021-01-15 14:00           ` Cyril Hrubis
2021-01-15 14:27             ` Cyril Hrubis [this message]
2021-01-14  9:17   ` Martin Doucha
2021-01-14 10:41     ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2021-01-14 15:01 gengcixi
2021-01-15 15:08 gengcixi
2021-01-19 10:43 ` Cyril Hrubis

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=YAGmbrmtAtyI8zQ4@yuki.lan \
    --to=chrubis@suse.cz \
    --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