linux-kernel - Re: section mismatch with a platform driver

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]

Date:	Mon, 13 Oct 2008 11:51:11 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Neshama Parhoti <pneshama@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: section mismatch with a platform driver

On Mon, Oct 13, 2008 at 10:19:05AM +0200, Neshama Parhoti wrote:
> Hi all,
> 
> I am working on a platform driver, and getting the following warning:
> 
> WARNING: vmlinux.o(.data+0x44bc4): Section mismatch: reference to
> .init.text:my_probe_func (between 'my_platform_struct' and
> 'debug_level_variable')
> 
> If I understand correctly, it shouts about my probe function being
> referenced from the data section:
> 
> static struct platform_driver my_platform_struct = {
> 	.probe		= my_probe,
> 	.remove		= my_remove,
> 	.suspend	= my_suspend,
> 	.resume		= my_resume,
> 	.driver		= {
> 		.name = DRIVER_NAME,
> 	},
> };
> 
> Why is that a problem ? Should I do something different ? Isn't my
> platform_driver struct completely standard ?

It complains about "my_probe_func", and that's not even in the code
you posted.

Please send the complete file.

> Thank You !
> Pnesh

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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