netdev - Re: [PATCH net] net/mlx5e: limit log messages due to (ovs) probing to

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: <CAJ3xEMibkDZmLYokvHinjiuv3V_ZA7x3s4SBpXbp2_BDpTUjgA@mail.gmail.com>
Date:   Mon, 13 Apr 2020 09:35:54 +0300
From:   Or Gerlitz <gerlitz.or@...il.com>
To:     Roi Dayan <roid@...lanox.com>, Saeed Mahameed <saeedm@...lanox.com>
Cc:     "marcelo.leitner@...il.com" <marcelo.leitner@...il.com>,
        Vlad Buslov <vladbu@...lanox.com>,
        Oz Shlomo <ozsh@...lanox.com>,
        Paul Blakey <paulb@...lanox.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Leon Romanovsky <leonro@...lanox.com>
Subject: Re: [PATCH net] net/mlx5e: limit log messages due to (ovs) probing to _once

On Sun, Apr 12, 2020 at 11:15 AM Roi Dayan <roid@...lanox.com> wrote:

[..]

> in some places we already only use extack without netdev_warn.
> so currently in favor in removing the other logs if extack error exists to
> avoid flooding the log

+1 for using the modern messaging way (extack)
+1 for driver diet by avoiding double messaging systems