netdev - Re: Bond recovery from BOND_LINK

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: <d55cf81e-0231-0a44-46bf-0c0876f38bc4@redhat.com>
Date:   Fri, 3 Nov 2017 17:46:05 -0400
From:   Jarod Wilson <jarod@...hat.com>
To:     Alex Sidorenko <alexandre.sidorenko@....com>,
        Jay Vosburgh <jay.vosburgh@...onical.com>
Cc:     netdev@...r.kernel.org, Mahesh Bandewar <maheshb@...gle.com>
Subject: Re: Bond recovery from BOND_LINK_FAIL state not working

On 2017-11-03 3:30 PM, Alex Sidorenko wrote:
> Indeed, we do not print slave's ->link_new_state on each entry - so it 
> is quite possible that we are at stage 6.
> 
> It is even possible that this has something to do with how NM initially 
> created bonds.
> Customer says that the problem occurs once only after host reboot, after 
> that
> failover works fine no matter how many times he changes the state of
> VirtualConnect modules.
> 
> Jarod,
> 
> could you please add printing slave->link_new_state for both slaves at each
> entry to bond_miimon_inspect?
> 
> (and instead of nudging slave->new_link like I suggested, use Jay's patch).

Will do, test build is just about ready here.

-- 
Jarod Wilson
jarod@...hat.com