From: santosh.shilimkar@oracle.com (santosh.shilimkar at oracle.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] divers/soc/ti: fix max dup length for kstrndup
Date: Sat, 16 Dec 2017 14:46:18 -0800 [thread overview]
Message-ID: <5930109a-f31f-8a2a-87bf-70326ed91e16@oracle.com> (raw)
In-Reply-To: <20171212092935.20211-1-mashimiao.fnst@cn.fujitsu.com>
On 12/12/17 1:29 AM, Ma Shimiao wrote:
> If source string longer than max, kstrndup will alloc max+1 space.
> So, we should make sure the result will not over limit.
>
> Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
> ---
Applied. Thanks !!
prev parent reply other threads:[~2017-12-16 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 9:29 [PATCH] divers/soc/ti: fix max dup length for kstrndup Ma Shimiao
2017-12-16 22:46 ` santosh.shilimkar at oracle.com [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=5930109a-f31f-8a2a-87bf-70326ed91e16@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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