* [cryptodev:master 43/49] WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq()
@ 2016-04-15 19:52 kbuild test robot
2016-04-15 20:39 ` Tadeusz Struk
0 siblings, 1 reply; 2+ messages in thread
From: kbuild test robot @ 2016-04-15 19:52 UTC (permalink / raw)
To: Tadeusz Struk; +Cc: kbuild-all, linux-crypto, Herbert Xu
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
head: 5f575efea79caae69b81f922d99b221302a2c003
commit: d6064165ba4449ea085a389724d728258a3180ec [43/49] crypto: qat - adf_dev_stop should not be called in atomic context
config: i386-allmodconfig (attached as .config)
reproduce:
git checkout d6064165ba4449ea085a389724d728258a3180ec
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>> WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq()
The function __init init_module() references
a function __exit adf_exit_vf_wq().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
adf_exit_vf_wq() so it may be used outside an exit section.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 54438 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [cryptodev:master 43/49] WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq()
2016-04-15 19:52 [cryptodev:master 43/49] WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq() kbuild test robot
@ 2016-04-15 20:39 ` Tadeusz Struk
0 siblings, 0 replies; 2+ messages in thread
From: Tadeusz Struk @ 2016-04-15 20:39 UTC (permalink / raw)
To: kbuild test robot; +Cc: kbuild-all, linux-crypto, Herbert Xu
On 04/15/2016 12:52 PM, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
> head: 5f575efea79caae69b81f922d99b221302a2c003
> commit: d6064165ba4449ea085a389724d728258a3180ec [43/49] crypto: qat - adf_dev_stop should not be called in atomic context
> config: i386-allmodconfig (attached as .config)
> reproduce:
> git checkout d6064165ba4449ea085a389724d728258a3180ec
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All warnings (new ones prefixed by >>):
>
>>> WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq()
> The function __init init_module() references
> a function __exit adf_exit_vf_wq().
> This is often seen when error handling in the init function
> uses functionality in the exit path.
> The fix is often to remove the __exit annotation of
> adf_exit_vf_wq() so it may be used outside an exit section.
>
Is it still complaining even after this?
https://patchwork.kernel.org/patch/8854461/
Thanks,
--
TS
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-04-15 20:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-15 19:52 [cryptodev:master 43/49] WARNING: drivers/crypto/qat/qat_common/intel_qat.o(.init.text+0x30d): Section mismatch in reference from the function init_module() to the function .exit.text:adf_exit_vf_wq() kbuild test robot
2016-04-15 20:39 ` Tadeusz Struk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).