From: Olaf Hering <olaf@aepfle.de>
To: Tomas Hozza <thozza@redhat.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, apw@canonical.com,
jasowang@redhat.com, kys@microsoft.com
Subject: Re: [PATCH] Tools: hv: Fix for long file names from readdir
Date: Thu, 8 Nov 2012 15:19:25 +0100 [thread overview]
Message-ID: <20121108141925.GA20083@aepfle.de> (raw)
In-Reply-To: <1352383995-13856-1-git-send-email-thozza@redhat.com>
On Thu, Nov 08, Tomas Hozza wrote:
> kvp_get_if_name and kvp_mac_to_if_name copy strings into statically
> sized buffers which could be too small to store really long names.
> - char dev_id[256];
> + char dev_id[512];
Shouldnt that be PATH_MAX or similar?
Olaf
next prev parent reply other threads:[~2012-11-08 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 14:13 [PATCH] Tools: hv: Fix for long file names from readdir Tomas Hozza
2012-11-08 14:19 ` Olaf Hering [this message]
2012-11-08 14:52 ` Tomas Hozza
2012-11-08 15:51 ` KY Srinivasan
2012-11-09 12:47 ` Tomas Hozza
2012-11-26 20:43 ` KY Srinivasan
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=20121108141925.GA20083@aepfle.de \
--to=olaf@aepfle.de \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thozza@redhat.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