From: David Miller <davem@davemloft.net>
To: nicolas.dichtel@dev.6wind.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC][PATCH] xfrm6 refcnt problem in bundle creation
Date: Wed, 21 Apr 2010 16:25:53 -0700 (PDT) [thread overview]
Message-ID: <20100421.162553.91324239.davem@davemloft.net> (raw)
In-Reply-To: <4BC73FB7.9090106@dev.6wind.com>
From: Nicolas Dichtel <nicolas.dichtel@dev.6wind.com>
Date: Thu, 15 Apr 2010 18:32:55 +0200
> Subject: [PATCH] xfrm6: ensure to use the same dev when building a bundle
>
> When building a bundle, we set dst.dev and rt6.rt6i_idev.
> We must ensure to set the same device for both fields.
>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
What we are doing now is definitely wrong and I think your
patch is the correct fix.
Applied to net-2.6, thanks!
prev parent reply other threads:[~2010-04-21 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 16:32 [RFC][PATCH] xfrm6 refcnt problem in bundle creation Nicolas Dichtel
2010-04-21 23:25 ` David Miller [this message]
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=20100421.162553.91324239.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@dev.6wind.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;
as well as URLs for NNTP newsgroup(s).