From: Jakub Kicinski <kuba@kernel.org>
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net v2 3/6] netdevsim: fix stack-out-of-bounds in nsim_dev_debugfs_init()
Date: Mon, 27 Jan 2020 20:04:45 -0800 [thread overview]
Message-ID: <20200127200445.760e34ee@cakuba> (raw)
In-Reply-To: <20200127143034.1367-1-ap420073@gmail.com>
On Mon, 27 Jan 2020 14:30:34 +0000, Taehee Yoo wrote:
> When netdevsim dev is being created, a debugfs directory is created.
> The variable "dev_ddir_name" is 16bytes device name pointer and device
> name is "netdevsim<dev id>".
> The maximum dev id length is 10.
> So, 16bytes for device name isn't enough.
> Fixes: ab1d0cc004d7 ("netdevsim: change debugfs tree topology")
> Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
prev parent reply other threads:[~2020-01-28 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 14:30 [PATCH net v2 3/6] netdevsim: fix stack-out-of-bounds in nsim_dev_debugfs_init() Taehee Yoo
2020-01-28 4:04 ` Jakub Kicinski [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=20200127200445.760e34ee@cakuba \
--to=kuba@kernel.org \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).