From: Ben Hutchings <ben@decadent.org.uk>
To: Tomas Hozza <thozza@redhat.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
jasowang@redhat.com, kys@microsoft.com
Subject: Re: [PATCH 1/3] tools/hv: Fix for long file names from readdir
Date: Tue, 27 Nov 2012 20:41:11 +0000 [thread overview]
Message-ID: <20121127204111.GY13292@decadent.org.uk> (raw)
In-Reply-To: <1758221706.1851628.1354048105347.JavaMail.root@redhat.com>
On Tue, Nov 27, 2012 at 03:28:25PM -0500, Tomas Hozza wrote:
>
>
> ----- Original Message -----
> > On Tue, 2012-11-27 at 08:56 +0100, 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.
> > >
> > > Buffer sizes have been changed to PATH_MAX, include "limits.h"
> > > where
> > > PATH_MAX is defined was added and length checks ware added via
> > > snprintf.
> > [...]
> >
> > PATH_MAX has nothing to do with any actual kernel limit; it's no more
> > meaningful than the current value of 256. Network interface names
> > are
> > limited to 15 characters, thus the current array is more than long
> > enough. So I think this is entirely unnecessary.
>
> This is just for sanity. The value PATH_MAX was chosen after discussion
> with K. Y. Srinivasan and Olaf Hering instead of some "magic" number like
> 256 or 512.
PATH_MAX is a magic name.
> > Using snprintf() is a good idea, but you need to check the return
> > value and handle the truncation case somehow.
>
> By using PATH_MAX sized buffer there is no need for handling the truncation
> case.
You are claiming two contradictory things: sprintf() may overrun the
buffer, so we need the length check provided by snprintf(), but there
is no need to check for truncation because we know the length is
sufficient.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
next prev parent reply other threads:[~2012-11-27 20:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 14:01 [PATCH 1/3] tools/hv: Fix /var subdirectory Tomas Hozza
2012-11-09 14:01 ` [PATCH 2/3] tools/hv: Fix string types Tomas Hozza
2012-11-09 15:56 ` KY Srinivasan
2012-11-09 14:01 ` [PATCH 3/3] tools/hv: Fix permissions of created directory and files Tomas Hozza
2012-11-09 15:52 ` KY Srinivasan
2012-11-09 15:57 ` KY Srinivasan
2012-11-09 15:56 ` [PATCH 1/3] tools/hv: Fix /var subdirectory KY Srinivasan
2012-11-12 8:55 ` Tomas Hozza
2012-11-12 8:55 ` [PATCH 3/3] tools/hv: Fix permissions of created directory and files Tomas Hozza
2012-11-26 20:40 ` KY Srinivasan
2012-11-26 20:42 ` [PATCH 1/3] tools/hv: Fix /var subdirectory KY Srinivasan
2012-11-26 21:12 ` gregkh
2012-11-26 21:15 ` KY Srinivasan
2012-11-27 7:56 ` [PATCH 1/3] tools/hv: Fix for long file names from readdir Tomas Hozza
2012-11-27 7:56 ` [PATCH 2/3] tools/hv: Fix /var subdirectory Tomas Hozza
2012-11-27 13:59 ` KY Srinivasan
2012-11-27 7:56 ` [PATCH 3/3] tools/hv: Fix permissions of created directory and files Tomas Hozza
2012-11-27 13:59 ` KY Srinivasan
2012-11-27 13:58 ` [PATCH 1/3] tools/hv: Fix for long file names from readdir KY Srinivasan
2012-11-27 14:50 ` Ben Hutchings
2012-11-27 20:28 ` Tomas Hozza
2012-11-27 20:41 ` Ben Hutchings [this message]
2012-12-18 8:06 ` Tomas Hozza
2012-12-18 12:38 ` Ben Hutchings
2013-01-17 18:41 ` Greg KH
2012-11-15 23:38 ` [PATCH 1/3] tools/hv: Fix /var subdirectory gregkh
2012-11-15 23:52 ` 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=20121127204111.GY13292@decadent.org.uk \
--to=ben@decadent.org.uk \
--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=olaf@aepfle.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.