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: <CAJ3xEMjX22Qju2JSN0wGd067JarPM+C3v4TFJu3Y8LzhtUHxcQ@mail.gmail.com>
Date:   Wed, 3 Oct 2018 20:23:10 +0300
From:   Or Gerlitz <gerlitz.or@...il.com>
To:     Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc:     David Miller <davem@...emloft.net>,
        anirudh.venkataramanan@...el.com,
        Linux Netdev List <netdev@...r.kernel.org>,
        nhorman@...hat.com, sassmann@...hat.com
Subject: Re: [net-next 08/15] ice: Notify VF of link status change

On Wed, Oct 3, 2018 at 6:46 PM Jeff Kirsher <jeffrey.t.kirsher@...el.com> wrote:
> From: Anirudh Venkataramanan <anirudh.venkataramanan@...el.com>
>
> When PF gets a link status change event, notify the VFs of the same.

so you always want to block east/west traffic when the uplink is down? why?

The correct approach is to have vf/vport e-switch representor on the
host, and if
the host admin puts down the administrative link of the rep -- the vf
operational link (carrier)
goes down.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ