linux-kernel - Re: [lkp] [net] 041de4d656: bcm_phy_lib: module license 'unspecified' taints kernel.

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: <561D5A92.2030800@broadcom.com>
Date:	Tue, 13 Oct 2015 12:25:06 -0700
From:	Arun Parameswaran <aparames@...adcom.com>
To:	kernel test robot <ying.huang@...ux.intel.com>,
	Arun Parameswaran <arunp@...adcom.com>
CC:	<lkp@...org>, LKML <linux-kernel@...r.kernel.org>,
	0day robot <fengguang.wu@...el.com>
Subject: Re: [lkp] [net] 041de4d656: bcm_phy_lib: module license 'unspecified'
 taints kernel.



On 15-10-11 11:17 PM, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> git://internal_mailing_list_patch_tree Arun-Parameswaran/Add-support-for-Broadcom-s-iProc-MDIO-and-Cygnus-Ethernet-PHY
> commit 041de4d6564535f639f0d4cec6712b5adf62723f ("net: phy: Add Broadcom phy library for common interfaces")
>
> Found new message as below in kernel log after the commit.
>
> [    2.527336] bcm_phy_lib: module license 'unspecified' taints kernel.
> [    2.527686] Disabling lock debugging due to kernel taint

Will fix this with a separate patch.

>
> To reproduce:
>
>         git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>         cd lkp-tests
>         bin/lkp install job.yaml  # job file is attached in this email
>         bin/lkp run     job.yaml
>
>
>
> Thanks,
> Ying Huang

Thanks,

Arun

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/