From: Tejun Heo <tj@kernel.org>
To: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Cc: lizefan@huawei.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup: limit max copied char length for cgroup file name
Date: Mon, 11 Dec 2017 07:05:51 -0800 [thread overview]
Message-ID: <20171211150551.GC2421075@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20171209054758.13870-1-mashimiao.fnst@cn.fujitsu.com>
On Sat, Dec 09, 2017 at 01:47:58PM +0800, Ma Shimiao wrote:
> the result of cgroup_file_name will be used by kernfs_remove_name,
> and then by kernfs_remove_by_name_ns().
> If reached the max length, may have problem printed by WARN() in
> kernfs_remove_by_name_ns().
>
> Signed-off-by: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
Can we use strscpy() instead?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-12-11 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 5:47 [PATCH] cgroup: limit max copied char length for cgroup file name Ma Shimiao
2017-12-11 15:05 ` Tejun Heo [this message]
2017-12-12 1:19 ` Ma Shimiao
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=20171211150551.GC2421075@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mashimiao.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).