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] LTP: '/proc/self/io' for reading at readahead02.c:113: ENOENT No such file or directory
Date: Tue, 15 Jan 2019 06:36:19 -0500 (EST)	[thread overview]
Message-ID: <1555912299.96157256.1547552179354.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYvA4XWajkvS9pP8vpFjPx=j+3F9TiueUrGjQ2RQ8vJiAQ@mail.gmail.com>



----- Original Message -----
> readahead02 used to pass on arm32 on LTP-20180926 release. Now using
> the latest LTP master it is getting FAILED.
> 
> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
> tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
> mke2fs 1.43.5 (04-Aug-2017)
> [  603.092608] EXT4-fs (loop0): mounting ext2 file system using the
> ext4 subsystem
> [  603.107967] EXT4-fs (loop0): mounted filesystem without journal. Opts:
> (null)
> tst_test.c:1085: INFO: Timeout per run is 0h 15m 00s
> readahead02.c:359: INFO: overlayfs is not configured in this kernel.
> readahead02.c:244: INFO: Test #0: readahead on file
> readahead02.c:134: INFO: creating test file of size: 67108864
> safe_file_ops.c:202: BROK: Failed to open FILE '/proc/self/io' for
> reading at readahead02.c:113: ENOENT

We switched from /proc/$pid to /proc/self in December:
  commit 75506e4f1b52ea6bb63a52afb34035d9dde55d14
  Date:   Tue Dec 4 14:54:19 2018 +0100
    syscalls/readahead02: Simplify reading proc files
   
    Use SAFE_FILE_LINES_SCANF() for parsing multiline /proc/ files
     Use /proc/self/io instead of /proc/$pid/io.

@Naresh, what is the kernel version you see this fail with?

> 
> Best regards
> Naresh Kamboju
> 
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
> 

  parent reply	other threads:[~2019-01-15 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 11:24 [LTP] LTP: '/proc/self/io' for reading at readahead02.c:113: ENOENT No such file or directory Naresh Kamboju
2019-01-15 11:33 ` Rafael David Tinoco
2019-01-15 11:36 ` Jan Stancek [this message]
2019-01-15 11:42   ` Rafael David Tinoco
2019-01-15 12:06     ` Rafael David Tinoco
2019-01-15 12:29       ` Naresh Kamboju
2019-01-15 11:43   ` Jan Stancek
2019-01-15 12:08   ` Naresh Kamboju
2019-01-15 13:03 ` 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=1555912299.96157256.1547552179354.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