From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: netdev@vger.kernel.org, lkundrak@v3.sk
Subject: Re: [PATCH net] ipv6: replacing a rt6_info needs to purge possible propagated rt6_infos too
Date: Tue, 27 Jan 2015 00:23:03 -0800 (PST) [thread overview]
Message-ID: <20150127.002303.21930811137608230.davem@davemloft.net> (raw)
In-Reply-To: <131075b1c8770c414675094c292d394316e8cd17.1422281427.git.hannes@stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Mon, 26 Jan 2015 15:11:17 +0100
> Lubomir Rintel reported that during replacing a route the interface
> reference counter isn't correctly decremented.
...
> During replacement of a rt6_info we must walk all parent nodes and check
> if the to be replaced rt6_info got propagated. If so, replace it with
> an alive one.
>
> Reported-by: Lubomir Rintel <lkundrak@v3.sk>
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2015-01-27 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 14:11 [PATCH net] ipv6: replacing a rt6_info needs to purge possible propagated rt6_infos too Hannes Frederic Sowa
2015-01-26 15:36 ` Lubomir Rintel
2015-01-26 16:02 ` Eric Dumazet
2015-01-26 16:08 ` Hannes Frederic Sowa
2015-01-27 8:23 ` 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=20150127.002303.21930811137608230.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=lkundrak@v3.sk \
--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