netdev - Re: Regression: Bug 196547 - Since 4.12 - bonding module not working with wireless drivers

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]

Date:   Wed, 16 Aug 2017 19:42:03 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dcbw@...hat.com
Cc:     james@...ealm.net, futur.andy@...glemail.com, kvalo@...eaurora.org,
        arend.vanspriel@...adcom.com, maheshb@...gle.com,
        andy@...yhouse.net, netdev@...r.kernel.org,
        linux-wireless@...r.kernel.org, greearb@...delatech.com
Subject: Re: Regression: Bug 196547 - Since 4.12 - bonding module not
 working with wireless drivers

From: Dan Williams <dcbw@...hat.com>
Date: Wed, 16 Aug 2017 21:11:47 -0500

> You'll probably say "aim for the 75% case" or something like that,
> which is fine, but then you're depending on your 75% case to be (a)
> single AP, (b) never move (eg, only bond wifi + ethernet), (c) little
> radio interference.  I'm not sure I'd buy that.  If I've put words in
> your mouth, forgive me.

You can interpret what I'm saying as "some reasonable value is
better than no value at all."

You can keep arguing about AP changes, radio interference, etc.
but anything is better than the current situation.

Start small and simple, try to handle everything over time and
gradually.