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>] [day] [month] [year] [list]
Message-ID: <CAHx5RXBCLPEZcrnUNx9GrQhQKtA-c4WSN6+vbAaqk6P4WSvrKA@mail.gmail.com>
Date: Mon, 13 May 2024 15:43:57 +0100
From: Stephen Langstaff <stephenlangstaff1@...il.com>
To: andrew@...n.ch, f.fainelli@...in.com, olteanv@...in.com
Cc: linux-kernel@...r.kernel.org
Subject: drivers/net/dsa/dsa_loop_bdinfo.c build problems

Hi there.

I have come across an issue in the Linux kernel (6.8.7 and others) and
wondered whether I am doing something wrong?

In trying to test the dsa_loop module, I have found that the
dsa_loop_bdinfo module is not built when the following combination of
configuration items is set:

CONFIG_NET_DSA=y
CONFIG_NET_DSA_LOOP=m
CONFIG_FIXED_PHY=y

This combination can easily be obtained using make menuconfig.

It seems that driver/net/Makefile’s inclusion of the dsa directory as
an obj-m precludes the building of dsa_loop_bdinfo.c (which is an
obj-y):

driver/net/Makefile:
…
obj-$(CONFIG_NET_DSA) += dsa/
…

driver/net/dsa/Makefile:
…
ifdef CONFIG_NET_DSA_LOOP
obj-$(CONFIG_FIXED_PHY)         += dsa_loop_bdinfo.o
endif
…

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ