netdev - Re: [PATCH net-next] net: fec: Use a proper ID allocation scheme

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20200217.214840.486235315714211732.davem@davemloft.net>
Date:   Mon, 17 Feb 2020 21:48:40 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     festevam@...il.com
Cc:     fugang.duan@....com, netdev@...r.kernel.org, andrew@...n.ch
Subject: Re: [PATCH net-next] net: fec: Use a proper ID allocation scheme

From: Fabio Estevam <festevam@...il.com>
Date: Mon, 17 Feb 2020 19:36:51 -0300

> Instead of using such poor mechanism for counting the network interfaces
> IDs, use a proper allocation scheme, such as IDR.
> 
> This fixes the network behavior after unbind/bind.

What about:

1) unbind fec0
2) unbind fec1
3) bind fec0

It doesn't work even with the IDR scheme.