From: Evgeny Kuznetsov <EXT-Eugeny.Kuznetsov@nokia.com>
To: menage@google.com, lizf@cn.fujitsu.com
Cc: akpm@linux-foundation.org, kamezawa.hiroyu@jp.fujitsu.com,
bblum@andrew.cmu.edu, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, ext-eugeny.kuznetsov@nokia.com
Subject: [PATCH 0/1] cgroups: strcpy destination string overflow
Date: Tue, 5 Oct 2010 12:38:04 +0400 [thread overview]
Message-ID: <cover.1286193571.git.EXT-Eugeny.Kuznetsov@nokia.com> (raw)
Hi,
Here is patch which fixes minor bug in /kernel/cgroup.c file.
Function "strcpy" is used without check for maximum allowed source
string length and could cause destination string overflow.
Thanks,
Best Regards,
Evgeny
Evgeny Kuznetsov (1):
cgroups: strcpy destination string overflow
kernel/cgroup.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
next reply other threads:[~2010-10-05 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 8:38 Evgeny Kuznetsov [this message]
2010-10-05 8:38 ` [PATCH 1/1] cgroups: strcpy destination string overflow Evgeny Kuznetsov
2010-10-05 19:48 ` Andrew Morton
2010-10-05 19:50 ` Paul Menage
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=cover.1286193571.git.EXT-Eugeny.Kuznetsov@nokia.com \
--to=ext-eugeny.kuznetsov@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=bblum@andrew.cmu.edu \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.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