From: David Miller <davem@davemloft.net>
To: michael@ellerman.id.au
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: Freeing alive fib_info caused by ebc0ffae5
Date: Thu, 04 Nov 2010 12:06:19 -0700 (PDT) [thread overview]
Message-ID: <20101104.120619.226790915.davem@davemloft.net> (raw)
In-Reply-To: <1288870526.30549.19.camel@concordia>
From: Michael Ellerman <michael@ellerman.id.au>
Date: Thu, 04 Nov 2010 22:35:26 +1100
> On Thu, 2010-11-04 at 12:21 +0100, Eric Dumazet wrote:
>> [PATCH] fib: fib_result_assign() should not change fib refcounts
>>
>> After commit ebc0ffae5 (RCU conversion of fib_lookup()),
>> fib_result_assign() should not change fib refcounts anymore.
>>
>> Thanks to Michael who did the bisection and bug report.
...
> Perfect, that fixes it, thanks!
Applied, thanks everyone!
prev parent reply other threads:[~2010-11-04 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 10:23 Freeing alive fib_info caused by ebc0ffae5 Michael Ellerman
2010-11-04 10:30 ` Eric Dumazet
2010-11-04 10:46 ` Eric Dumazet
2010-11-04 11:21 ` Eric Dumazet
2010-11-04 11:23 ` Michael Ellerman
2010-11-04 11:35 ` Michael Ellerman
2010-11-04 19:06 ` 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=20101104.120619.226790915.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=michael@ellerman.id.au \
--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).