From: Jarek Poplawski <jarkao2@o2.pl>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
"David S\. Miller" <davem@davemloft.net>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.20] kobject net ifindex + rename
Date: Thu, 1 Mar 2007 08:42:09 +0100 [thread overview]
Message-ID: <20070301074209.GA1735@ff.dom.local> (raw)
In-Reply-To: <20070228184541.GD6134@bougret.hpl.hp.com>
On Wed, Feb 28, 2007 at 10:45:41AM -0800, Jean Tourrilhes wrote:
> On Wed, Feb 28, 2007 at 10:34:37AM +0100, Jarek Poplawski wrote:
> > On 28-02-2007 02:27, Jean Tourrilhes wrote:
> > > Hi all,
> > ...
> > > Patch for 2.6.20 is attached. The patch was tested on a system
> > > running the hotplug scripts, and on another system running udev.
> > >
> > > Have fun...
> > >
> > > Jean
> > >
> > > Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
> > >
> > > ---------------------------------------------------------
> > ...
> > > diff -u -p linux/net/core/net-sysfs.j1.c linux/net/core/net-sysfs.c
> > > --- linux/net/core/net-sysfs.j1.c 2007-02-27 15:01:08.000000000 -0800
> > > +++ linux/net/core/net-sysfs.c 2007-02-27 15:06:49.000000000 -0800
> > > @@ -412,6 +412,17 @@ static int netdev_uevent(struct class_de
> > > if ((size <= 0) || (i >= num_envp))
> > > return -ENOMEM;
> > >
> > > + /* pass ifindex to uevent.
> > > + * ifindex is useful as it won't change (interface name may change)
> > > + * and is what RtNetlink uses natively. */
> > > + envp[i++] = buf;
> > > + n = snprintf(buf, size, "IFINDEX=%d", dev->ifindex) + 1;
> > > + buf += n;
> > > + size -= n;
> > > +
> > > + if ((size <= 0) || (i >= num_envp))
> >
> > Btw.:
> > 1. if size == 10 and snprintf returns 9 (without NULL)
> > then n == 10 (with NULL), so isn't it enough (here and above):
> >
> > if ((size < 0) || (i >= num_envp))
>
> I just cut'n'pasted the code a few line above. If the original
> code is incorrect, it need fixing. And it will need fixing in probably
> a lot of places.
I think you're kind of responsible for your part, at least.
>
> > 2. shouldn't there be (here and above):
> >
> > envp[--i] = NULL;
> >
>
> No, envp is local, so who cares.
But envp[i] isn't (at least here). So, I guess, a caller
of this function could care.
> > > + if ((size <= 0) || (i >= num_envp))
> > > + return -ENOMEM;
And one more thing (not necessarily for you):
ENOBUFS is probably more adequate here.
Cheers,
Jarek P.
next prev parent reply other threads:[~2007-03-01 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 1:27 [PATCH 2.6.20] kobject net ifindex + rename Jean Tourrilhes
[not found] ` <20070228012741.GA3988-yAE0UhLNZJawPNPzzlOzwdBPR1lH4CV8@public.gmane.org>
2007-02-28 9:16 ` Johannes Berg
2007-02-28 18:51 ` Jean Tourrilhes
2007-02-28 19:03 ` Johannes Berg
2007-02-28 9:34 ` Jarek Poplawski
2007-02-28 9:52 ` Jarek Poplawski
2007-02-28 18:45 ` Jean Tourrilhes
2007-03-01 7:42 ` Jarek Poplawski [this message]
2007-03-01 19:27 ` Jean Tourrilhes
2007-03-02 9:18 ` Jarek Poplawski
2007-02-28 15:36 ` Greg KH
2007-02-28 18:43 ` Jean Tourrilhes
2007-03-01 0:26 ` Jean Tourrilhes
2007-03-01 0:37 ` Johannes Berg
2007-03-01 0:51 ` Jean Tourrilhes
2007-03-01 0:57 ` Johannes Berg
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=20070301074209.GA1735@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--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).