From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] inode01: remove "slash" array
Date: Wed, 20 Mar 2013 17:53:57 +0800 [thread overview]
Message-ID: <51498735.6000708@cn.fujitsu.com> (raw)
In-Reply-To: <1363772673-14851-2-git-send-email-jstancek@redhat.com>
On 03/20/2013 05:44 PM, Jan Stancek wrote:
> and replace strcats with snprintf.
>
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
Reviewed-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
> ---
> testcases/kernel/fs/inode/inode01.c | 26 ++++++++++++++++----------
> 1 files changed, 16 insertions(+), 10 deletions(-)
>
> diff --git a/testcases/kernel/fs/inode/inode01.c b/testcases/kernel/fs/inode/inode01.c
> index 9643651..b3a9a0b 100644
> --- a/testcases/kernel/fs/inode/inode01.c
> +++ b/testcases/kernel/fs/inode/inode01.c
> @@ -96,7 +96,6 @@ char rm_string[200];
> FILE *list_stream = NULL;
> int file_id;
> int list_id;
> -char slash[2];
>
> int increment_name(), get_next_name(), mode(), escrivez();
>
> @@ -110,9 +109,7 @@ int main()
> int status;
> int len;
> int term();
> -
> - slash[0] = '/';
> - slash[1] = '\0';
> + int snp_ret;
>
> strcpy(path_string, "inode");
> sprintf(root, "A%d", getpid());
> @@ -160,9 +157,13 @@ int main()
> /* */
> /****************************************/
>
> - strcpy(path_list_string, path_string);
> - strcat(path_list_string, slash);
> - strcat(path_list_string, "path_list");
> + snp_ret = snprintf(path_list_string, sizeof(path_list_string),
> + "%s/path_list", path_string);
> + if (snp_ret < 0 || snp_ret >= sizeof(path_list_string)) {
> + tst_resm(TBROK, "snprintf(path_list_string,..) returned %d",
> + snp_ret);
> + fail_exit();
> + }
> list_id = creat(path_list_string, FILE_MODE);
> if (list_id == -1) {
> fprintf(temp,
> @@ -308,6 +309,7 @@ int level; /* the tree depth variable */
> char new_string[PATH_STRING_LENGTH + 1];
> int new_level;
> int i, j; /* iteration counters */
> + int snp_ret;
>
> switch_flag = level & TRUE;
> if (strlen(string) >= MAX_PATH_STRING_LENGTH) {
> @@ -324,9 +326,13 @@ int level; /* the tree depth variable */
> } else if (level < MAX_DEPTH) {
> for (i = 0; i <= MAX_BREADTH; i++) {
> get_next_name();
> - strcpy(new_string, string);
> - strcat(new_string, slash);
> - strcat(new_string, name);
> + snp_ret = snprintf(new_string, sizeof(new_string),
> + "%s/%s", string, name);
> + if (snp_ret < 0 || snp_ret >= sizeof(new_string)) {
> + tst_resm(TBROK, "snprintf(new_string,..) "
> + "returned %d", snp_ret);
> + fail_exit();
> + }
>
> /****************************************/
> /* */
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-03-20 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 9:44 [LTP] [PATCH] inode01: remove "slash" array Jan Stancek
2013-03-20 9:53 ` Wanlong Gao [this message]
2013-03-20 10:21 ` Caspar Zhang
2013-03-21 0:51 ` Wanlong Gao
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=51498735.6000708@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=jstancek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox