From: Pavel Emelyanov <xemul@openvz.org>
To: David Miller <davem@davemloft.net>
Cc: kaber@trash.net, netdev@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] Don't limit the number of tunnels with generic name explicitly.
Date: Tue, 26 Feb 2008 10:47:44 +0300 [thread overview]
Message-ID: <47C3C420.1060407@openvz.org> (raw)
In-Reply-To: <20080223.202021.191612366.davem@davemloft.net>
David Miller wrote:
> From: Pavel Emelyanov <xemul@openvz.org>
> Date: Thu, 21 Feb 2008 15:38:16 +0300
>
>> Changelog:
>>
>> Use the added dev_alloc_name() call to create tunnel device name,
>> rather than iterate in a hand-made loop with an artificial limit.
>>
>> Thanks Patrick for noticing this.
>>
>> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
>
> Applied, but I had to rework this in two places that didn't
> apply cleanly.
That's because you skipped the first patch titled "Don't create
tunnels with '%' in name.", which adds the dev_alloc_name() call
and tosses the error paths a bit. Without this first patch, these
four drivers become broken :( When user doesn't specify the name,
the device's name will be e.g. "tunl%d", but not "tunl0" like
he expects.
> The ip_gre.c and ipip.c changes remove a "failed" label but
> that can't be done in the current tree as there are other
> existing references.
>
Yup :( this code was removed in that first patch...
next prev parent reply other threads:[~2008-02-26 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 12:05 [PATCH] Don't create tunnels with '%' in name Pavel Emelyanov
2008-02-21 12:10 ` Patrick McHardy
2008-02-21 12:17 ` Pavel Emelyanov
2008-02-21 12:22 ` Patrick McHardy
2008-02-21 12:38 ` [PATCH] Don't limit the number of tunnels with generic name explicitly Pavel Emelyanov
2008-02-21 12:45 ` Patrick McHardy
2008-02-24 4:20 ` David Miller
2008-02-26 7:47 ` Pavel Emelyanov [this message]
2008-02-26 21:31 ` David Miller
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=47C3C420.1060407@openvz.org \
--to=xemul@openvz.org \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=kaber@trash.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).