From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
<netdev@vger.kernel.org>
Subject: [PATCH net 0/3] ipv6: Return an error when adding an already existing tunnel
Date: Mon, 22 Sep 2014 10:07:23 +0200 [thread overview]
Message-ID: <1411373246-22389-1-git-send-email-steffen.klassert@secunet.com> (raw)
The ipv6 tunnel locate functions should not return an existing
tunnel if create is true. Otherwise it is possible to add the
same tunnel multiple times without getting an error.
All our ipv6 tunnels have this bug from the very beginning.
Only the sit tunnel was fixed some years ago with:
commit 8db99e57175 ("sit: Fail to create tunnel, if it already exists").
This patchset fixes the remaining ipv6 tunnels.
next reply other threads:[~2014-09-22 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 8:07 Steffen Klassert [this message]
2014-09-22 8:07 ` [PATCH net 1/3] ip6_tunnel: Return an error when adding an existing tunnel Steffen Klassert
2014-09-22 8:07 ` [PATCH net 2/3] ip6_vti: " Steffen Klassert
2014-09-22 8:07 ` [PATCH net 3/3] ip6_gre: " Steffen Klassert
2014-09-26 4:44 ` [PATCH net 0/3] ipv6: Return an error when adding an already " 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=1411373246-22389-1-git-send-email-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.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