linux-kernel - ATI driver conflict with LOCK

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

Message-Id: <E9D727BD-78FC-4D85-9841-34A8F41613BB@gmail.com>
Date:	Thu, 20 Aug 2009 11:04:00 +0800
From:	Bowen <zbw1983@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: ATI driver conflict with LOCK_STAT

Hi All:

	I just found that I can't compile my ATI driver. I have downloaded a  
ATI driver from their web site, but I can't compile it successfully,  
it reported "FATAL: modpost: GPL-incompatible module fglrx.ko uses  
GPL-only symbol
'lock_acquire'",

	I found when I close LOCK_STAT, I can compiled ATI driver  
successfully. And I also try to remove GPL declaration from  
"lock_acquire, lock_release, rcu_lock_map, lockdep_init_map", I can  
also use ATI driver. So does anybody meet same problem? Should we  
remove GPL limitation from those functions in kernel? Or just make  
ATI driver conflict with LOCK_STAT?

Regards
Bowen

--
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/