From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH] f2fs_io: fix wrong buffered/dio option
Date: Fri, 12 Jul 2019 14:20:37 -0700 [thread overview]
Message-ID: <20190712212037.41820-1-jaegeuk@kernel.org> (raw)
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
tools/f2fs_io/f2fs_io.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/f2fs_io/f2fs_io.c b/tools/f2fs_io/f2fs_io.c
index 91f8cf2..7fd4425 100644
--- a/tools/f2fs_io/f2fs_io.c
+++ b/tools/f2fs_io/f2fs_io.c
@@ -194,9 +194,9 @@ static void do_write(int argc, char **argv, const struct cmd_desc *cmd)
exit(1);
}
- if (!strcmp(argv[5], "buffered")) {
+ if (!strcmp(argv[5], "dio")) {
flags |= O_DIRECT;
- } else if (strcmp(argv[5], "dio")) {
+ } else if (strcmp(argv[5], "buffered")) {
fputs("Wrong IO type\n\n", stderr);
exit(1);
}
@@ -263,9 +263,9 @@ static void do_read(int argc, char **argv, const struct cmd_desc *cmd)
exit(1);
}
count = atoi(argv[3]);
- if (!strcmp(argv[4], "buffered")) {
+ if (!strcmp(argv[4], "dio")) {
flags |= O_DIRECT;
- } else if (strcmp(argv[4], "dio")) {
+ } else if (strcmp(argv[4], "buffered")) {
fputs("Wrong IO type\n\n", stderr);
exit(1);
}
--
2.19.0.605.g01d371f741-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-07-12 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 21:20 Jaegeuk Kim [this message]
2019-07-17 10:12 ` [f2fs-dev] [PATCH] f2fs_io: fix wrong buffered/dio option Chao Yu
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=20190712212037.41820-1-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).