public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] fcntl36: fix 32-bit sporadic failures
Date: Fri, 15 Jun 2018 14:39:29 -0400 (EDT)	[thread overview]
Message-ID: <1789102313.26921391.1529087969115.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CADtBP2CCPTXgy7QhESn-qMUv2wSM+xpEksMT1hWwfcFvk50HqA@mail.gmail.com>



----- Original Message -----
> Jan,
> 
> Running in a container, armhf userland, with arm64 kernel (real HW: hikey):
> 
> $ uname -a
> Linux ltpfcntl36 4.16.0-2-arm64 #1 SMP Debian 4.16.12-1 (2018-05-27)
> armv8l GNU/Linux
> 
> $ file ./fcntl36
> ./fcntl36: ELF 32-bit LSB pie executable ARM, EABI5 version 1 (SYSV),
> dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for
> GNU/Linux 3.2.0,
> BuildID[sha1]=074ba3622d50f62108260d2912ae5dc0e8d52d46, with
> debug_info, not stripped
> 
> My un-patched binary shows me:
> 
> [pid  3501] fcntl64(11, F_OFD_SETLK, {l_type=F_UNLCK,
> l_whence=SEEK_SET, l_start=16384, l_len=4096} <unfinished ...>
> 
> no F_SETLK for this binary.
> 
> Running in a container, arm64 userland, with arm64 kernel (real HW: hikey):
> 
> $ file ./fcntl36
> ./fcntl36: ELF 64-bit LSB pie executable ARM aarch64, version 1
> (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1,
> for GNU/Linux 3.7.0,
> BuildID[sha1]=8fb1d0e0e0d027fce5c8d11742ce5bdb7678749b, with
> debug_info, not stripped
> 
> Same un-patched binary shows me:
> 
> [pid   483] fcntl(10, F_OFD_SETLKW, {l_type=F_UNLCK,
> l_whence=SEEK_SET, l_start=13312, l_len=4096} <unfinished ...>
> 
> Do you want me to test patched LTP in arm32/64 to make sure they work

Yes, if possible test patched LTP in environment which
is known to hit the failure.

> and you check if it fixes the issue for i686 on your side ?

I already did, it does eliminate problem for me.

> Or should
> I compile it some other way ?

Default build is OK. Apply patch, build and see if
you can reproduce the failure.

> 
> Let me know what you need.
> 
> Rafael
> 
> On 15 June 2018 at 14:22, Jan Stancek <jstancek@redhat.com> wrote:
> 
> > No kernel bug, problem was found in my reproducer.
> > Can anyone confirm this fixes 32-bit arm too?
> 

  reply	other threads:[~2018-06-15 18:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 17:22 [LTP] [PATCH] fcntl36: fix 32-bit sporadic failures Jan Stancek
2018-06-15 18:27 ` Rafael Tinoco
2018-06-15 18:39   ` Jan Stancek [this message]
2018-06-16  4:15 ` Li Wang
2018-06-19  7:51 ` Naresh Kamboju
2018-06-19 10:56   ` Jan Stancek

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=1789102313.26921391.1529087969115.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