linux-toradex.git/scripts/mod/modpost.c, branch tegra-10.9.9

Fix all -Wmissing-prototypes warnings in x86 defconfig

2009-09-23T14:39:28+00:00

Signed-off-by: Trevor Keith 
Cc: Sam Ravnborg 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kbuild: add hint about __refdata to modpost

2009-06-09T20:37:53+00:00

As requested by Guennadi Liakhovetski

Cc: Guennadi Liakhovetski 
Signed-off-by: Sam Ravnborg

initconst adjustments

2009-06-09T20:37:43+00:00

- add .init.rodata to INIT_DATA, and group all initconst flavors
  together
- move strings generated from __setup_param() into .init.rodata
- add .*init.rodata to modpost's sets of init sections
- make modpost warn about references between meminit and cpuinit
  as well as memexit and cpuexit sections (as CPU and memory
  hotplug are independently selectable features)

Signed-off-by: Jan Beulich 
Signed-off-by: Sam Ravnborg

kbuild, modpost: fix unexpected non-allocatable warning with mips

2009-05-04T11:05:26+00:00

mips emit the following debug sections:
.mdebug* and .pdr

They were included in the check for non-allocatable section
and caused modpost to warn.

Manuel Lauss suggested to fix this by adding the relevant
sections to the list of sections we do not check.

Signed-off-by: Sam Ravnborg 
Reported-by: Manuel Lauss

kbuild, modpost: fix "unexpected non-allocatable" warning with SUSE gcc

2009-05-04T11:05:06+00:00

Jean reported that he saw one warning for each module like the one below:
WARNING: arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.o (.comment.SUSE.OPTs): unexpected non-allocatable section.

The warning appeared with the improved version of the
check of the flags in the sections.

That check already ignored sections named ".comment" - but SUSE store
additional info in the comment section and has named it in a SUSE
specific way. Therefore modpost failed to ignore the section.

The fix is to extend the pattern so we ignore all sections
that start with the name ".comment.".

Signed-off-by: Sam Ravnborg 
Reported-by: Jean Delvare 
Tested-by: Jean Delvare

kbuild, modpost: fix unexpected non-allocatable section when cross compiling

2009-05-04T11:05:03+00:00

The missing TO_NATIVE(sechdrs[i].sh_flags) was causing many
unexpected non-allocatable section warnings when cross-compiling
for an architecture with a different endianness.

Fix endianness of all the fields in the ELF header and
section headers, not just some of them so we are not
hit by this anohter time.

Signed-off-by: Anders Kaseorg 
Reported-by: Sean MacLennan 
Tested-by: Sean MacLennan 
Signed-off-by: Sam Ravnborg

kbuild, modpost: Check the section flags, to catch missing "ax"/"aw"

2009-05-01T08:54:05+00:00

When you put
  .section ".foo"
in an assembly file instead of
  .section "foo", "ax"
, one of the possible symptoms is that modpost will see an
ld-generated section name ".foo.1" in section_rel() or section_rela().
But this heuristic has two problems: it will miss a bad section that
has no relocations, and it will incorrectly flag many gcc-generated
sections as bad when compiling with -ffunction-sections
-fdata-sections.

On mips it fixes a lot of bogus warnings with gcc 4.4.0 lije this one:
WARNING: crypto/cryptd.o (.text.T.349): unexpected section name.

So instead of checking whether the section name matches a particular
pattern, we directly check for a missing SHF_ALLOC in the section
flags.

Signed-off-by: Anders Kaseorg 
Tested-by: Ralf Baechle 
Signed-off-by: Sam Ravnborg

kbuild: fix comment in modpost.c

2009-05-01T08:54:04+00:00

There is some confusion on naming of the head section.
Correct naming is .head.text.

Fix comment so we use correct naming.

Signed-off-by: Sam Ravnborg

kbuild: fix Module.markers permission error under cygwin

2009-05-01T08:54:03+00:00

While building the kernel, we end-up calling modpost with -K and -M
options for the same file (Modules.markers).  This is resulting in
modpost's main function calling read_markers() and then write_markers() on
the same file.

We then have read_markers() mmap'ing the file, and writer_markers()
opening that same file for writing.

The issue is that read_markers() exits without munmap'ing the file and is
as a matter holding a reference on Modules.markers.  When write_markers()
is opening that very same file for writing, we still have a reference on
it and cygwin (Windows?) is then making fopen() fail with EPERM.

Calling release_file() before exiting read_markers() clears that reference
(and memory leak) and fopen() then succeeds.

Tested on both cygwin (1.3.22) and Linux.  Also ran modpost within
valgrind on Linux to make sure that the munmap'ed file was not accessed
after read_markers()

Signed-off-by: Cedric Hombourger 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Sam Ravnborg

Remove unused support code for refok sections.

2009-04-28T02:51:58+00:00

The old refok sections

  .text.init.refok
  .data.init.refok
  .exit.text.refok

have been deprecated since commit
312b1485fb509c9bc32eda28ad29537896658cb8.  After the other patches in
this patch series nothing is put in these sections, so clean things up
by eliminating all the remaining references to them.

Signed-off-by: Tim Abbott 
Acked-by: Sam Ravnborg 
Signed-off-by: Linus Torvalds