On Fri, Jun 05, 2020 at 02:12:54AM +0530, Syed Nayyar Waris wrote: > On Sun, May 31, 2020 at 12:50 AM kbuild test robot <[email protected]> wrote:
> > >> WARNING: modpost: lib/test_bitmap.o(.data+0xe80): Section mismatch in > > >> reference from the variable clump_test_data to the variable > > >> .init.rodata:clump_exp1 > > The variable clump_test_data references > > the variable __initconst clump_exp1 > > If the reference is valid then annotate the > > variable with or __refdata (see linux/init.h) or name the variable: > > > > -- > > >> WARNING: modpost: lib/test_bitmap.o(.data+0xec8): Section mismatch in > > >> reference from the variable clump_test_data to the variable > > >> .init.rodata:clump_exp2 > > The variable clump_test_data references > > the variable __initconst clump_exp2 > > If the reference is valid then annotate the > > variable with or __refdata (see linux/init.h) or name the variable: > > > > -- > > >> WARNING: modpost: lib/test_bitmap.o(.data+0xf10): Section mismatch in > > >> reference from the variable clump_test_data to the variable > > >> .init.rodata:clump_exp3 > > The variable clump_test_data references > > the variable __initconst clump_exp3 > > If the reference is valid then annotate the > > variable with or __refdata (see linux/init.h) or name the variable: > > > > -- > > >> WARNING: modpost: lib/test_bitmap.o(.data+0xf58): Section mismatch in > > >> reference from the variable clump_test_data to the variable > > >> .init.rodata:clump_exp4 > > The variable clump_test_data references > > the variable __initconst clump_exp4 > > If the reference is valid then annotate the > > variable with or __refdata (see linux/init.h) or name the variable: > I am unable to reproduce the compilation warning. You have to enable section mismatch checker. > I ran the command: > make W=1 C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' lib/ > > But the compilation warning didn't show up. Can anyone please point to me > what I am doing wrong here? How shall I reproduce the warning? Thanks ! You put some data into init section of the object, while you are trying to access it from non-init one. It's easy-to-fix issue. -- With Best Regards, Andy Shevchenko
