From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] Add io_read_eof in common.h utilities
Date: Mon, 13 Dec 2021 13:14:17 +0100 [thread overview]
Message-ID: <20211213121417.21825-1-andrea.cervesato@suse.com> (raw)
Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
---
testcases/kernel/io/ltp-aiodio/common.h | 30 +++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/testcases/kernel/io/ltp-aiodio/common.h b/testcases/kernel/io/ltp-aiodio/common.h
index c9fd0bbaa..c27c3a0ad 100644
--- a/testcases/kernel/io/ltp-aiodio/common.h
+++ b/testcases/kernel/io/ltp-aiodio/common.h
@@ -86,6 +86,36 @@ static inline void io_read(const char *filename, int filesize, volatile int *run
SAFE_CLOSE(fd);
}
+static inline void io_read_eof(const char *filename, volatile int *run_child)
+{
+ char buff[4096];
+ int fd;
+ int r;
+
+ while ((fd = open(filename, O_RDONLY, 0666)) < 0)
+ usleep(100);
+
+ tst_res(TINFO, "child %i reading file", getpid());
+
+ while (*run_child) {
+ off_t offset;
+ char *bufoff;
+
+ offset = SAFE_LSEEK(fd, SEEK_END, 0);
+
+ r = SAFE_READ(0, fd, buff, sizeof(buff));
+ if (r > 0) {
+ bufoff = check_zero(buff, r);
+ if (bufoff) {
+ tst_res(TINFO, "non-zero read at offset %p", offset + bufoff);
+ break;
+ }
+ }
+ }
+
+ SAFE_CLOSE(fd);
+}
+
/*
* This code tries to create dirty free blocks on
* the HDD so there is a chance that blocks to be allocated
--
2.34.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2021-12-13 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 12:14 Andrea Cervesato via ltp [this message]
2021-12-14 16:40 ` [LTP] [PATCH v2] Add io_read_eof in common.h utilities Petr Vorel
2021-12-15 13:06 ` 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=20211213121417.21825-1-andrea.cervesato@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
/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 NNTP newsgroup(s).