From: jes.sorensen@gmail.com
To: Xiao Ni <xni@redhat.com>
Cc: linux-raid@vger.kernel.org, ncroxon@redhat.com
Subject: Re: [MDADM PATCH 2/2] Specify suitable size when write to buffer
Date: Mon, 06 Mar 2017 16:21:54 -0500 [thread overview]
Message-ID: <wrfjd1dum77x.fsf@gmail.com> (raw)
In-Reply-To: <1488348766-31087-3-git-send-email-xni@redhat.com> (Xiao Ni's message of "Wed, 1 Mar 2017 14:12:46 +0800")
Xiao Ni <xni@redhat.com> writes:
> ---
> Detail.c | 2 +-
> super-intel.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Detail.c b/Detail.c
> index 509b0d4..f4d4241 100644
> --- a/Detail.c
> +++ b/Detail.c
> @@ -575,7 +575,7 @@ This is pretty boring
> printf(" Member Arrays :");
>
> while (dir && (de = readdir(dir)) != NULL) {
> - char path[200];
> + char path[320];
> char vbuf[1024];
> int nlen = strlen(sra->sys_name);
> dev_t devid;
> diff --git a/super-intel.c b/super-intel.c
> index d5e9517..ea50265 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -1811,7 +1811,7 @@ static void examine_super_imsm(struct supertype *st, char *homehost)
> __u32 reserved = imsm_reserved_sectors(super, super->disks);
> struct dl *dl;
>
> - snprintf(str, MPB_SIG_LEN, "%s", mpb->sig);
> + snprintf(str, MAX_SIGNATURE_LENGTH, "%s", mpb->sig);
> printf(" Magic : %s\n", str);
> snprintf(str, strlen(MPB_VERSION_RAID0), "%s", get_imsm_version(mpb));
> printf(" Version : %s\n", get_imsm_version(mpb));
Hi Xiao,
This is really two independent changes, so they should come in two
seperate patches. All the patches needs their own commit messages and
signed-off-by lines.
Thanks,
Jes
prev parent reply other threads:[~2017-03-06 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 6:12 [MDADM PATCH 0/2] Fix some building errors Xiao Ni
2017-03-01 6:12 ` [MDADM PATCH 1/2] Add Wimplicit-fallthrough=0 in Makefile Xiao Ni
2017-03-06 20:30 ` jes.sorensen
2017-03-01 6:12 ` [MDADM PATCH 2/2] Specify suitable size when write to buffer Xiao Ni
2017-03-06 21:21 ` jes.sorensen [this message]
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=wrfjd1dum77x.fsf@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=ncroxon@redhat.com \
--cc=xni@redhat.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 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.