netdev - Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e9cbd091-bb51-6f30-f31b-9080145caa93@cumulusnetworks.com>
Date:   Thu, 13 Apr 2017 08:36:38 -0600
From:   David Ahern <dsa@...ulusnetworks.com>
To:     Robert Shearman <rshearma@...cade.com>, davem@...emloft.net
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

On 4/13/17 6:48 AM, Robert Shearman wrote:
>> the patches look ok to me, but in testing them I see I refcnt problem.
>> simple reproducer:
>>
>> ip li add red type vrf table 254
>> ip link set dev eth1 vrf red
>> ip addr add 127.0.0.1/8 dev red
>> ip link set dev eth1 up
>> ip li set red up
>> ping -c1 -w1 -I red 127.0.0.1
>> ip li del red
>> --> hangs with 'uregister_netdevice: waiting for red to become free.'
> 
> Right, I've reproduced the same and it occurs even without using the
> main table and I believe it has been introduced within the last week.

The cached dst on sockets is one known place that causes a hang on a
delete. Basically the delete stalls until the sockets are closed. I have
a patch for sk_rx_dst which is the one I chased down last week.
sk_dst_cache is another possibility.

Neither of those should be at play with the above example because the
ping command runs and then exits.