From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux390@de.ibm.com, linux-s390@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>
Subject: Re: [PATCH] s390: ensure NUL termination by strncpy()
Date: Mon, 16 Nov 2009 22:13:29 +0100 [thread overview]
Message-ID: <20091116211328.GA5828@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <4B019FC2.3060004@gmail.com>
On Mon, Nov 16, 2009 at 07:53:54PM +0100, Roel Kluin wrote:
> For a larger source string, strncpy only NUL terminates when
> the size argument is less than the size of the destination string.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> arch/s390/kernel/ipl.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> Is this maybe needed?
No, kernel_nss_name as well as the data.nss.name char array within ipl_info
have the same size. So it will always fit and it is always NUL terminated.
Maybe it should be changed to a simple memcpy, like we have it at a second
place in the same file. I think that's up to Michael.
> diff --git a/arch/s390/kernel/ipl.c b/arch/s390/kernel/ipl.c
> index 4890ac6..d52fcb4 100644
> --- a/arch/s390/kernel/ipl.c
> +++ b/arch/s390/kernel/ipl.c
> @@ -1881,7 +1881,7 @@ void __init setup_ipl(void)
> break;
> case IPL_TYPE_NSS:
> strncpy(ipl_info.data.nss.name, kernel_nss_name,
> - sizeof(ipl_info.data.nss.name));
> + sizeof(ipl_info.data.nss.name) - 1);
> break;
> case IPL_TYPE_UNKNOWN:
> /* We have no info to copy */
prev parent reply other threads:[~2009-11-16 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 18:53 [PATCH] s390: ensure NUL termination by strncpy() Roel Kluin
2009-11-16 21:13 ` Heiko Carstens [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=20091116211328.GA5828@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=roel.kluin@gmail.com \
--cc=schwidefsky@de.ibm.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