All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] LTP: readahead02 failed
Date: Mon, 15 May 2017 03:22:09 -0400 (EDT)	[thread overview]
Message-ID: <1149421133.11389918.1494832929012.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYvHus+AB1CD4AGxw3pOAKavO=gQ0W2zfPSZ-qkUac9U-w@mail.gmail.com>


----- Original Message -----
> Hi Team,
> 
> readahead02 failed on HiKey board with below error message.
> 1. Any minimal limitation of Buffers size or Cached size should have
> to pass this test case ?  if yes we would change test logic to detect
> and skip test run.

Hi,

Your system appears to have plenty of memory for this test.

> 2. The first FAIL message is not giving enough information (*) there
> is a room for improvement here.

I pushed a patch to include errno code in failure message.

> 3.  strace output show Invalid argument for readahead()
> 
> readahead(3, 0, 67108864)               = -1 EINVAL (Invalid argument)
> write(1, "readahead02    1  TFAIL  :  read"..., 100readahead02    1
> TFAIL  :  readahead02.c:86: unexpected failure - returned value = -1,
> expected: 0
> ) = 100
> 
> The man page have explanation of EINVAL is
> EINVAL fd  does  not  refer  to a file type to which readahead() can be
> applied.

Have you run into this with any of previous kernels?

What filesystem is /tmp? Is it tmpfs?

Can you try with LTP tmpdir backed by different fs?
For example: env TMPDIR=/root/ ./readahead02

Regards,
Jan

  reply	other threads:[~2017-05-15  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 14:24 [LTP] LTP: readahead02 failed Naresh Kamboju
2017-05-15  7:22 ` Jan Stancek [this message]
2017-05-15  7:36   ` Naresh Kamboju

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=1149421133.11389918.1494832929012.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.