Changes in Makefile

7f7f6f7a - Makefile: remove redundant tool coverage variables

Mon, 06 May 2024 13:35:43 +0000

Makefile: remove redundant tool coverage variablesNow Kbuild provides reasonable defaults for objtool, sanitizers, andprofilers.Remove redundant variables.Note:This commit changes the coverage for some objects: - include arch/mips/vdso/vdso-image.o into UBSAN, GCOV, KCOV - include arch/sparc/vdso/vdso-image-*.o into UBSAN - include arch/sparc/vdso/vma.o into UBSAN - include arch/x86/entry/vdso/extable.o into KASAN, KCSAN, UBSAN, GCOV, KCOV - include arch/x86/entry/vdso/vdso-image-*.o into KASAN, KCSAN, UBSAN, GCOV, KCOV - include arch/x86/entry/vdso/vdso32-setup.o into KASAN, KCSAN, UBSAN, GCOV, KCOV - include arch/x86/entry/vdso/vma.o into GCOV, KCOV - include arch/x86/um/vdso/vma.o into KASAN, GCOV, KCOVI believe these are positive effects because all of them are kernelspace objects.Signed-off-by: Masahiro Yamada Reviewed-by: Kees Cook Tested-by: Roberto Sassu List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

93324e68 - x86: kmsan: disable instrumentation of unsupported code

Thu, 15 Sep 2022 15:04:06 +0000

x86: kmsan: disable instrumentation of unsupported codeInstrumenting some files with KMSAN will result in kernel being unable tolink, boot or crashing at runtime for various reasons (e.g. infiniterecursion caused by instrumentation hooks calling instrumented codeagain).Completely omit KMSAN instrumentation in the following places: - arch/x86/boot and arch/x86/realmode/rm, as KMSAN doesn't work for i386; - arch/x86/entry/vdso, which isn't linked with KMSAN runtime; - three files in arch/x86/kernel - boot problems; - arch/x86/mm/cpu_entry_area.c - recursion.Link: https://lkml.kernel.org/r/20220915150417.722975-33-glider@google.comSigned-off-by: Alexander Potapenko Cc: Alexander Viro Cc: Alexei Starovoitov Cc: Andrey Konovalov Cc: Andrey Konovalov Cc: Andy Lutomirski Cc: Arnd Bergmann Cc: Borislav Petkov Cc: Christoph Hellwig Cc: Christoph Lameter Cc: David Rientjes Cc: Dmitry Vyukov Cc: Eric Biggers Cc: Eric Biggers Cc: Eric Dumazet Cc: Greg Kroah-Hartman Cc: Herbert Xu Cc: Ilya Leoshkevich Cc: Ingo Molnar Cc: Jens Axboe Cc: Joonsoo Kim Cc: Kees Cook Cc: Marco Elver Cc: Mark Rutland Cc: Matthew Wilcox Cc: Michael S. Tsirkin Cc: Pekka Enberg Cc: Peter Zijlstra Cc: Petr Mladek Cc: Stephen Rothwell Cc: Steven Rostedt Cc: Thomas Gleixner Cc: Vasily Gorbik Cc: Vegard Nossum Cc: Vlastimil Babka Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

003602ad - x86/*/Makefile: Use -fno-asynchronous-unwind-tables to suppress .eh_frame sections

Mon, 24 Feb 2020 23:21:28 +0000

x86/*/Makefile: Use -fno-asynchronous-unwind-tables to suppress .eh_frame sectionsWhile discussing a patch to discard .eh_frame from the compressedvmlinux using the linker script, Fangrui Song pointed out [1] that thesesections shouldn't exist in the first place because arch/x86/Makefileuses -fno-asynchronous-unwind-tables.It turns out this is because the Makefiles used to build the compressedkernel redefine KBUILD_CFLAGS, dropping this flag.Add the flag to the Makefile for the compressed kernel, as well as theEFI stub Makefile to fix this.Also add the flag to boot/Makefile and realmode/rm/Makefile so that thekernel's boot code (boot/setup.elf) and realmode trampoline(realmode/rm/realmode.elf) won't be compiled with .eh_frame sections,since their linker scripts also just discard them. [1] https://lore.kernel.org/lkml/20200222185806.ywnqhfqmy67akfsa@google.com/Suggested-by: Fangrui Song Signed-off-by: Arvind Sankar Signed-off-by: Borislav Petkov Reviewed-by: Nathan Chancellor Reviewed-by: Nick Desaulniers Reviewed-by: Kees Cook Tested-by: Nathan Chancellor Link: https://lkml.kernel.org/r/20200224232129.597160-2-nivedita@alum.mit.edu List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

5f2fb52f - kbuild: rename hostprogs-y/always to hostprogs/always-y

Sat, 01 Feb 2020 16:49:24 +0000

kbuild: rename hostprogs-y/always to hostprogs/always-yIn old days, the "host-progs" syntax was used for specifying hostprograms. It was renamed to the current "hostprogs-y" in 2004.It is typically useful in scripts/Makefile because it allows Kbuild toselectively compile host programs based on the kernel configuration.This commit renames like follows: always -> always-y hostprogs-y -> hostprogsSo, scripts/Makefile will look like this: always-$(CONFIG_BUILD_BIN2C) += ... always-$(CONFIG_KALLSYMS) += ... ... hostprogs := $(always-y) $(always-m)I think this makes more sense because a host program is always a hostprogram, irrespective of the kernel configuration. We want to specifywhich ones to compile by CONFIG options, so always-y will be handier.The "always", "hostprogs-y", "hostprogs-m" will be kept for backwardcompatibility for a while.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

40d04110 - x86, kcsan: Enable KCSAN for x86

Thu, 14 Nov 2019 18:03:03 +0000

x86, kcsan: Enable KCSAN for x86This patch enables KCSAN for x86, with updates to build rules to not useKCSAN for several incompatible compilation units.Signed-off-by: Marco Elver Acked-by: Paul E. McKenney Signed-off-by: Paul E. McKenney List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

afa974b7 - kbuild: add real-prereqs shorthand for $(filter-out FORCE,$^)

Thu, 17 Jan 2019 10:02:43 +0000

kbuild: add real-prereqs shorthand for $(filter-out FORCE,$^)In Kbuild, if_changed and friends must have FORCE as a prerequisite.Hence, $(filter-out FORCE,$^) or $(filter-out $(PHONY),$^) is a commonidiom to get the names of all the prerequisites except phony targets.Add real-prereqs as a shorthand.Note:We cannot replace $(filter %.o,$^) in cmd_link_multi-m because $^ mayinclude auto-generated dependencies from the .*.cmd file when a singleobject module is changed into a multi object module. Refer to commit69ea912fda74 ("kbuild: remove unneeded link_multi_deps"). I added somecomment to avoid accidental breakage.Signed-off-by: Masahiro Yamada Acked-by: Rob Herring List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

927185c1 - x86/build: Specify elf_i386 linker emulation explicitly for i386 objects

Fri, 11 Jan 2019 20:10:12 +0000

x86/build: Specify elf_i386 linker emulation explicitly for i386 objectsThe kernel uses the OUTPUT_FORMAT linker script command in it's linkerscripts. Most of the time, the -m option is passed to the linker withcorrect architecture, but sometimes (at least for x86_64) the -m optioncontradicts the OUTPUT_FORMAT directive.Specifically, arch/x86/boot and arch/x86/realmode/rm produce i386 objectfiles, but are linked with the -m elf_x86_64 linker flag when buildingfor x86_64.The GNU linker manpage doesn't explicitly state any tie-breakers between-m and OUTPUT_FORMAT. But with BFD and Gold linkers, OUTPUT_FORMAToverrides the emulation value specified with the -m option.LLVM lld has a different behavior, however. When supplied withcontradicting -m and OUTPUT_FORMAT values it fails with the followingerror message: ld.lld: error: arch/x86/realmode/rm/header.o is incompatible with elf_x86_64Therefore, just add the correct -m after the incorrect one (it overridesit), so the linker invocation looks like this: ld -m elf_x86_64 -z max-page-size=0x200000 -m elf_i386 --emit-relocs -T \ realmode.lds header.o trampoline_64.o stack.o reboot.o -o realmode.elfThis is not a functional change for GNU ld, because (although notexplicitly documented) OUTPUT_FORMAT overrides -m EMULATION.Tested by building x86_64 kernel with GNU gcc/ld toolchain and bootingit in QEMU. [ bp: massage and clarify text. ]Suggested-by: Dmitry Golovin Signed-off-by: George Rimar Signed-off-by: Tri Vo Signed-off-by: Borislav Petkov Tested-by: Tri Vo Tested-by: Nick Desaulniers Cc: "H. Peter Anvin" Cc: Ingo Molnar Cc: Michael Matz Cc: Thomas Gleixner Cc: morbo@google.comCc: ndesaulniers@google.comCc: ruiu@google.comCc: x86-ml Link: https://lkml.kernel.org/r/20190111201012.71210-1-trong@android.com List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

06cbbac0 - x86/build: Don't use $(LINUXINCLUDE) twice

Fri, 25 Nov 2016 12:38:34 +0000

x86/build: Don't use $(LINUXINCLUDE) twiceThe make variable KBUILD_CFLAGS contains $(LINUXINCLUDE). But the buildalready picks up $(LINUXINCLUDE) from scripts/Makefile.lib. The net effectis that the (long) list of include directories is used twice.This is harmless but pointless. So stop using $(LINUXINCLUDE) twice.Signed-off-by: Paul Bolle Cc: Linus Torvalds Cc: Masahiro Yamada Cc: Peter Zijlstra Cc: Thomas Gleixner Link: http://lkml.kernel.org/r/1480077514-2586-1-git-send-email-pebolle@tiscali.nlSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

58ab5e0c - Kbuild: arch: look for generated headers in obtree

Wed, 15 Jun 2016 15:45:46 +0000

Kbuild: arch: look for generated headers in obtreeThere are very few files that need add an -I$(obj) gcc for the preprocessoror the assembler. For C files, we add always these for both the objtree andsrctree, but for the other ones we require the Makefile to add them, andKbuild then adds it for both trees.As a preparation for changing the meaning of the -I$(obj) directive toonly refer to the srctree, this changes the two instances in arch/x86 to usean explictit $(objtree) prefix where needed, otherwise we won't find theheaders any more, as reported by the kbuild 0day builder.arch/x86/realmode/rm/realmode.lds.S:75:20: fatal error: pasyms.h: No such file or directorySigned-off-by: Arnd Bergmann Signed-off-by: Michal Marek List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

be1fb0e8 - kbuild: delete unnecessary "@:"

Thu, 31 Mar 2016 11:14:16 +0000

kbuild: delete unnecessary "@:"Since commit 2aedcd098a94 ('kbuild: suppress annoying "... is up todate." message'), $(call if_changed,...) is evaluated to "@:"when there is nothing to do.We no longer need to add "@:" after $(call if_changed,...) tosuppress "... is up to date." message.Signed-off-by: Masahiro Yamada Signed-off-by: Michal Marek List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

5c9a8750 - kernel: add kcov code coverage

Tue, 22 Mar 2016 21:27:30 +0000

kernel: add kcov code coveragekcov provides code coverage collection for coverage-guided fuzzing(randomized testing). Coverage-guided fuzzing is a testing techniquethat uses coverage feedback to determine new interesting inputs to asystem. A notable user-space example is AFL(http://lcamtuf.coredump.cx/afl/). However, this technique is notwidely used for kernel testing due to missing compiler and kernelsupport.kcov does not aim to collect as much coverage as possible. It aims tocollect more or less stable coverage that is function of syscall inputs.To achieve this goal it does not collect coverage in soft/hardinterrupts and instrumentation of some inherently non-deterministic ornon-interesting parts of kernel is disbled (e.g. scheduler, locking).Currently there is a single coverage collection mode (tracing), but theAPI anticipates additional collection modes. Initially I alsoimplemented a second mode which exposes coverage in a fixed-size hashtable of counters (what Quentin used in his original patch). I'vedropped the second mode for simplicity.This patch adds the necessary support on kernel side. The complimentarycompiler support was added in gcc revision 231296.We've used this support to build syzkaller system call fuzzer, which hasfound 90 kernel bugs in just 2 months: https://github.com/google/syzkaller/wiki/Found-BugsWe've also found 30+ bugs in our internal systems with syzkaller.Another (yet unexplored) direction where kcov coverage would greatlyhelp is more traditional "blob mutation". For example, mounting arandom blob as a filesystem, or receiving a random blob over wire.Why not gcov. Typical fuzzing loop looks as follows: (1) resetcoverage, (2) execute a bit of code, (3) collect coverage, repeat. Atypical coverage can be just a dozen of basic blocks (e.g. an invalidinput). In such context gcov becomes prohibitively expensive asreset/collect coverage steps depend on total number of basicblocks/edges in program (in case of kernel it is about 2M). Cost ofkcov depends only on number of executed basic blocks/edges. On top ofthat, kernel requires per-thread coverage because there are alwaysbackground threads and unrelated processes that also produce coverage.With inlined gcov instrumentation per-thread coverage is not possible.kcov exposes kernel PCs and control flow to user-space which isinsecure. But debugfs should not be mapped as user accessible.Based on a patch by Quentin Casasnovas.[akpm@linux-foundation.org: make task_struct.kcov_mode have type `enum kcov_mode'][akpm@linux-foundation.org: unbreak allmodconfig][akpm@linux-foundation.org: follow x86 Makefile layout standards]Signed-off-by: Dmitry Vyukov Reviewed-by: Kees Cook Cc: syzkaller Cc: Vegard Nossum Cc: Catalin Marinas Cc: Tavis Ormandy Cc: Will Deacon Cc: Quentin Casasnovas Cc: Kostya Serebryany Cc: Eric Dumazet Cc: Alexander Potapenko Cc: Kees Cook Cc: Bjorn Helgaas Cc: Sasha Levin Cc: David Drysdale Cc: Ard Biesheuvel Cc: Andrey Ryabinin Cc: Kirill A. Shutemov Cc: Jiri Slaby Cc: Ingo Molnar Cc: Thomas Gleixner Cc: "H. Peter Anvin" Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

c0dd6716 - objtool: Mark non-standard object files and directories

Mon, 29 Feb 2016 04:22:34 +0000

objtool: Mark non-standard object files and directoriesCode which runs outside the kernel's normal mode of operation often doesunusual things which can cause a static analysis tool like objtool toemit false positive warnings: - boot image - vdso image - relocation - realmode - efi - head - purgatory - modpostSet OBJECT_FILES_NON_STANDARD for their related files and directories,which will tell objtool to skip checking them. It's ok to skip thembecause they don't affect runtime stack traces.Also skip the following code which does the right thing with respect toframe pointers, but is too "special" to be validated by a tool: - entry - mcountAlso skip the test_nx module because it modifies its exception handlingtable at runtime, which objtool can't understand. Fortunately it'sjust a test module so it doesn't matter much.Currently objtool is the only user of OBJECT_FILES_NON_STANDARD, but itmight eventually be useful for other tools.Signed-off-by: Josh Poimboeuf Cc: Andrew Morton Cc: Andy Lutomirski Cc: Arnaldo Carvalho de Melo Cc: Bernd Petrovitsch Cc: Borislav Petkov Cc: Chris J Arges Cc: Jiri Slaby Cc: Linus Torvalds Cc: Michal Marek Cc: Namhyung Kim Cc: Pedro Alves Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: live-patching@vger.kernel.orgLink: http://lkml.kernel.org/r/366c080e3844e8a5b6a0327dc7e8c2b90ca3baeb.1456719558.git.jpoimboe@redhat.comSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

c6d30853 - UBSAN: run-time undefined behavior sanity checker

Wed, 20 Jan 2016 23:00:55 +0000

UBSAN: run-time undefined behavior sanity checkerUBSAN uses compile-time instrumentation to catch undefined behavior(UB). Compiler inserts code that perform certain kinds of checks beforeoperations that could cause UB. If check fails (i.e. UB detected)__ubsan_handle_* function called to print error message.So the most of the work is done by compiler. This patch just implementsubsan handlers printing errors.GCC has this capability since 4.9.x [1] (see -fsanitize=undefinedoption and its suboptions).However GCC 5.x has more checkers implemented [2].Article [3] has a bit more details about UBSAN in the GCC.[1] - https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcc/Debugging-Options.html[2] - https://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html[3] - http://developerblog.redhat.com/2014/10/16/gcc-undefined-behavior-sanitizer-ubsan/Issues which UBSAN has found thus far are:Found bugs: * out-of-bounds access - 97840cb67ff5 ("netfilter: nfnetlink: fix insufficient validation in nfnetlink_bind")undefined shifts: * d48458d4a768 ("jbd2: use a better hash function for the revoke table") * 10632008b9e1 ("clockevents: Prevent shift out of bounds") * 'x << -1' shift in ext4 - http://lkml.kernel.org/r/<5444EF21.8020501@samsung.com> * undefined rol32(0) - http://lkml.kernel.org/r/<1449198241-20654-1-git-send-email-sasha.levin@oracle.com> * undefined dirty_ratelimit calculation - http://lkml.kernel.org/r/<566594E2.3050306@odin.com> * undefined roundown_pow_of_two(0) - http://lkml.kernel.org/r/<1449156616-11474-1-git-send-email-sasha.levin@oracle.com> * [WONTFIX] undefined shift in __bpf_prog_run - http://lkml.kernel.org/r/ WONTFIX here because it should be fixed in bpf program, not in kernel.signed overflows: * 32a8df4e0b33f ("sched: Fix odd values in effective_load() calculations") * mul overflow in ntp - http://lkml.kernel.org/r/<1449175608-1146-1-git-send-email-sasha.levin@oracle.com> * incorrect conversion into rtc_time in rtc_time64_to_tm() - http://lkml.kernel.org/r/<1449187944-11730-1-git-send-email-sasha.levin@oracle.com> * unvalidated timespec in io_getevents() - http://lkml.kernel.org/r/ * [NOTABUG] signed overflow in ktime_add_safe() - http://lkml.kernel.org/r/[akpm@linux-foundation.org: fix unused local warning][akpm@linux-foundation.org: fix __int128 build woes]Signed-off-by: Andrey Ryabinin Cc: Peter Zijlstra Cc: Sasha Levin Cc: Randy Dunlap Cc: Rasmus Villemoes Cc: Jonathan Corbet Cc: Michal Marek Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: Yury Gribov Cc: Dmitry Vyukov Cc: Konstantin Khlebnikov Cc: Kostya Serebryany Cc: Johannes Berg Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

ef7f0d6a - x86_64: add KASan support

Fri, 13 Feb 2015 22:39:25 +0000

x86_64: add KASan supportThis patch adds arch specific code for kernel address sanitizer.16TB of virtual addressed used for shadow memory. It's located in range[ffffec0000000000 - fffffc0000000000] between vmemmap and %esp fixupstacks.At early stage we map whole shadow region with zero page. Latter, afterpages mapped to direct mapping address range we unmap zero pages fromcorresponding shadow (see kasan_map_shadow()) and allocate and map a realshadow memory reusing vmemmap_populate() function.Also replace __pa with __pa_nodebug before shadow initialized. __pa withCONFIG_DEBUG_VIRTUAL=y make external function call (__phys_addr)__phys_addr is instrumented, so __asan_load could be called before shadowarea initialized.Signed-off-by: Andrey Ryabinin Cc: Dmitry Vyukov Cc: Konstantin Serebryany Cc: Dmitry Chernenkov Signed-off-by: Andrey Konovalov Cc: Yuri Gribov Cc: Konstantin Khlebnikov Cc: Sasha Levin Cc: Christoph Lameter Cc: Joonsoo Kim Cc: Dave Hansen Cc: Andi Kleen Cc: Ingo Molnar Cc: Thomas Gleixner Cc: "H. Peter Anvin" Cc: Christoph Lameter Cc: Pekka Enberg Cc: David Rientjes Cc: Jim Davis Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

a9358bc3 - x86/build: Supress realmode.bin is up to date message

Tue, 15 Apr 2014 17:58:13 +0000

x86/build: Supress realmode.bin is up to date messageSupress this unnecessary message during kernel re-build: make[3]: 'arch/x86/realmode/rm/realmode.bin' is up to date.Signed-off-by: Peter Foley Link: http://lkml.kernel.org/r/1397584693-15902-1-git-send-email-pefoley2@pefoley.comSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

1c678da3 - x86: Remove duplication of 16-bit CFLAGS

Wed, 08 Jan 2014 11:21:20 +0000

x86: Remove duplication of 16-bit CFLAGSDefine them once in arch/x86/Makefile instead of twice.Signed-off-by: David Woodhouse Link: http://lkml.kernel.org/r/1389180083-23249-1-git-send-email-David.Woodhouse@intel.comSigned-off-by: H. Peter Anvin List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

8b3b005d - x86, build: Pass in additional -mno-mmx, -mno-sse options

Mon, 09 Dec 2013 23:43:38 +0000

x86, build: Pass in additional -mno-mmx, -mno-sse optionsIn checkin 5551a34e5aea x86-64, build: Always pass in -mno-ssewe unconditionally added -mno-sse to the main build, to keep newercompilers from generating SSE instructions from autovectorization.However, this did not extend to the special environments(arch/x86/boot, arch/x86/boot/compressed, and arch/x86/realmode/rm).Add -mno-sse to the compiler command line for these environments, andadd -mno-mmx to all the environments as well, as we don't want acompiler to generate MMX code either.This patch also removes a $(cc-option) call for -m32, since we havelong since stopped supporting compilers too old for the -m32 option,and in fact hardcode it in other places in the Makefiles.Reported-by: Kevin B. Smith Cc: Sunil K. Pandey Signed-off-by: H. Peter Anvin Cc: H. J. Lu Link: http://lkml.kernel.org/n/tip-j21wzqv790q834n7yc6g80j1@git.kernel.orgCc: # build fix only List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

c889ba80 - x86, relocs: Refactor the relocs tool to merge 32- and 64-bit ELF

Tue, 16 Apr 2013 23:02:58 +0000

x86, relocs: Refactor the relocs tool to merge 32- and 64-bit ELFRefactor the relocs tool so that the same tool can handle 32- and64-bit ELF.Signed-off-by: H. Peter Anvin Cc: Kees Cook Link: http://lkml.kernel.org/r/1365797627-20874-5-git-send-email-keescook@chromium.org List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

17c961f7 - x86, relocs: Build separate 32/64-bit tools

Fri, 12 Apr 2013 20:13:45 +0000

x86, relocs: Build separate 32/64-bit toolsSince the ELF structures and access macros change size based on 32 vs64 bits, build a separate 32-bit relocs tool (for handling realmodeand 32-bit relocations), and a 64-bit relocs tool (for handling 64-bitkernel relocations).Signed-off-by: Kees Cook Link: http://lkml.kernel.org/r/1365797627-20874-5-git-send-email-keescook@chromium.orgSigned-off-by: H. Peter Anvin List of files: /linux-6.15/arch/x86/realmode/rm/Makefile

484d90ee - x86, build: Globally set -fno-pic

Fri, 10 Aug 2012 18:49:06 +0000

x86, build: Globally set -fno-picGCC built with nonstandard options can enable -fpic by default.We never want this for 32-bit kernels and it will break the build.[ hpa: Notably the Android toolchain apparently does this. ]Change-Id: Iaab7d66e598b1c65ac4a4f0229eca2cd3d0d2898Signed-off-by: Andrew Boie Link: http://lkml.kernel.org/r/1344624546-29691-1-git-send-email-andrew.p.boie@intel.comSigned-off-by: H. Peter Anvin List of files: /linux-6.15/arch/x86/realmode/rm/Makefile