netdev - Re: [PATCH iproute2] man/tc-mirred: don't recommend modprobe

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] [day] [month] [year] [list]

Message-ID: <20240112104207.120c0993@hermes.local>
Date: Fri, 12 Jan 2024 10:42:07 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] man/tc-mirred: don't recommend modprobe

On Fri, 12 Jan 2024 19:21:34 +0100
Jiri Pirko <jiri@...nulli.us> wrote:

> >> 
> >> You can't add "ifb0" like this, it is created implicitly on module probe
> >> time. Pick a different name.  
> >
> >Right.
> >Looks like ifb is behaving differently than other devices.
> >For example, doing modprobe of dummy creates no device.  
> 
> Older drivers did do this. Bonding modprobe also created bond0 in
> the past. Now it does not. I guess ifb behaviour could be changed as
> well.

In most distros, for bond and dummy, there is this from systemd.conf


options bonding max_bonds=0
options dummy numdummies=0