Changes in Makefile

541b57e3 - selinux: do not include headers from host programs

Fri, 06 Sep 2024 17:29:13 +0000

selinux: do not include headers from host programsThe header, security/selinux/include/classmap.h, is included not onlyfrom kernel space but also from host programs.It includes and , which pull inmore headers. This makes the host programs less portable,specifically causing build errors on macOS.Those headers are included for the following purposes: - for checking CAP_LAST_CAP - for checking PF_MAXThese checks can be guarded by __KERNEL__ so they are skipped whenbuilding host programs. Testing them when building the kernel shouldbe sufficient.The header, security/selinux/include/initial_sid_to_string.h, includes for the NULL definition, but this is not portableeither. Instead, should be included for host programs.Reported-by: Daniel Gomez Closes: https://lore.kernel.org/lkml/20240807-macos-build-support-v1-6-4cd1ded85694@samsung.com/Closes: https://lore.kernel.org/lkml/20240807-macos-build-support-v1-7-4cd1ded85694@samsung.com/Signed-off-by: Masahiro Yamada Signed-off-by: Paul Moore List of files: /linux-6.15/scripts/selinux/mdp/Makefile

faabed29 - kbuild: introduce hostprogs-always-y and userprogs-always-y

Sat, 01 Aug 2020 12:27:18 +0000

kbuild: introduce hostprogs-always-y and userprogs-always-yTo build host programs, you need to add the program names to 'hostprogs'to use the necessary build rule, but it is not enough to build thembecause there is no dependency.There are two types of host programs: built as the prerequisite ofanother (e.g. gen_crc32table in lib/Makefile), or always built whenKbuild visits the Makefile (e.g. genksyms in scripts/genksyms/Makefile).The latter is typical in Makefiles under scripts/, which contains hostprograms globally used during the kernel build. To build them, you needto add them to both 'hostprogs' and 'always-y'.This commit adds hostprogs-always-y as a shorthand.The same applies to user programs. net/bpfilter/Makefile buildsbpfilter_umh on demand, hence always-y is unneeded. In contrast,programs under samples/ are added to both 'userprogs' and 'always-y'so they are always built when Kbuild visits the Makefiles.userprogs-always-y works as a shorthand.Signed-off-by: Masahiro Yamada Acked-by: Miguel Ojeda List of files: /linux-6.15/scripts/selinux/mdp/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/scripts/selinux/mdp/Makefile

ccd19d4c - scripts/selinux: fix build

Tue, 19 Mar 2019 13:21:06 +0000

scripts/selinux: fix buildWe need to add the object tree include directory to the include pathfor building mdp in order to pick up generated/autoconf.h. Otherwise,make O=/path/to/objtree breaks.Fixes: e37c1877ba5b ("scripts/selinux: modernize mdp")Reported-by: Stephen Rothwell Signed-off-by: Stephen Smalley Signed-off-by: Paul Moore List of files: /linux-6.15/scripts/selinux/mdp/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/scripts/selinux/mdp/Makefile

bfc5e3a6 - selinux: use the kernel headers when building scripts/selinux

Wed, 21 Dec 2016 15:39:25 +0000

selinux: use the kernel headers when building scripts/selinuxCommit 3322d0d64f4e ("selinux: keep SELinux in sync with new capabilitydefinitions") added a check on the defined capabilities withoutexplicitly including the capability header file which caused problemswhen building genheaders for users of clang/llvm. Resolve this byusing the kernel headers when building genheaders, which is arguablythe right thing to do regardless, and explicitly including thekernel's capability.h header file in classmap.h. We also update themdp build, even though it wasn't causing an error we really shouldbe using the headers from the kernel we are building.Reported-by: Nicolas Iooss Signed-off-by: Paul Moore List of files: /linux-6.15/scripts/selinux/mdp/Makefile

aa65506f - selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-files

Tue, 17 Jun 2014 21:31:40 +0000

selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-filesFiles added to hostprogs-y are cleaned. (See scripts/Makefile.clean)Adding them to clean-files is redundant.Signed-off-by: Masahiro Yamada Acked-by: Paul Moore Signed-off-by: Paul Moore List of files: /linux-6.15/scripts/selinux/mdp/Makefile

93c06cbb - selinux: add support for installing a dummy policy (v2)

Tue, 26 Aug 2008 19:47:57 +0000

selinux: add support for installing a dummy policy (v2)In August 2006 I posted a patch generating a minimal SELinux policy. Thisweek, David P. Quigley posted an updated version of that as a patch againstthe kernel. It also had nice logic for auto-installing the policy.Following is David's original patch intro (preserved especiallybc it has stats on the generated policies):se interested in the changes there were only two significantchanges. The first is that the iteration through the list of classesused NULL as a sentinel value. The problem with this is that theclass_to_string array actually has NULL entries in its table as placeholders for the user space object classes.The second change was that it would seem at some point the initial sidstable was NULL terminated. This is no longer the case so that iterationhas to be done on array length instead of looking for NULL.Some statistics on the policy that it generates:The policy consists of 523 lines which contain no blank lines. Of those523 lines 453 of them are class, permission, and initial siddefinitions. These lines are usually little to no concern to the policydeveloper since they will not be adding object classes or permissions.Of the remaining 70 lines there is one type, one role, and one userstatement. The remaining lines are broken into three portions. The firstgroup are TE allow rules which make up 29 of the remaining lines, thesecond is assignment of labels to the initial sids which consist of 27lines, and file system labeling statements which are the remaining 11.In addition to the policy.conf generated there is a single file_contextsfile containing two lines which labels the entire system with base_t.This policy generates a policy.23 binary that is 7920 bytes.(then a few versions later...):The new policy is 587 lines (stripped of blank lines) with 476 of thoselines being the boilerplate that I mentioned last time. The remaining111 lines have the 3 lines for type, user, and role, 70 lines for theallow rules (one for each object class including user space objectclasses), 27 lines to assign types to the initial sids, and 11 lines forfile system labeling. The policy binary is 9194 bytes.Changelog: Aug 26: Added Documentation/SELinux.txt Aug 26: Incorporated a set of comments by Stephen Smalley: 1. auto-setup SELINUXTYPE=dummy 2. don't auto-install if selinux is enabled with non-dummy policy 3. don't re-compute policy version 4. /sbin/setfiles not /usr/sbin/setfiles Aug 22: As per JMorris comments, made sure make distclean cleans up the mdp directory. Removed a check for file_contexts which is now created in the same file as the check, making it superfluous.Signed-off-by: Serge Hallyn Signed-off-by: David Quigley Signed-off-by: James Morris List of files: /linux-6.15/scripts/selinux/mdp/Makefile