From: Jan Stancek <jstancek@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] diotest3: fix -f argument
Date: Wed, 6 Nov 2013 16:34:58 -0500 (EST) [thread overview]
Message-ID: <1924029835.23120751.1383773698263.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1383755951-21231-1-git-send-email-jlayton@redhat.com>
----- Original Message -----
> From: "Jeff Layton" <jlayton@redhat.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Wednesday, 6 November, 2013 5:39:11 PM
> Subject: [LTP] [PATCH] diotest3: fix -f argument
>
> The '-f' argument to diotest3 is currently ignored. During options
> processing it's copied to the buffer, then subsequently overwritten
> by the default in a later sprintf() call.
>
> Move the setting of the default prior to the options processing.
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
Hi Jeff,
pushed. I checked also other diotest*.c, but diotest3.c
was the only one having this issue.
Thanks,
Jan
> ---
> testcases/kernel/io/direct_io/diotest3.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/testcases/kernel/io/direct_io/diotest3.c
> b/testcases/kernel/io/direct_io/diotest3.c
> index ac460ed..002a6d0 100644
> --- a/testcases/kernel/io/direct_io/diotest3.c
> +++ b/testcases/kernel/io/direct_io/diotest3.c
> @@ -238,6 +238,8 @@ int main(int argc, char *argv[])
> int numchild = 1; /* Number of children. Default 5 */
> int i, fail_count = 0, failed = 0, total = 0;
>
> + sprintf(filename, "testdata-3.%ld", syscall(__NR_gettid));
> +
> /* Options */
> while ((i = getopt(argc, argv, "b:o:i:n:f:")) != -1) {
> switch (i) {
> @@ -277,7 +279,6 @@ int main(int argc, char *argv[])
> prg_usage();
> }
> }
> - sprintf(filename, "testdata-3.%ld", syscall(__NR_gettid));
>
> setup();
>
> --
> 1.7.1
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-11-06 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 16:39 [LTP] [PATCH] diotest3: fix -f argument Jeff Layton
2013-11-06 21:34 ` Jan Stancek [this message]
2013-11-06 21:43 ` Jeff Layton
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=1924029835.23120751.1383773698263.JavaMail.root@redhat.com \
--to=jstancek@redhat.com \
--cc=jlayton@redhat.com \
--cc=ltp-list@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 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.