From: Tommi Rantala <tt.rantala@gmail.com>
To: Tommi Rantala <tommi.t.rantala@nokia.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>,
linux-sctp@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Subject: Re: sctp netns "unregister_netdevice: waiting for lo to become free. Usage count = 1"
Date: Thu, 1 Feb 2018 20:02:07 +0200 [thread overview]
Message-ID: <CA+ydwtpiPeFuOB9PyCiOiKhzx69Ecu9mMt2ut=t0F-dwrt40Sg@mail.gmail.com> (raw)
In-Reply-To: <aba6d3c5-4b26-5e61-e4c4-e5925749cd1e@nokia.com>
2018-01-31 19:51 GMT+02:00 Tommi Rantala <tommi.t.rantala@nokia.com>:
> On 31.01.2018 14:31, Neil Horman wrote:
>>
>> On Wed, Jan 31, 2018 at 11:42:24AM +0200, Tommi Rantala wrote:
>>>
>>> I think there's a problem in the dst refcounting in sctp_v4_get_dst()
>>>
>>> There's a dst_entry struct that has >0 refcnt after running the testcase,
>>> which makes it impossible to delete the loopback device, as that dst is
>>> never freed.
>>>
>>> I'll try to make a patch.
>>>
>> Are you looking at the second for loop there, which uses
>> ip_route_output_key,
>> but discards the result if dst is already set? That does look a bit
>> wonky, and
>> the same problem may exist in the ipv6 path. Let me know what the result
>> is.
>
>
> Yes, that was it. Did you receive the email I sent with the patch?
> (I'm not seeing that message e.g. at spinics.net linux-sctp archive, so just
> wondering if that email got lost somehow...)
>
> I'll check the ipv6 case, did not try it yet.
>
> Tommi
As far as I can tell, the ipv6 code does not suffer from this.
The dst handling there looks good to me.
Tommi
next prev parent reply other threads:[~2018-02-01 18:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 15:55 sctp netns "unregister_netdevice: waiting for lo to become free. Usage count = 1" Tommi Rantala
2018-01-30 15:59 ` Neil Horman
2018-01-30 19:24 ` Tommi Rantala
2018-01-30 21:03 ` Neil Horman
2018-01-31 9:42 ` Tommi Rantala
2018-01-31 12:13 ` Tommi Rantala
2018-01-31 12:31 ` Neil Horman
2018-01-31 17:51 ` Tommi Rantala
2018-02-01 18:02 ` Tommi Rantala [this message]
2018-02-01 19:23 ` Neil Horman
2018-02-01 20:41 ` Tommi Rantala
2018-02-02 12:34 ` Neil Horman
2018-02-04 9:05 ` Tommi Rantala
2018-02-01 23:57 ` Alexey Kodanev
2018-02-02 8:27 ` Tommi Rantala
2018-02-02 12:17 ` Alexey Kodanev
2018-01-30 22:52 ` Marcelo Ricardo Leitner
2018-01-31 6:58 ` Tommi Rantala
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='CA+ydwtpiPeFuOB9PyCiOiKhzx69Ecu9mMt2ut=t0F-dwrt40Sg@mail.gmail.com' \
--to=tt.rantala@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=tommi.t.rantala@nokia.com \
--cc=vyasevich@gmail.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).