2020-03-03 16:35:59 +03:00
# SPDX-License-Identifier: GPL-2.0-only
2005-10-18 19:26:15 +04:00
#
# NOTE! Don't add files that are generated in specific
# subdirectories here. Add them in the ".gitignore" file
# in that subdirectory instead.
#
2022-12-29 10:43:09 +03:00
# NOTE! Please use 'git ls-files -i -c --exclude-per-directory=.gitignore'
2008-06-26 11:54:34 +04:00
# command after changing this file, to see if there are
# any tracked files which get ignored after the change.
#
2017-10-30 18:33:45 +03:00
# Normal rules (sorted alphabetically)
2005-10-18 19:26:15 +04:00
#
.*
2017-10-30 18:33:45 +03:00
*.a
2018-03-23 16:04:37 +03:00
*.asn1.[ch]
2017-10-30 18:33:45 +03:00
*.bin
*.bz2
*.c.[012]*.*
2018-09-06 21:26:07 +03:00
*.dt.yaml
2017-10-30 18:33:46 +03:00
*.dtb
2021-01-29 10:24:08 +03:00
*.dtbo
2017-10-30 18:33:46 +03:00
*.dtb.S
2022-11-14 23:59:39 +03:00
*.dtbo.S
2017-10-30 18:33:45 +03:00
*.dwo
*.elf
*.gcno
*.gz
*.i
*.ko
2018-03-23 16:04:30 +03:00
*.lex.c
2017-10-30 18:33:45 +03:00
*.ll
*.lst
*.lz4
*.lzma
*.lzo
kbuild: create *.mod with full directory path and remove MODVERDIR
While descending directories, Kbuild produces objects for modules,
but do not link final *.ko files; it is done in the modpost.
To keep track of modules, Kbuild creates a *.mod file in $(MODVERDIR)
for every module it is building. Some post-processing steps read the
necessary information from *.mod files. This avoids descending into
directories again. This mechanism was introduced in 2003 or so.
Later, commit 551559e13af1 ("kbuild: implement modules.order") added
modules.order. So, we can simply read it out to know all the modules
with directory paths. This is easier than parsing the first line of
*.mod files.
$(MODVERDIR) has a flat directory structure, that is, *.mod files
are named only with base names. This is based on the assumption that
the module name is unique across the tree. This assumption is really
fragile.
Stephen Rothwell reported a race condition caused by a module name
conflict:
https://lkml.org/lkml/2019/5/13/991
In parallel building, two different threads could write to the same
$(MODVERDIR)/*.mod simultaneously.
Non-unique module names are the source of all kind of troubles, hence
commit 3a48a91901c5 ("kbuild: check uniqueness of module names")
introduced a new checker script.
However, it is still fragile in the build system point of view because
this race happens before scripts/modules-check.sh is invoked. If it
happens again, the modpost will emit unclear error messages.
To fix this issue completely, create *.mod with full directory path
so that two threads never attempt to write to the same file.
$(MODVERDIR) is no longer needed.
Since modules with directory paths are listed in modules.order, Kbuild
is still able to find *.mod files without additional descending.
I also killed cmd_secanalysis; scripts/mod/sumversion.c computes MD4 hash
for modules with MODULE_VERSION(). When CONFIG_DEBUG_SECTION_MISMATCH=y,
it occurs not only in the modpost stage, but also during directory
descending, where sumversion.c may parse stale *.mod files. It would emit
'No such file or directory' warning when an object consisting a module is
renamed, or when a single-obj module is turned into a multi-obj module or
vice versa.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Nicolas Pitre <nico@fluxnic.net>
2019-07-17 09:17:57 +03:00
*.mod
2017-10-30 18:33:45 +03:00
*.mod.c
2005-10-18 19:26:15 +04:00
*.o
2007-07-31 11:37:25 +04:00
*.o.*
2017-10-30 18:33:45 +03:00
*.patch
2021-07-03 17:42:57 +03:00
*.rmeta
2022-12-26 21:54:44 +03:00
*.rpm
2021-07-03 17:42:57 +03:00
*.rsi
2005-10-18 19:26:15 +04:00
*.s
2006-01-05 20:10:52 +03:00
*.so
2007-10-19 22:35:02 +04:00
*.so.dbg
2017-10-30 18:33:45 +03:00
*.su
2006-09-16 23:15:44 +04:00
*.symtypes
2020-12-11 21:46:20 +03:00
*.symversions
2018-03-23 16:04:30 +03:00
*.tab.[ch]
2015-04-16 22:49:24 +03:00
*.tar
2011-02-22 12:48:06 +03:00
*.xz
2020-07-30 22:08:40 +03:00
*.zst
2014-04-14 10:56:15 +04:00
Module.symvers
2019-08-19 07:18:07 +03:00
modules.order
2005-10-18 19:26:15 +04:00
#
# Top-level generic files
#
2010-03-13 03:30:23 +03:00
/linux
2021-03-25 21:54:09 +03:00
/modules-only.symvers
2010-03-13 03:30:23 +03:00
/vmlinux
2015-04-24 20:27:40 +03:00
/vmlinux.32
2021-03-05 12:27:07 +03:00
/vmlinux.map
modpost: generate vmlinux.symvers and reuse it for the second modpost
The full build runs modpost twice, first for vmlinux.o and second for
modules.
The first pass dumps all the vmlinux symbols into Module.symvers, but
the second pass parses vmlinux again instead of reusing the dump file,
presumably because it needs to avoid accumulating stale symbols.
Loading symbol info from a dump file is faster than parsing an ELF object.
Besides, modpost deals with various issues to parse vmlinux in the second
pass.
A solution is to make the first pass dumps symbols into a separate file,
vmlinux.symvers. The second pass reads it, and parses module .o files.
The merged symbol information is dumped into Module.symvers in the same
way as before.
This makes further modpost cleanups possible.
Also, it fixes the problem of 'make vmlinux', which previously overwrote
Module.symvers, throwing away module symbols.
I slightly touched scripts/link-vmlinux.sh so that vmlinux is re-linked
when you cross this commit. Otherwise, vmlinux.symvers would not be
generated.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2020-06-01 08:57:11 +03:00
/vmlinux.symvers
2015-02-18 00:47:38 +03:00
/vmlinux-gdb.py
2010-03-13 03:30:23 +03:00
/vmlinuz
/System.map
/Module.markers
2021-04-25 09:24:05 +03:00
/modules.builtin
2019-04-29 19:11:14 +03:00
/modules.builtin.modinfo
2019-10-29 15:38:07 +03:00
/modules.nsdeps
2010-03-13 03:30:23 +03:00
2017-09-30 04:10:10 +03:00
#
# RPM spec file (make rpm-pkg)
#
2023-03-15 18:50:17 +03:00
/rpmbuild/
2017-09-30 04:10:10 +03:00
2011-07-01 03:42:50 +04:00
#
# Debian directory (make deb-pkg)
#
/debian/
scripts/package: snap-pkg target
Following in footsteps of other targets like 'deb-pkg, 'rpm-pkg' and 'tar-pkg',
this patch adds a 'snap-pkg' target for the creation of a Linux kernel snap
package using the kbuild infrastructure.
A snap, in its general form, is a self contained, sandboxed, universal package
and it is intended to work across multiple distributions and/or devices. A snap
package is distributed as a single compressed squashfs filesystem.
A kernel snap is a snap package carrying the Linux kernel, kernel modules,
accessory files (DTBs, System.map, etc) and a manifesto file. The purpose of a
kernel snap is to carry the Linux kernel during the creation of a system image,
eg. Ubuntu Core, and its subsequent upgrades.
For more information on snap packages: https://snapcraft.io/docs/
Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-11-27 14:07:34 +03:00
#
# Snap directory (make snap-pkg)
#
/snap/
2015-02-13 02:01:19 +03:00
#
# tar directory (make tar*-pkg)
#
/tar-install/
2010-03-13 03:30:23 +03:00
#
2019-05-11 06:13:54 +03:00
# We don't want to ignore the following even if they are dot-files
2010-03-13 03:30:23 +03:00
#
2019-05-11 06:13:54 +03:00
!.clang-format
!.cocciconfig
Add .editorconfig file for basic formatting
EditorConfig is a specification to define the most basic code formatting
stuff, and it's supported by many editors and IDEs, either directly or
via plugins, including VSCode/VSCodium, Vim, emacs and more.
It allows to define formatting style related to indentation, charset,
end of lines and trailing whitespaces. It also allows to apply different
formats for different files based on wildcards, so for example it is
possible to apply different configs to *.{c,h}, *.py and *.rs.
In linux project, defining a .editorconfig might help to those people
that work on different projects with different indentation styles, so
they cannot define a global style. Now they will directly see the
correct indentation on every fresh clone of the project.
See https://editorconfig.org
Co-developed-by: Danny Lin <danny@kdrag0n.dev>
Signed-off-by: Danny Lin <danny@kdrag0n.dev>
Signed-off-by: Íñigo Huguet <ihuguet@redhat.com>
Acked-by: Mickaël Salaün <mic@digikod.net>
Reviewed-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Tested-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2023-06-01 10:53:33 +03:00
!.editorconfig
2019-05-11 06:13:54 +03:00
!.get_maintainer.ignore
!.gitattributes
2007-10-16 11:22:21 +04:00
!.gitignore
2023-01-27 17:57:08 +03:00
!.kunitconfig
2008-06-26 11:54:34 +04:00
!.mailmap
2022-08-04 13:54:09 +03:00
!.rustfmt.toml
2005-10-18 19:26:15 +04:00
#
# Generated include files
#
2019-04-29 18:17:53 +03:00
/include/config/
/include/generated/
/arch/*/include/generated/
2005-10-18 19:26:15 +04:00
2006-02-27 06:07:24 +03:00
# stgit generated dirs
patches-*
2006-07-17 09:37:06 +04:00
# quilt's files
patches
series
2006-12-22 12:07:32 +03:00
2021-04-25 09:24:04 +03:00
# ctags files
tags
TAGS
2006-12-22 12:07:32 +03:00
# cscope files
cscope.*
2008-05-22 05:23:10 +04:00
ncscope.*
2007-07-16 10:41:52 +04:00
2009-06-11 13:21:47 +04:00
# gnu global files
GPATH
GRTAGS
GSYMS
GTAGS
2015-04-17 00:02:41 +03:00
# id-utils files
ID
2007-07-16 10:41:52 +04:00
*.orig
2008-03-05 01:28:59 +03:00
*~
\#*#
2012-09-26 13:09:50 +04:00
#
# Leavings from module signing
#
extra_certificates
2015-07-20 23:16:30 +03:00
signing_key.pem
2012-09-26 13:09:50 +04:00
signing_key.priv
signing_key.x509
x509.genkey
2014-02-11 02:25:45 +04:00
# Kconfig presets
2019-05-07 15:48:46 +03:00
/all.config
/alldef.config
/allmod.config
/allno.config
/allrandom.config
/allyes.config
2014-11-25 19:42:54 +03:00
2020-07-02 14:12:00 +03:00
# Kconfig savedefconfig output
/defconfig
2014-11-25 19:42:54 +03:00
# Kdevelop4
*.kdev4
2019-07-24 03:22:33 +03:00
# Clang's compilation database file
/compile_commands.json
2020-09-09 17:10:32 +03:00
# Documentation toolchain
sphinx_*/
2021-07-03 18:26:15 +03:00
# Rust analyzer configuration
/rust-project.json