linux-kernel - Re: [PATCH net-next 0/7] bonding: clean up and standarize logging printks

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: <20190609.133622.727594888423105130.davem@davemloft.net>
Date:   Sun, 09 Jun 2019 13:36:22 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     jarod@...hat.com
Cc:     linux-kernel@...r.kernel.org, joe@...ches.com,
        j.vosburgh@...il.com, vfalico@...il.com, andy@...yhouse.net,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/7] bonding: clean up and standarize logging
 printks

From: Jarod Wilson <jarod@...hat.com>
Date: Fri,  7 Jun 2019 10:59:25 -0400

> This set improves a few somewhat terse bonding debug messages, fixes some
> errors in others, and then standarizes the majority of them, using new
> slave_* printk macros that wrap around netdev_* to ensure both master
> and slave information is provided consistently, where relevant. This set
> proves very useful in debugging issues on hosts with multiple bonds.
> 
> I've run an array of LNST tests over this set, creating and destroying
> quite a few different bonds of the course of testing, fixed the little
> gotchas here and there, and everything looks stable and reasonable to me,
> but I can't guarantee I've tested every possible message and scenario to
> catch every possible "slave could be NULL" case.

Series applied, thanks.