Compare commits

...

1872 Commits

Author SHA1 Message Date
David Abdurachmanov 05547aa707
New riscv64 for kernels 5.14/5.15
Signed-off-by: David Abdurachmanov <david.abdurachmanov@gmail.com>
2021-11-08 13:07:13 +02:00
Justin M. Forbes e7357cfc20 Merge branch 'gcov' into 'os-build'
Fix dist-srpm-gcov

See merge request cki-project/kernel-ark!1430
2021-10-14 12:28:05 +00:00
Justin M. Forbes 90f7166fb7 Merge branch 'config-ark-ntb' into 'os-build'
redhat: configs: add CONFIG_NTB and related items

See merge request cki-project/kernel-ark!1428
2021-10-14 11:33:43 +00:00
Justin M. Forbes 1999a606df Merge branch 'kfencefilter' into 'os-build'
Add kfence_test to mod-internal.list

See merge request cki-project/kernel-ark!1429
2021-10-14 11:32:12 +00:00
Fedora Kernel Team 92d22de6b0 [redhat] kernel-5.15.0-0.rc5.20211014git348949d9a444.42
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-14 11:19:24 +00:00
Fedora Kernel Team 4110ca97d7 Merge 'master' into 'os-build' 2021-10-14 10:19:14 +00:00
Don Zickus 528777da30 Fix dist-srpm-gcov
make dist-srpm-gcov failed to do the expected thing.  It appears changes
from commit 2d525ab424 forced a second run of dist-sources.  This
second run regenerated the kernel.spec without the gcov pieces because
the env variables were not defined.

Fix this by setting the BUILDOPTS variable to global for the target.
Then simplify the target by leveraging the dist-srpm target.

Now dist-srpm-gcov just sets BUILDID and BUILDOPTS and then calls
dist-srpm to do the expected thing.

Tested by running 'make dist-srpm-gcov' and checking the resulting
redhat/rpm/SOURCES/kernel.spec file for the '_with_gcov 1' definition.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-10-13 17:09:02 -04:00
Fedora Kernel Team 2cebfeda0c [redhat] kernel-5.15.0-0.rc5.20211013gitf4d0cc426f77.41
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-13 11:20:37 +00:00
Fedora Kernel Team a638b203ec Merge 'master' into 'os-build' 2021-10-13 10:19:15 +00:00
Justin M. Forbes f8b6e0ba9d
Add kfence_test to mod-internal.list
MR 1422 enabled a number of kunit tests in the config including
CONFIG_KFENCE_KUNIT_TEST, but this test does not build in  RHEL configs
because KFENCE itself it turned off. As a result, the module for the
test was not added to mod-internal.list causing depmod to fail on Fedora
builds.  This simply adds the module to the internal list so that it
filters properly.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-10-12 20:57:07 -05:00
Fedora Kernel Team 4c25305f00 [redhat] kernel-5.15.0-0.rc5.20211012gitfa5878760579.40
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-12 11:22:52 +00:00
Fedora Kernel Team 8436849dda Merge 'master' into 'os-build' 2021-10-12 10:23:33 +00:00
Justin M. Forbes 156e2b8df5 Merge branch 'configs/2021-09-27/arch/powerpc' into 'os-build'
[redhat] New configs in arch/powerpc

See merge request cki-project/kernel-ark!1398
2021-10-11 19:42:24 +00:00
CKI Gitlab 7bf0838a16 [redhat] New configs in arch/powerpc 2021-10-11 19:42:23 +00:00
Justin M. Forbes 5f4f27bdca Merge branch 'configs/2021-09-27/drivers/vhost' into 'os-build'
[redhat] New configs in drivers/vhost

See merge request cki-project/kernel-ark!1405
2021-10-11 19:40:53 +00:00
John W. Linville a323a73dac redhat: configs: add CONFIG_NTB and related items
Signed-off-by: John W. Linville <linville@redhat.com>
2021-10-11 14:09:09 -04:00
Justin M. Forbes e5dfcc2a9f Merge branch 'kunit-ark' into 'os-build'
Enable KUNIT tests for redhat kernel-modules-internal

See merge request cki-project/kernel-ark!1422
2021-10-11 18:06:56 +00:00
Justin M. Forbes e6569aea97 Merge branch 'matched-rpminspect' into 'os-build'
redhat: add *-matched meta packages to rpminspect emptyrpm config

See merge request cki-project/kernel-ark!1418
2021-10-11 15:30:21 +00:00
Justin M. Forbes 3a60f10028 Merge branch 'nodes' into 'os-build'
aarch64: Use common config for NODES_SHIFT

See merge request cki-project/kernel-ark!1333
2021-10-11 15:22:58 +00:00
Fedora Kernel Team 5ced9b3eff [redhat] kernel-5.15.0-0.rc5.39
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-11 11:22:56 +00:00
Fedora Kernel Team 8aedb03f2d Merge 'master' into 'os-build' 2021-10-11 10:21:15 +00:00
Justin M. Forbes ca501d8102 Merge branch 'configs/2021-09-02/drivers/dma-buf' into 'os-build'
[redhat] New configs in drivers/dma-buf

See merge request cki-project/kernel-ark!1355
2021-10-10 14:12:28 +00:00
Fedora Kernel Team 04a5d00e96 [redhat] kernel-5.15.0-0.rc4.20211010git7fd2bf83d59a.38
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-10 11:23:10 +00:00
Fedora Kernel Team c2fb224a6b Merge 'master' into 'os-build' 2021-10-10 10:24:16 +00:00
Fedora Kernel Team 6e6daa6ab2 [redhat] kernel-5.15.0-0.rc4.20211009git5d6ab0bb408f.37
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-09 11:21:53 +00:00
Fedora Kernel Team 2ec0d451f0 Merge 'master' into 'os-build' 2021-10-09 10:21:11 +00:00
Justin M. Forbes 7395733e33 Merge branch 'centos-sync-typo' into 'os-build'
redhat: fix typo and make the output more silent for dist-git sync

See merge request cki-project/kernel-ark!1417
2021-10-08 22:01:24 +00:00
Justin M. Forbes e4a190b34b Merge branch 'configs/2021-08-31/arch/x86' into 'os-build'
[redhat] New configs in arch/x86

See merge request cki-project/kernel-ark!1336
2021-10-08 11:41:52 +00:00
Fedora Kernel Team 5aaa7ee03a [redhat] kernel-5.15.0-0.rc4.20211008git1da38549dd64.36
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-08 11:21:24 +00:00
Fedora Kernel Team f54776cf8a Merge 'master' into 'os-build' 2021-10-08 10:21:24 +00:00
Mark Salter eac34cdcbc
Use common config for NODES_SHIFT
ARK is currently has CONFIG_NODES_SHIFT=6 where Fedora is set
to 9. Let's simplify things and share the Fedora config with
ARK.

Signed-off-by: Mark Salter <msalter@redhat.com>
2021-10-07 16:34:07 -05:00
Justin M. Forbes 838b5282f5 Merge branch 'configs/2021-08-31/crypto/Kconfig' into 'os-build'
[redhat] New configs in crypto/Kconfig

See merge request cki-project/kernel-ark!1338
2021-10-07 18:32:46 +00:00
Fedora Kernel Team f8c785df1e [redhat] kernel-5.15.0-0.rc4.20211007git5af4055fa813.35
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-07 11:22:18 +00:00
Fedora Kernel Team 4f03cbc20b Merge 'master' into 'os-build' 2021-10-07 10:21:11 +00:00
Justin M. Forbes 100efebed3
Fedora NTFS config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-10-06 11:38:50 -05:00
Justin M. Forbes c22c7793a5
Fedora 5.15 configs part 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-10-06 11:33:03 -05:00
Fedora Kernel Team 45c783db15 [redhat] kernel-5.15.0-0.rc4.20211006git60a9483534ed.34
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-06 11:22:33 +00:00
Fedora Kernel Team c5ce342fa6 Merge 'master' into 'os-build' 2021-10-06 10:22:37 +00:00
Justin M. Forbes 5c947920ff Revert "Merge branch 'ppcbpfselftest' into 'os-build'"
This reverts merge request !1416
2021-10-05 18:07:30 +00:00
Nico Pache 39f7bd1ed4 Enable KUNIT tests for redhat kernel-modules-internal
This commit will enable KUNIT tests to be compiled as modules and
packaged into the kernel-modules-internal package.

Signed-off-by: Nico Pache <npache@redhat.com>
2021-10-05 14:00:23 -04:00
Fedora Kernel Team 783160572f [redhat] kernel-5.15.0-0.rc4.20211005gitf6274b06e326.33
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-05 11:23:00 +00:00
Fedora Kernel Team 561e7b411c Merge 'master' into 'os-build' 2021-10-05 10:20:08 +00:00
Justin M. Forbes 64e917b8db Merge branch 'includefiles' into 'os-build'
Fix ordering in genspec args

See merge request cki-project/kernel-ark!1421
2021-10-04 15:09:01 +00:00
Fedora Kernel Team db50d41a8e [redhat] kernel-5.15.0-0.rc4.32
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-04 11:24:22 +00:00
Fedora Kernel Team 2688861203 Merge 'master' into 'os-build' 2021-10-04 10:22:19 +00:00
Fedora Kernel Team a92c17dd5b [redhat] kernel-5.15.0-0.rc3.20211003git7b66f4393ad4.31
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-03 11:21:32 +00:00
Fedora Kernel Team d4be0cd065 Merge 'master' into 'os-build' 2021-10-03 10:21:18 +00:00
Fedora Kernel Team c59f4d8584 [redhat] kernel-5.15.0-0.rc3.20211002git53d5fc89d66a.30
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-02 11:22:11 +00:00
Fedora Kernel Team c4a43e0b97 Merge 'master' into 'os-build' 2021-10-02 10:21:39 +00:00
Justin M. Forbes 52fb277fc5 Merge branch 'bug2007430' into 'os-build'
redhat/configs: Enable Hyper-V guests on ARM64

See merge request cki-project/kernel-ark!1394
2021-10-01 20:18:50 +00:00
Justin M. Forbes a4676b3ddb Merge branch 'redhat-config-THINKPAD_LMI' into 'os-build'
redhat: configs: Enable CONFIG_THINKPAD_LMI

See merge request cki-project/kernel-ark!1301
2021-10-01 20:16:56 +00:00
Justin M. Forbes 0f7444e3dc
Fix ordering in genspec args
MR 1413 added some new arguments to genspec.sh, but BUILDID must be the
last argument as it can be empty, and is for official builds.  This
simply fixes the ordering so that BUILDID is last again.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-10-01 11:42:04 -05:00
Justin M. Forbes 14fbbe186a Merge branch 'configs/2021-09-03/security/Kconfig.hardening' into 'os-build'
[redhat] New configs in security/Kconfig.hardening

See merge request cki-project/kernel-ark!1366
2021-10-01 14:56:25 +00:00
Justin M. Forbes f5ef421696 Merge branch 'configs/2021-09-10/drivers/dma' into 'os-build'
[redhat] New configs in drivers/dma

See merge request cki-project/kernel-ark!1377
2021-10-01 14:55:20 +00:00
Justin M. Forbes 21b0a93a82 Merge branch 'koji_link' into 'os-build'
redhat/docs: update Koji link to avoid redirect

See merge request cki-project/kernel-ark!1420
2021-10-01 14:21:00 +00:00
Joel Savitz 719e66b065 redhat/docs: update Koji link to avoid redirect
Signed-off-by: Joel Savitz <jsavitz@redhat.com>
2021-10-01 09:50:21 -04:00
Justin M. Forbes 117870de78 Merge branch 'RHMAINTAINERS_20211001' into 'os-build'
RHMAINTAINERS: Update for Oct 1 2021

See merge request cki-project/kernel-ark!1419
2021-10-01 12:24:22 +00:00
Justin M. Forbes 54cac564f2 Merge branch 'build-profile' into 'os-build'
redhat: add support for different profiles with dist*-brew

See merge request cki-project/kernel-ark!1414
2021-10-01 12:11:36 +00:00
Justin M. Forbes d24f41834f Merge branch 'ppcbpfselftest' into 'os-build'
Fix BPF selftests build on ppc64

See merge request cki-project/kernel-ark!1416
2021-10-01 12:11:20 +00:00
Justin M. Forbes 3fdf33df58 Merge branch 'configs/2021-09-27/crypto/Kconfig' into 'os-build'
[redhat] New configs in crypto/Kconfig

See merge request cki-project/kernel-ark!1399
2021-10-01 12:10:31 +00:00
Justin M. Forbes 1eb3d97f6d Merge branch 'configs/2021-09-02/drivers/firmware' into 'os-build'
[redhat] New configs in drivers/firmware

See merge request cki-project/kernel-ark!1356
2021-10-01 12:08:17 +00:00
Justin M. Forbes a5f3992634 Merge branch 'configs/2021-09-27/drivers/gpio' into 'os-build'
[redhat] New configs in drivers/gpio

See merge request cki-project/kernel-ark!1402
2021-10-01 12:06:59 +00:00
Justin M. Forbes c964e50b83 Merge branch 'configs/2021-08-31/drivers/char' into 'os-build'
[redhat] New configs in drivers/char

See merge request cki-project/kernel-ark!1339
2021-10-01 12:04:49 +00:00
Prarit Bhargava b809bdf718 RHMAINTAINERS: Update for Oct 1 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-10-01 08:03:28 -04:00
Justin M. Forbes 42773625e2 Merge branch 'kernel-ark/deprecate_xtables' into 'os-build'
netfilter: Drop xtables

See merge request cki-project/kernel-ark!1226
2021-10-01 11:56:06 +00:00
Justin M. Forbes 6e4f295d2c Merge branch 'configs/2021-09-08/drivers/gpio' into 'os-build'
[redhat] New configs in drivers/gpio

See merge request cki-project/kernel-ark!1373
2021-10-01 11:52:12 +00:00
Fedora Kernel Team fda58ab4a5 [redhat] kernel-5.15.0-0.rc3.20211001git4de593fb965f.29
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-10-01 11:23:21 +00:00
Fedora Kernel Team caaa8a110c Merge 'master' into 'os-build' 2021-10-01 10:22:15 +00:00
Hans de Goede ebe1b1a39c redhat: configs: Enable CONFIG_THINKPAD_LMI
If the Lenovo BIOS lock-bootorder option is enabled then fwupd
cannot install EFI capsule updates as those require adding
temporary boot-option pointing to the update.

The latest fwupd code has support for detecting this through the
think-lmi kernel module, so this should be enabled for full
fwupd functionality.

And this is also something which I expect Lenovo to want to have
enabled in RHEL kernels in general.

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
Changes in v2:
-Move CONFIG_THINKPAD_LMI to configs/common/generic/x86
2021-10-01 11:29:05 +02:00
Herton R. Krzesinski ece2f810e7 redhat: add *-matched meta packages to rpminspect emptyrpm config
Bugzilla: INTERNAL
Upstream Status: RHEL-only

The emptyrpm test is asking today for verification of *-matched empty meta
packages. Those are meta packages and are intended to be empty (without
files). Thus add these to the exclusion list for emptyrpm rpminspect
test.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-30 19:44:49 -03:00
Herton R. Krzesinski 00a1533ff8 redhat: fix typo and make the output more silent for dist-git sync
The addition of gitlab centos dist-git sync added a typo, plus
the dist-git check about the GL_DISTGIT_USER setting was verbose,
make it silent now.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-30 19:10:19 -03:00
Justin M. Forbes fe87f12171
Fix BPF selftests build on ppc64
For some reason the bpf selftest is failing only on ppc64le. Adding
FORCE_TARGETS=1 fixes the issue, and was taken from RHEL 9.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-30 16:50:20 -05:00
Herton R. Krzesinski 2c22a236ba redhat: add support for different profiles with dist*-brew
Right now there is no way dist-brew/dist-koji can build against the
CentOS koji instance. Add support so that if DISTRO=centos is given
on the command line, dist-brew/koji will use the stream profile and
build against CentOS koji (this requires centpkg to be installed in
the system).

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-30 14:16:11 -03:00
Justin M. Forbes e3c28ded19 Merge branch 's390nodeshift' into 'os-build'
Change s390x CONFIG_NODES_SHIFT from 4 to 1

See merge request cki-project/kernel-ark!1410
2021-09-30 13:55:44 +00:00
Justin M. Forbes 0f026ebff9 Merge branch 's390sha3' into 'os-build'
Build CRYPTO_SHA3_*_S390 inline for s390 zfcpdump

See merge request cki-project/kernel-ark!1409
2021-09-30 13:55:22 +00:00
Justin M. Forbes 914c4e3383 Merge branch 'dist-variable' into 'os-build'
redhat: move the DIST variable setting to Makefile.variables

See merge request cki-project/kernel-ark!1395
2021-09-30 13:54:39 +00:00
Justin M. Forbes a8236ad073 Merge branch 'configs/2021-09-27/drivers/gpu' into 'os-build'
[redhat] New configs in drivers/gpu

See merge request cki-project/kernel-ark!1403
2021-09-30 13:54:17 +00:00
Justin M. Forbes 3ad06197b9 Merge branch 'omit_fedora_rhel_files' into 'os-build'
configs: Add include_rhel and include_fedora to kernel.spec

See merge request cki-project/kernel-ark!1413
2021-09-30 13:53:34 +00:00
Justin M. Forbes a89415ab3f Merge branch 'x86schedutil' into 'os-build'
Turn on CONFIG_CPU_FREQ_GOV_SCHEDUTIL for x86

See merge request cki-project/kernel-ark!1411
2021-09-30 13:47:05 +00:00
Justin M. Forbes 305790e963 Merge branch 'configs/2021-09-27/drivers/acpi' into 'os-build'
[redhat] New configs in drivers/acpi

See merge request cki-project/kernel-ark!1400
2021-09-30 13:44:31 +00:00
Justin M. Forbes 53f2fa7e04 Merge branch 'configs/2021-09-27/arch/Kconfig' into 'os-build'
[redhat] New configs in arch/Kconfig

See merge request cki-project/kernel-ark!1396
2021-09-30 13:44:02 +00:00
Fedora Kernel Team 645a0198e4 [redhat] kernel-5.15.0-0.rc3.20210930git02d5e016800d.28
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-30 11:23:08 +00:00
Fedora Kernel Team 8df5f51474 Merge 'master' into 'os-build' 2021-09-30 10:23:11 +00:00
Prarit Bhargava 4231f0c41a redhat/kernel.spec.template: Cleanup source numbering
Cleanup the numbering of the source files.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-09-29 10:51:50 -04:00
Prarit Bhargava 754935bfcc redhat/kernel.spec.template: Reorganize RHEL and Fedora specific files
Reorganize the RHEL and Fedora specific files into a single section.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-09-29 10:51:50 -04:00
Prarit Bhargava 95ed178152 redhat/kernel.spec.template: Add include_fedora and include_rhel variables
The centos-stream-9 (c9s) [1] repository contains files for both RHEL and
Fedora configs.  The Fedora configs will never be updated, and will
quickly be out-of-date with respect to upstream.  Having the files in
place causes confusion having the Fedora files causes for engineers and
contributors.

Add include_fedora and include_rhel variables.  These can be set in
Makefile.variables to include or exclude RHEL or Fedora-specific files.
These are enabled for ARK, and include_fedora can be disabled for c9s.

[1] https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-09-29 10:51:50 -04:00
Prarit Bhargava 6f7a498fdc redhat/Makefile: Make kernel-local global
The kernel-local file is applied on both rhel and fedora builds.  Make it
a global file instead of in the fedora_files dir.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-09-29 10:51:10 -04:00
Prarit Bhargava c86a2e62a0 redhat/Makefile: Use flavors file
Use the configs/flavors file instead of hardcoding directory copies.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-09-29 10:51:10 -04:00
Justin M. Forbes 6f093cf6a7 Merge branch 'remove-i40iw' into 'os-build'
redhat/configs: Remove CONFIG_INFINIBAND_I40IW

See merge request cki-project/kernel-ark!1354
2021-09-29 14:27:36 +00:00
Fedora Kernel Team 8989b6161d [redhat] kernel-5.15.0-0.rc3.20210929gita4e6f95a891a.27
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-29 12:11:37 +00:00
Justin M. Forbes b2a17c4167 Merge branch 'configs/2021-09-27/arch/arm64' into 'os-build'
[redhat] New configs in arch/arm64

See merge request cki-project/kernel-ark!1397
2021-09-29 11:25:10 +00:00
Justin M. Forbes 9a83af9f53 Merge branch 'config_x86_platform_drivers_intel' into 'os-build'
Fix CONFIG_X86_PLATFORM_DRIVERS_INTEL

See merge request cki-project/kernel-ark!1407
2021-09-29 11:22:32 +00:00
Fedora Kernel Team 51f59ce950 Merge 'master' into 'os-build' 2021-09-29 10:25:34 +00:00
Justin M. Forbes 41965df8a6 Merge branch 'configs/2021-09-27/lib/Kconfig.debug' into 'os-build'
[redhat] New configs in lib/Kconfig.debug

See merge request cki-project/kernel-ark!1406
2021-09-28 19:51:18 +00:00
Justin M. Forbes 2b982ae63d Merge branch 'configs/2021-09-27/drivers/block' into 'os-build'
[redhat] New configs in drivers/block

See merge request cki-project/kernel-ark!1401
2021-09-28 19:45:31 +00:00
Justin M. Forbes 5af2b7b4f3 Merge branch 'rhpkg' into 'os-build'
redhat: rename usage of .rhel8git.mk to .rhpkg.mk

See merge request cki-project/kernel-ark!1389
2021-09-28 19:44:27 +00:00
Justin M. Forbes 0207870905
Turn on CONFIG_CPU_FREQ_GOV_SCHEDUTIL for x86
While CPU_FREQ_GOV_SCHEDUTIL was reviewed and turned off some time ago,
X86_INTEL_PSTATE was reviewed and turned on for x86. With commit
a00ec3874e these options are now conflicting as X86_INTEL_PSTATE
selects pstate as the default governor now. We have been building this
way for quite some time, but because an MR was never created to get
reviews, it has not been formalized. This seeks to rectify that.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-28 13:58:41 -05:00
Justin M. Forbes 1129e141e8
Change s390x CONFIG_NODES_SHIFT from 4 to 1
Upstream change 701dc81e74 removed the fake numa support on s390.  As
a result, though some generic structure was left in place for
applications that expect NUMA interfaces to exist. The current reviewed
and approved setting for NODES_SHIFT on s390 is 4, but that is no longer
valid.  The only valid options are 1 or turning off numa completely
which can be problematic for some applications.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-28 12:13:42 -05:00
Justin M. Forbes 35a90209a7
Build CRYPTO_SHA3_*_S390 inline for s390 zfcpdump
While the configs for CRYPTO_SHA3_512_S390 and CRYPTO_SHA3_256_S390 were
reviewed and set to a module, the zfcpdump kernel does not support
modules. We have to either build them inline (as we have been for a
while) or we need to turn them off all together for the zfcpdump kernel.
This MR exists because it was created in pending and got dropped without
a proper MR to review and decide on the proper solution. I have set them
to build inline, but am happy to change them based on review.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-28 11:47:29 -05:00
David Arcari f61b0d2aa5 cleanup CONFIG_X86_PLATFORM_DRIVERS_INTEL
We want this enabled for x86 on Fedora and RHEL.

Signed-off-by: David Arcari <darcari@redhat.com>
2021-09-28 08:48:36 -04:00
Fedora Kernel Team 494049a545 [redhat] kernel-5.15.0-0.rc3.20210928git0513e464f900.26
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-28 11:21:41 +00:00
Fedora Kernel Team 7717146d51 Merge 'master' into 'os-build' 2021-09-28 10:22:20 +00:00
Justin M. Forbes 972a3abf4e
Manually add pending items that need to be set due to mismatch
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-27 16:51:11 -05:00
Fedora Kernel Team 9acf4e6aa2 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: TEST_SCANF [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:2181
   Prompt: Test scanf() family of functions at runtime
   Depends on: RUNTIME_TESTING_MENU [=y]
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Runtime Testing (RUNTIME_TESTING_MENU [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Eugene Syromiatnikov <esyromia@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Oleg Nesterov <onestero@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:26 +00:00
Fedora Kernel Team a259f0043d [redhat] New configs in drivers/vhost
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: VHOST_MENU [=y]
 Type  : bool
 Defined at drivers/vhost/Kconfig:23
   Prompt: VHOST drivers
   Location:
     -> Device Drivers

---

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:25 +00:00
Fedora Kernel Team 9260ebe8f7 [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/panel/Kconfig:436
   Prompt: Samsung AMS452EF01 panel with S6E88A0 DSI video mode controller
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Panels
 Selects: DRM_MIPI_DSI [=n] && VIDEOMODE_HELPERS [=n]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:22 +00:00
Fedora Kernel Team 81a95d19cb [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: GPIO_CDEV_V1 [=y]
 Type  : bool
 Defined at drivers/gpio/Kconfig:86
   Prompt: Support GPIO ABI Version 1
   Depends on: GPIOLIB [=y] && GPIO_CDEV [=y]
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> Character device (/dev/gpiochipN) support (GPIO_CDEV [=y])

---

Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:21 +00:00
Fedora Kernel Team afadad4e7b [redhat] New configs in drivers/block
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: ZRAM_DEF_COMP_842 [=n]
 Type  : bool
 Defined at drivers/block/zram/Kconfig:42
   Prompt: 842
   Depends on: <choice> && CRYPTO_842 [=m]
   Location:
     -> Device Drivers
       -> Block devices (BLK_DEV [=y])
         -> Compressed RAM block device support (ZRAM [=m])
           -> Default zram compressor (<choice> [=y])

---

 Symbol: ZRAM_DEF_COMP_LZO [=n]
 Type  : bool
 Defined at drivers/block/zram/Kconfig:34
   Prompt: lzo
   Depends on: <choice> && CRYPTO_LZO [=y]
   Location:
     -> Device Drivers
       -> Block devices (BLK_DEV [=y])
         -> Compressed RAM block device support (ZRAM [=m])
           -> Default zram compressor (<choice> [=y])

---

 Symbol: ZRAM_DEF_COMP_LZORLE [=y]
 Type  : bool
 Defined at drivers/block/zram/Kconfig:22
   Prompt: lzo-rle
   Depends on: <choice> && CRYPTO_LZO [=y]
   Location:
     -> Device Drivers
       -> Block devices (BLK_DEV [=y])
         -> Compressed RAM block device support (ZRAM [=m])
           -> Default zram compressor (<choice> [=y])

---

Cc: Ming Lei <ming.lei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:20 +00:00
Fedora Kernel Team f789120870 [redhat] New configs in crypto/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: CRYPTO_CURVE25519 [=n]
 Type  : tristate
 Defined at crypto/Kconfig:285
   Prompt: Curve25519 algorithm
   Depends on: CRYPTO [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
 Selects: CRYPTO_KPP [=y] && CRYPTO_LIB_CURVE25519_GENERIC [=m]
 Selected by [n]:
   - CRYPTO_DEV_HISI_HPRE [=n] && CRYPTO [=y] && CRYPTO_HW [=y] && PCI [=y] && PCI_MSI [=y] && (UACCE [=n] || UACCE [=n]=n) && (ARM64 || COMPILE_TEST [=n] && 64BIT [=y]) && ACPI [=y]

---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Phil Auld <pauld@redhat.com>
Cc: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:19 +00:00
Fedora Kernel Team c2cb8f4204 [redhat] New configs in drivers/acpi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: ACPI_PRMT [=y]
 Type  : bool
 Defined at drivers/acpi/Kconfig:550
   Prompt: Platform Runtime Mechanism Support
   Depends on: EFI [=y] && X86_64 [=y]
   Location:
     -> Power management and ACPI options

---

Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:19 +00:00
Fedora Kernel Team 1f797b8370 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: ARM64_MTE [=y]
 Type  : bool
 Defined at arch/arm64/Kconfig:1647
   Prompt: Memory Tagging Extension support
   Depends on: ARM64_AS_HAS_MTE [=y] && ARM64_TAGGED_ADDR_ABI [=y] && AS_HAS_ARMV8_5 [=y] && AS_HAS_LSE_ATOMICS [=y] && ARM64_PAN [=y]
   Location:
     -> Kernel Features
       -> ARMv8.5 architectural features
 Selects: ARCH_USES_HIGH_VMA_FLAGS [=y]

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:17 +00:00
Fedora Kernel Team 74352b05b0 [redhat] New configs in arch/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: LTO_NONE [=y]
 Type  : bool
 Defined at arch/Kconfig:665
   Prompt: None
   Depends on: <choice>
   Location:
     -> General architecture-dependent options
       -> Link Time Optimization (LTO) (<choice> [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 15:51:16 +00:00
Fedora Kernel Team 5159211ec5 [redhat] AUTOMATIC: New configs 2021-09-27 15:51:15 +00:00
Fedora Kernel Team ddc3eac41a [redhat] AUTOMATIC: New configs 2021-09-27 15:50:53 +00:00
Justin M. Forbes 5212d358b6
Clean up pending common
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-27 10:27:57 -05:00
Justin M. Forbes aef86b3fef Merge branch 'bz2006813_cgrp_config' into 'os-build'
redhat/configs: Enable CONFIG_BLK_CGROUP_IOLATENCY & CONFIG_BLK_CGROUP_FC_APPID

See merge request cki-project/kernel-ark!1391
2021-09-27 12:22:28 +00:00
Justin M. Forbes 13de7e82fa Merge branch 'drop-8.99-chlog' into 'os-build'
redhat: remove kernel.changelog-8.99 file

See merge request cki-project/kernel-ark!1392
2021-09-27 11:29:01 +00:00
Fedora Kernel Team faae7cc4d7 [redhat] kernel-5.15.0-0.rc3.25
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-27 11:22:21 +00:00
Fedora Kernel Team 5f698745e1 Merge 'master' into 'os-build' 2021-09-27 10:21:40 +00:00
Fedora Kernel Team 957528627d [redhat] kernel-5.15.0-0.rc2.20210926gita3b397b4fffb.24
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-26 11:23:16 +00:00
Fedora Kernel Team 83af1b2a5f Merge 'master' into 'os-build' 2021-09-26 10:22:10 +00:00
Fedora Kernel Team ade62880ea [redhat] kernel-5.15.0-0.rc2.20210925git7d42e9818258.23
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-25 11:24:23 +00:00
Fedora Kernel Team b61e178586 Merge 'master' into 'os-build' 2021-09-25 10:22:34 +00:00
Herton R. Krzesinski 3393f72a0a redhat: move the DIST variable setting to Makefile.variables
The DIST value is dynamically detected on ARK, but it can be set to a
fixed value for a branch which forks from it (as some branches are built
only for a given distro and we don't want the DIST value to change even
if building eg. the src.rpm in a different environment). So it makes sense
in this case to move it to the Makefile.variables file.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-24 17:07:32 -03:00
Fedora Kernel Team 5e1e621a4f [redhat] kernel-5.15.0-0.rc2.20210924gitf9e36107ec70.22
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-24 11:22:47 +00:00
Fedora Kernel Team 52f5ce5fee Merge 'master' into 'os-build' 2021-09-24 10:22:14 +00:00
Vitaly Kuznetsov 71263802a0 redhat/configs: Enable Hyper-V guests on ARM64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2007430

Enable Hyper-V guest support for both x86 and ARM64, drop wrong entries
from 'pending'.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
2021-09-24 11:24:25 +02:00
Herton R. Krzesinski 1f475b63e5 redhat: remove kernel.changelog-8.99 file
Now that "redhat: bump RHEL_MAJOR and add the changelog file for it" was
applied, we can drop this old changelog file, the new kernel.changelog-9.99
is being used now.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-23 12:41:18 -03:00
Fedora Kernel Team 98e493ce65 [redhat] kernel-5.15.0-0.rc2.20210923git58e2cf5d7946.21
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-23 11:26:30 +00:00
Fedora Kernel Team b4a1239f65 Merge 'master' into 'os-build' 2021-09-23 10:23:09 +00:00
Waiman Long 7fea6598f1 redhat/configs: Enable CONFIG_BLK_CGROUP_IOLATENCY & CONFIG_BLK_CGROUP_FC_APPID
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2006813
Upstream Status: RHEL only
Tested: After "make dist-configs", both CONFIG_BLK_CGROUP_IOLATENCY and
	CONFIG_BLK_CGROUP_FC_APPID are turned on in all config files.

RHEL8 has CONFIG_BLK_CGROUP_IOLATENCY enabled, so kernel-ark must have
this config option enabled too to provide equivalent functionality.

CONFIG_BLK_CGROUP_FC_APPID should be enabled too as it is for the VMID
feature that will allow RHV to assign an ID so that the FC switches
can identify the flows from different VMs (or containers, even). It is
a feature requested by Broadcom.

The new configs are enabled under the common directory. The ones under
the ark or pending-common directory are removed.

Signed-off-by: Waiman Long <longman@redhat.com>
2021-09-22 20:12:47 -04:00
Justin M. Forbes b71581142b Merge branch 'bz1976884' into 'os-build'
[redhat] redhat/configs: Update configs for secure IPL

See merge request cki-project/kernel-ark!1371
2021-09-22 17:07:49 +00:00
Justin M. Forbes af9559aa97 Merge branch 'os-build' into 'os-build'
redhat/configs: enable CONFIG_SQUASHFS_ZSTD which is already enabled in Fedora 34

See merge request cki-project/kernel-ark!1390
2021-09-22 13:54:26 +00:00
Fedora Kernel Team 9855772315 [redhat] kernel-5.15.0-0.rc2.20210922git92477dd1faa6.20
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-22 11:22:38 +00:00
Fedora Kernel Team d81970b828 Merge 'master' into 'os-build' 2021-09-22 10:21:17 +00:00
Tao Liu be15ac3a6d redhat/configs: enable CONFIG_SQUASHFS_ZSTD which is already enabled in Fedora 34
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1998953
Upstream Status: RHEL-only

Kdump will use ZSTD as the default method for initrd squashfs compression. It is helpful
for reducing the vmcore dump and read time consumption while keeping a good compression
ratio on machines with large memories. Fedora has already enabled CONFIG_SQUASHFS_ZSTD,
this patch enables CONFIG_SQUASHFS_ZSTD for RHEL by removing configs/ark/generic/CONFIG_SQUASHFS_ZSTD
and moving configs/fedora/generic/CONFIG_SQUASHFS_ZSTD to configs/common/generic.

Signed-off-by: Tao Liu <ltao@redhat.com>
2021-09-22 17:04:15 +08:00
Fedora Kernel Team 76b46441ce [redhat] kernel-5.15.0-0.rc2.20210921gitd9fb678414c0.19
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-21 11:20:59 +00:00
Fedora Kernel Team b4a168fa2a Merge 'master' into 'os-build' 2021-09-21 10:19:31 +00:00
Herton R. Krzesinski 4da7d0b65c redhat: rename usage of .rhel8git.mk to .rhpkg.mk
We do not need to use the rhel version in the file name to look for the
RHDISTGIT_CACHE value. Usually this file is used by the maintainers for
configuring the location of the dist-git cache (the dist-git repo can
be big so this saves time in the dist-git sync operation). But having
the version in the name means bumping/changing the major each release,
we do not need to do it: if the maintainer has to maintain different
majors in the same stream, he will use the same dist-git repo/cache for
it. In the case different dist-git repos are needed or the dist-git
repos differ (are not synced between them), the .rhpkg.mk can have if
statements to single out the repos.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-20 19:51:57 -03:00
Fedora Kernel Team 10f24f4dff [redhat] kernel-5.15.0-0.rc2.18
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-20 11:20:17 +00:00
Fedora Kernel Team 667e75f09c Merge 'master' into 'os-build' 2021-09-20 10:21:08 +00:00
Fedora Kernel Team b375782770 [redhat] kernel-5.15.0-0.rc1.20210919gitd4d016caa4b8.17
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-19 11:19:17 +00:00
Fedora Kernel Team b64bf80a6e Merge 'master' into 'os-build' 2021-09-19 10:18:56 +00:00
Fedora Kernel Team 967f0050cc [redhat] kernel-5.15.0-0.rc1.20210918git4357f03d6611.16
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-18 11:19:45 +00:00
Fedora Kernel Team 909479f02a Merge 'master' into 'os-build' 2021-09-18 10:18:24 +00:00
Justin M. Forbes 65af23e9a0 Merge branch 'rhel-next' into 'os-build'
redhat: bump RHEL_MAJOR and add the changelog file for it

See merge request cki-project/kernel-ark!1388
2021-09-17 21:16:13 +00:00
Herton R. Krzesinski 00a155c23a redhat: bump RHEL_MAJOR and add the changelog file for it
kernel-ark does not track anymore work for RHEL 9/CentOS Stream 9. We look
forward to the next major. While "8.99" was chosen as the version for
the work preceding RHEL 9, bump the major so the considered version now is
"9.99". I'm intentionally not removing redhat/kernel.changelog-8.99 yet
in this commit, to avoid any conflicts while this isn't merged. When
this change goes in, I'll propose a new merge request for the removal of
this old changelog file.

Also I'm not including/moving all old changelog entries into the new file,
to avoid conflicts in the next os-build rebase. So when this is included/merged
the first time, no old entries before last release commit will be in the
changelog. However, all changelog entries will be picked up with the first
release commit in the next os-build rebase.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-17 15:01:30 -03:00
Claudio Imbrenda bb92e05d7c [redhat] redhat/configs: Update configs for secure IPL
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976884
Upstream Status: RHEL-only
Tested: by IBM
Conflicts: None

This commit fixes a regression from RHEL8, where the following CONFIG
entries were created in order to support secure IPL on s390x

Signed-off-by: Claudio Imbrenda <cimbrend@redhat.com>
2021-09-17 13:14:04 -04:00
Justin M. Forbes 9c67713d44 Merge branch 'rebase-doc' into 'os-build'
redhat: add documentation about the os-build rebase process

See merge request cki-project/kernel-ark!1387
2021-09-17 16:52:40 +00:00
Herton R. Krzesinski b39b9054bb redhat: add documentation about the os-build rebase process
We have been rebasing os-build lately on each new major Linux upstream
release. Add general instructions/guideline on how to do the rebase
process on top of last upstream tag/commit.

This also provides an explanation on why we are doing the rebase,
provided by Don Zickus. Added some of his suggestions as well on
the rebase process instructions.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-09-17 12:36:04 -03:00
Fedora Kernel Team 4cc6ebc5d9 [redhat] kernel-5.15.0-0.rc1.20210917gitbdb575f87217.15
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-17 11:20:04 +00:00
Fedora Kernel Team 2f66d9f305 Merge 'master' into 'os-build' 2021-09-17 10:19:37 +00:00
Justin M. Forbes 5af493e630 Merge branch 'platform_keyring' into 'os-build'
redhat/configs: enable SYSTEM_BLACKLIST_KEYRING which is already enabled in rhel8 and Fedora 34

See merge request cki-project/kernel-ark!1385
2021-09-16 11:25:53 +00:00
Fedora Kernel Team 5ffa2984d1 [redhat] kernel-5.15.0-0.rc1.20210916gitff1ffd71d5f0.14
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-16 11:19:56 +00:00
Fedora Kernel Team c7e016fd87 Merge 'master' into 'os-build' 2021-09-16 10:19:59 +00:00
Coiby Xu 2b0d3f4480 redhat/configs: enable SYSTEM_BLACKLIST_KEYRING which is already enabled in rhel8 and Fedora 34
Upstream Status: RHEL-only

INTEGRITY_PLATFORM_KEYRING which depends on SYSTEM_BLACKLIST_KEYRING is
needed to make use of the .platform keyring to verify kdump kernel image
signature. By removing configs/ark/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING,
configs/common/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING which has
CONFIG_SYSTEM_BLACKLIST_KEYRING=y will take precedence.

Suggested-by: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Coiby Xu <coxu@redhat.com>
2021-09-15 21:31:03 -04:00
Justin M. Forbes 55e8e99456 Merge branch 'fedoradoc' into 'os-build'
Build kernel-doc for Fedora

See merge request cki-project/kernel-ark!1384
2021-09-15 14:32:43 +00:00
Justin M. Forbes 279da27830
Build kernel-doc for Fedora
We have had a few requests to bring back the kernel-doc package for
Fedora.  While I wanted to bring it into kernel-tools so that it was
built less frequently, it is already being maintained in the kernel spec
so let's just add noarch to Fedora so that it builds there too.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-15 07:56:31 -05:00
Justin M. Forbes 9ca9b313e2 Merge branch 'configs/2021-09-02/drivers/gpu' into 'os-build'
[redhat] New configs in drivers/gpu

See merge request cki-project/kernel-ark!1357
2021-09-15 12:54:15 +00:00
Fedora Kernel Team f6ed2f5179 [redhat] kernel-5.15.0-0.rc1.20210915git3ca706c189db.13
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-15 11:24:35 +00:00
Fedora Kernel Team c06d859928 Merge 'master' into 'os-build' 2021-09-15 10:18:59 +00:00
Justin M. Forbes b3e6a7b2b3 Merge branch 'enable_intel_qep' into 'os-build'
x86_64: Enable Elkhart Lake Quadrature Encoder Peripheral support

See merge request cki-project/kernel-ark!1383
2021-09-14 22:55:08 +00:00
Fedora Kernel Team b214e1b600 [redhat] kernel-5.15.0-0.rc1.20210914gitd0ee23f9d78b.12
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-14 11:19:30 +00:00
Fedora Kernel Team 2651629a2d Merge 'master' into 'os-build' 2021-09-14 10:25:05 +00:00
Prarit Bhargava f34c9742bd x86_64: Enable Elkhart Lake Quadrature Encoder Peripheral support
Enable Elkhart Lake Quadrature Encoder Peripheral support for both
RHEL and Fedora.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-09-13 15:12:07 -04:00
Fedora Kernel Team bae524e7c2 [redhat] New configs in kernel/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: DMA_RESTRICTED_POOL [=n]
 Type  : bool
 Defined at kernel/dma/Kconfig:83
   Prompt: DMA Restricted Pool
   Depends on: OF [=y] && OF_RESERVED_MEM [=y] && SWIOTLB [=y]
   Location:
     -> Library routines

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Joel Savitz <jsavitz@redhat.com>
Cc: Lucas Zampieri <lzampier@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-13 15:10:53 -04:00
Justin M. Forbes f5f6f14b87 Merge branch 'configs/2021-09-07/kernel/dma' into 'os-build'
[redhat] New configs in kernel/dma

See merge request cki-project/kernel-ark!1370
2021-09-13 15:00:10 +00:00
Fedora Kernel Team 293c1d5c86 [redhat] kernel-5.15.0-0.rc1.11
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-13 11:20:11 +00:00
Fedora Kernel Team 953c6010e1 Merge 'master' into 'os-build' 2021-09-13 10:19:36 +00:00
Fedora Kernel Team 51e379686d [redhat] kernel-5.15.0-0.rc0.20210912git78e709522d2c.10
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-12 11:19:52 +00:00
Fedora Kernel Team 6ddf6bd917 [redhat] AUTOMATIC: New configs 2021-09-12 10:19:40 +00:00
Fedora Kernel Team 015556b1c4 [redhat] AUTOMATIC: New configs 2021-09-12 10:19:22 +00:00
Fedora Kernel Team dc02ad16e0 Merge 'master' into 'os-build' 2021-09-12 10:18:39 +00:00
Fedora Kernel Team 3be79dc758 [redhat] kernel-5.15.0-0.rc0.20210911git926de8c4326c.9
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-11 11:20:03 +00:00
Fedora Kernel Team 21773cf1d1 Merge 'master' into 'os-build' 2021-09-11 10:18:21 +00:00
Fedora Kernel Team 27a798072d [redhat] kernel-5.15.0-0.rc0.20210910gitbf9f243f23e6.8
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-10 11:20:01 +00:00
Fedora Kernel Team f302bae7bf [redhat] New configs in drivers/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: AMD_PTDMA [=n]
 Type  : tristate
 Defined at drivers/dma/ptdma/Kconfig:2
   Prompt: AMD PassThru DMA Engine
   Depends on: DMADEVICES [=y] && X86_64 [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
 Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]

---

 Symbol: INTEL_IDXD_COMPAT [=n]
 Type  : bool
 Defined at drivers/dma/Kconfig:299
   Prompt: Legacy behavior for idxd driver
   Depends on: DMADEVICES [=y] && PCI [=y] && X86_64 [=y]
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
 Selects: INTEL_IDXD_BUS [=m]

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-10 10:20:24 +00:00
Fedora Kernel Team 07174d1120 [redhat] AUTOMATIC: New configs 2021-09-10 10:20:23 +00:00
Fedora Kernel Team c8cdb9a709 [redhat] AUTOMATIC: New configs 2021-09-10 10:20:09 +00:00
Fedora Kernel Team 21f7130d80 Merge 'master' into 'os-build' 2021-09-10 10:19:29 +00:00
Justin M. Forbes 38311c7b64 Merge branch 'configs/2021-09-09/mm/damon' into 'os-build'
[redhat] New configs in mm/damon

See merge request cki-project/kernel-ark!1376
2021-09-09 15:39:15 +00:00
Justin M. Forbes 7f68ae6400 Merge branch 'configs/2021-09-08/arch/arm64' into 'os-build'
[redhat] New configs in arch/arm64

See merge request cki-project/kernel-ark!1372
2021-09-09 15:38:46 +00:00
Justin M. Forbes f1cdec3ce7 Merge branch 'configs/2021-09-07/init/Kconfig' into 'os-build'
[redhat] New configs in init/Kconfig

See merge request cki-project/kernel-ark!1369
2021-09-09 14:23:42 +00:00
Justin M. Forbes 987423f578
Fixup IOMMU configs in pending so that configs are sane again
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-09 09:07:43 -05:00
Fedora Kernel Team 65fc502aef [redhat] kernel-5.15.0-0.rc0.20210909gita3fa7a101dcf.7
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-09 11:20:29 +00:00
Phil Sutter 87aa0869b0 redhat: configs: Disable xtables and ipset
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945179
Upstream Status: RHEL-only

These drivers have been deprecated with RHEL9, so with RHEL10 it is time
to remove them:

- CONFIG_BRIDGE_NF_EBTABLES
- CONFIG_IP6_NF_IPTABLES
- CONFIG_IP_NF_ARPTABLES
- CONFIG_IP_NF_IPTABLES
- CONFIG_IP_SET
- CONFIG_NFT_COMPAT

Enable previous selected symbols to reduce impact to deprecated symbols:

- CONFIG_NF_CONNTRACK_LABELS

Drop symbols not used anymore:

- CONFIG_NETFILTER_XTABLES
- CONFIG_BRIDGE_NETFILTER
2021-09-09 12:31:53 +02:00
Fedora Kernel Team 5bdc634a0a [redhat] New configs in mm/damon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: DAMON [=n]
 Type  : bool
 Defined at mm/damon/Kconfig:5
   Prompt: DAMON: Data Access Monitoring Framework
   Location:
     -> Memory Management options
       -> Data Access Monitoring

---

Cc: Rafael Aquini <aquini@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Artem Savkov <asavkov@redhat.com>
Cc: Baoquan He <bhe@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Waiman Long <longman@redhat.com>
Cc: mm-maint@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-09 10:20:29 +00:00
Fedora Kernel Team 3b3ac7a912 [redhat] AUTOMATIC: New configs 2021-09-09 10:20:28 +00:00
Fedora Kernel Team f779c29bda [redhat] AUTOMATIC: New configs 2021-09-09 10:20:09 +00:00
Fedora Kernel Team e0784bf79b Merge 'master' into 'os-build' 2021-09-09 10:19:22 +00:00
Phil Sutter 1739846090 redhat: Add mark_driver_deprecated()
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945179
Upstream Status: RHEL-only

Allow marking drivers deprecated. The printed message is basically
identical to what mark_hardware_deprecated() prints but generalized a
bit to cover non-hardware drivers also. Semantically, the introduced
function aligns with mark_driver_unsupported().

Signed-off-by: Phil Sutter <psutter@redhat.com>
2021-09-08 21:47:27 +02:00
Justin M. Forbes 1d1be2574a Merge branch 'configs/2021-08-31/lib/Kconfig.kcsan' into 'os-build'
[redhat] New configs in lib/Kconfig.kcsan

See merge request cki-project/kernel-ark!1340
2021-09-08 14:35:18 +00:00
Fedora Kernel Team 470034e37f [redhat] kernel-5.15.0-0.rc0.20210908gitac08b1c68d1b.6
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-08 11:22:07 +00:00
Fedora Kernel Team f430f25c6b [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: GPIO_VIRTIO [=n]
 Type  : tristate
 Defined at drivers/gpio/Kconfig:1674
   Prompt: VirtIO GPIO support
   Depends on: GPIOLIB [=y] && VIRTIO [=y]
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> Virtual GPIO drivers

---

Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-08 10:20:22 +00:00
Fedora Kernel Team 0dee9517ba [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: NVHE_EL2_DEBUG [=n]
 Type  : bool
 Defined at arch/arm64/kvm/Kconfig:50
   Prompt: Debug mode for non-VHE EL2 object
   Depends on: VIRTUALIZATION [=y] && KVM [=y]
   Location:
     -> Virtualization (VIRTUALIZATION [=y])
       -> Kernel-based Virtual Machine (KVM) support (KVM [=y])

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-08 10:20:21 +00:00
Fedora Kernel Team 4d90b35d17 [redhat] AUTOMATIC: New configs 2021-09-08 10:20:20 +00:00
Fedora Kernel Team e45f7d908c [redhat] AUTOMATIC: New configs 2021-09-08 10:20:03 +00:00
Fedora Kernel Team bbef0707fe Merge 'master' into 'os-build' 2021-09-08 10:19:23 +00:00
Justin M. Forbes 077c6b8fba
Some initial Fedora config items for 5.15
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-07 16:16:36 -05:00
Justin M. Forbes 12a24cc274 Update CONFIG_WERROR to disabled as it can cause issue with out of tree modules. 2021-09-07 15:22:36 +00:00
Justin M. Forbes d4a9c7d853 Merge branch 'configs/2021-09-03/drivers/platform' into 'os-build'
[redhat] New configs in drivers/platform

See merge request cki-project/kernel-ark!1365
2021-09-07 15:01:03 +00:00
Justin M. Forbes dc780c9a0b Merge branch 'configs/2021-09-02/drivers/iio' into 'os-build'
[redhat] New configs in drivers/iio

See merge request cki-project/kernel-ark!1359
2021-09-07 13:28:46 +00:00
Fedora Kernel Team 280e65edaf [redhat] kernel-5.15.0-0.rc0.20210907git4b93c544e90e.5
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-07 11:22:25 +00:00
Fedora Kernel Team bbb46cfeb8 [redhat] New configs in kernel/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: DMA_RESTRICTED_POOL [=n]
 Type  : bool
 Defined at kernel/dma/Kconfig:83
   Prompt: DMA Restricted Pool
   Depends on: OF [=y] && OF_RESERVED_MEM [=y] && SWIOTLB [=y]
   Location:
     -> Library routines

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Joel Savitz <jsavitz@redhat.com>
Cc: Lucas Zampieri <lzampier@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-07 10:37:41 +00:00
Fedora Kernel Team 7ed5bdfc1e [redhat] New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: WERROR [=y]
 Type  : bool
 Defined at init/Kconfig:140
   Prompt: Compile the kernel with warnings as errors
   Location:
     -> General setup

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Artem Savkov <asavkov@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Kairui Song <kasong@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-07 10:37:40 +00:00
Fedora Kernel Team f7ce31ad6a [redhat] AUTOMATIC: New configs 2021-09-07 10:37:38 +00:00
Fedora Kernel Team 945aac1909 [redhat] AUTOMATIC: New configs 2021-09-07 10:37:19 +00:00
Justin M. Forbes 1a4e7f4080
Merge branch 'master' into os-build
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-06 21:35:58 -05:00
Justin M. Forbes bf09afbdac Merge branch 'config_chelsio_ipsec' into 'os-build'
[redhat] configs: Remove pending CONFIG_CHELSIO_IPSEC_INLINE file

See merge request cki-project/kernel-ark!1342
2021-09-03 17:06:49 +00:00
Justin M. Forbes 0277f41939 Merge branch 'configs/2021-09-01/drivers/net/phy' into 'os-build'
[redhat] New configs in drivers/net/phy

See merge request cki-project/kernel-ark!1347
2021-09-03 17:05:00 +00:00
Justin M. Forbes c13178fbfd Merge branch 'configs/2021-09-01/net/mctp' into 'os-build'
[redhat] New configs in net/mctp

See merge request cki-project/kernel-ark!1352
2021-09-03 17:04:10 +00:00
Justin M. Forbes ce58fafd71 Merge branch 'configs/2021-09-01/net/ipv6' into 'os-build'
[redhat] New configs in net/ipv6

See merge request cki-project/kernel-ark!1351
2021-09-03 17:03:20 +00:00
Justin M. Forbes b771731898 Merge branch 'configs/2021-09-02/sound/soc' into 'os-build'
[redhat] New configs in sound/soc

See merge request cki-project/kernel-ark!1364
2021-09-03 17:02:30 +00:00
Justin M. Forbes c58f026981 Merge branch 'configs/2021-09-02/drivers/nvmem' into 'os-build'
[redhat] New configs in drivers/nvmem

See merge request cki-project/kernel-ark!1361
2021-09-03 17:01:10 +00:00
Justin M. Forbes 18ed62483f Merge branch 'configs/2021-09-02/drivers/media' into 'os-build'
[redhat] New configs in drivers/media

See merge request cki-project/kernel-ark!1360
2021-09-03 17:00:30 +00:00
Justin M. Forbes 3bdfff2f7b Merge branch 'configs/2021-09-01/drivers/hwmon' into 'os-build'
[redhat] New configs in drivers/hwmon

See merge request cki-project/kernel-ark!1344
2021-09-03 16:59:32 +00:00
Justin M. Forbes c93f517550 Merge branch 'configs/2021-09-02/init/Kconfig' into 'os-build'
[redhat] New configs in init/Kconfig

See merge request cki-project/kernel-ark!1362
2021-09-03 16:58:50 +00:00
CKI Gitlab a2956882ae [redhat] New configs in init/Kconfig 2021-09-03 16:58:48 +00:00
Fedora Kernel Team 4cddd8e830 [redhat] kernel-5.15.0-0.rc0.20210903gita9c9a6f741cd.4
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-03 12:52:16 +00:00
Fedora Kernel Team 0548ef64d6 [redhat] New configs in security/Kconfig.hardening
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: ZERO_CALL_USED_REGS [=n]
 Type  : bool
 Defined at security/Kconfig.hardening:235
   Prompt: Enable register zeroing on function exit
   Depends on: CC_HAS_ZERO_CALL_USED_REGS [=y]
   Location:
     -> Security options
       -> Kernel hardening options
         -> Memory initialization

---

Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Richard Guy Briggs <rbriggs@redhat.com>
Cc: Vladis Dronov <vdronov@redhat.com>
Cc: Wander Costa <wcosta@redhat.com>
Cc: Yannick Cote <ycote@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-03 12:11:35 +00:00
Fedora Kernel Team 1128a77649 [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: INTEL_SAR_INT1092 [=n]
 Type  : tristate
 Defined at drivers/platform/x86/intel/int1092/Kconfig:1
   Prompt: Intel Specific Absorption Rate Driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_PLATFORM_DRIVERS_INTEL [=y] && ACPI [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
         -> Intel x86 Platform Specific Device Drivers (X86_PLATFORM_DRIVERS_INTEL [=y])

---

 Symbol: MERAKI_MX100 [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:284
   Prompt: Cisco Meraki MX100 Platform Driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && GPIOLIB [=y] && GPIO_ICH [=m] && LEDS_CLASS [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
 Selects: LEDS_GPIO [=n]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-03 12:11:34 +00:00
Fedora Kernel Team 4f116dd3c8 [redhat] AUTOMATIC: New configs 2021-09-03 12:11:34 +00:00
Fedora Kernel Team 0b498e593b [redhat] AUTOMATIC: New configs 2021-09-03 12:11:15 +00:00
Justin M. Forbes 641b046455
Merge branch 'master' into os-build
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-03 06:51:30 -05:00
Fedora Kernel Team 0b8f039c58 [redhat] kernel-5.15.0-0.rc0.20210902git4ac6d90867a4.3
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 11:20:33 +00:00
Fedora Kernel Team 6b9d4f5b59 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: SND_SOC_AMD_ACP5x [=n]
 Type  : tristate
 Defined at sound/soc/amd/Kconfig:56
   Prompt: AMD Audio Coprocessor-v5.x I2S support
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && X86 [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])

---

 Symbol: SND_SOC_MT8195 [=n]
 Type  : tristate
 Defined at sound/soc/mediatek/Kconfig:188
   Prompt: ASoC support for Mediatek MT8195 chip
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
 Selects: SND_SOC_MEDIATEK [=n]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 10:20:32 +00:00
Fedora Kernel Team 4b3e47a505 [redhat] New configs in drivers/nvmem
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: NVMEM_NINTENDO_OTP [=n]
 Type  : tristate
 Defined at drivers/nvmem/Kconfig:110
   Prompt: Nintendo Wii and Wii U OTP Support
   Depends on: NVMEM [=y]
   Location:
     -> Device Drivers
       -> NVMEM Support (NVMEM [=y])

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 10:20:29 +00:00
Fedora Kernel Team 7cb77dc043 [redhat] New configs in drivers/media
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: VIDEO_IMX335 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:845
   Prompt: Sony IMX335 sensor support
   Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]

---

 Symbol: VIDEO_IMX412 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:871
   Prompt: Sony IMX412 sensor support
   Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]

---

 Symbol: VIDEO_OV9282 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:1134
   Prompt: OmniVision OV9282 sensor support
   Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]

---

Cc: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 10:20:28 +00:00
Fedora Kernel Team afc4701aea [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: AD5110 [=n]
 Type  : tristate
 Defined at drivers/iio/potentiometer/Kconfig:9
   Prompt: Analog Devices AD5110 and similar Digital Potentiometer driver
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Digital potentiometers

---

 Symbol: SENSIRION_SGP40 [=n]
 Type  : tristate
 Defined at drivers/iio/chemical/Kconfig:134
   Prompt: Sensirion SGP40 gas sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Chemical Sensors
 Selects: CRC8 [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 10:20:27 +00:00
Fedora Kernel Team e792544401 [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: DRM_PANEL_INNOLUX_EJ030NA [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/panel/Kconfig:149
   Prompt: Innolux EJ030NA 320x480 LCD panel
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && SPI [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Panels
 Selects: REGMAP_SPI [=m]

---

 Symbol: DRM_PANEL_SAMSUNG_ATNA33XC20 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/panel/Kconfig:368
   Prompt: Samsung ATNA33XC20 eDP panel
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && BACKLIGHT_CLASS_DEVICE [=y] && PM [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Panels
 Selects: DRM_DP_AUX_BUS [=n]

---

 Symbol: DRM_PANEL_SAMSUNG_DB7430 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/panel/Kconfig:379
   Prompt: Samsung DB7430-based DPI panels
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && SPI [=y] && GPIOLIB [=y] && BACKLIGHT_CLASS_DEVICE [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Panels
 Selects: DRM_MIPI_DBI [=n]

---

 Symbol: DRM_PANEL_WIDECHIPS_WS2401 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/panel/Kconfig:600
   Prompt: Widechips WS2401 DPI panel driver
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && SPI [=y] && GPIOLIB [=y] && BACKLIGHT_CLASS_DEVICE [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Panels
 Selects: DRM_MIPI_DBI [=n]

---

 Symbol: DRM_VMWGFX_MKSSTATS [=n]
 Type  : bool
 Defined at drivers/gpu/drm/vmwgfx/Kconfig:25
   Prompt: Enable mksGuestStats instrumentation of vmwgfx by default
   Depends on: HAS_IOMEM [=y] && DRM_VMWGFX [=m] && X86 [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> DRM driver for VMware Virtual GPU (DRM_VMWGFX [=m])

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 10:20:24 +00:00
Fedora Kernel Team 5a873436ea [redhat] New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: ARM_SCMI_TRANSPORT_MAILBOX [=y]
 Type  : bool
 Defined at drivers/firmware/arm_scmi/Kconfig:45
   Prompt: SCMI transport based on Mailbox
   Depends on: ARM_SCMI_PROTOCOL [=y] && MAILBOX [=y]
   Location:
     -> Firmware Drivers
       -> ARM System Control and Management Interface Protocol
         -> ARM System Control and Management Interface (SCMI) Message Protocol (ARM_SCMI_PROTOCOL [=y])
 Selects: ARM_SCMI_HAVE_TRANSPORT [=y] && ARM_SCMI_HAVE_SHMEM [=y]

---

 Symbol: ARM_SCMI_TRANSPORT_SMC [=y]
 Type  : bool
 Defined at drivers/firmware/arm_scmi/Kconfig:57
   Prompt: SCMI transport based on SMC
   Depends on: ARM_SCMI_PROTOCOL [=y] && HAVE_ARM_SMCCC_DISCOVERY [=y]
   Location:
     -> Firmware Drivers
       -> ARM System Control and Management Interface Protocol
         -> ARM System Control and Management Interface (SCMI) Message Protocol (ARM_SCMI_PROTOCOL [=y])
 Selects: ARM_SCMI_HAVE_TRANSPORT [=y] && ARM_SCMI_HAVE_SHMEM [=y]

---

 Symbol: ARM_SCMI_TRANSPORT_VIRTIO [=n]
 Type  : bool
 Defined at drivers/firmware/arm_scmi/Kconfig:69
   Prompt: SCMI transport based on VirtIO
   Depends on: ARM_SCMI_PROTOCOL [=y] && VIRTIO [=y]
   Location:
     -> Firmware Drivers
       -> ARM System Control and Management Interface Protocol
         -> ARM System Control and Management Interface (SCMI) Message Protocol (ARM_SCMI_PROTOCOL [=y])
 Selects: ARM_SCMI_HAVE_TRANSPORT [=y] && ARM_SCMI_HAVE_MSG [=n]

---

 Symbol: QCOM_SCM [=n]
 Type  : tristate
 Defined at drivers/firmware/Kconfig:205
   Prompt: Qcom SCM driver
   Depends on: (ARM || ARM64 [=y]) && HAVE_ARM_SMCCC [=y]
   Location:
     -> Firmware Drivers
 Selects: RESET_CONTROLLER [=y]
 Selected by [n]:
   - ARM_QCOM_SPM_CPUIDLE [=n] && CPU_IDLE [=y] && (ARM || ARM64 [=y]) && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && !ARM64 [=y] && MMU [=y]
   - SCSI_UFS_QCOM [=n] && SCSI_LOWLEVEL [=y] && SCSI [=y] && SCSI_UFSHCD_PLATFORM [=n] && ARCH_QCOM [=y] && SCSI_UFS_CRYPTO [=n]
   - VIDEO_QCOM_VENUS [=n] && MEDIA_SUPPORT [=n] && MEDIA_PLATFORM_SUPPORT [=n] && V4L_MEM2MEM_DRIVERS [=n] && VIDEO_DEV [=n] && VIDEO_V4L2 [=n] && QCOM_SMEM [=n] && (ARCH_QCOM [=y] && IOMMU_DMA [=y] || COMPILE_TEST [=n]) && ARCH_QCOM [=y]
   - DRM_MSM [=n] && HAS_IOMEM [=y] && DRM [=m] && (ARCH_QCOM [=y] || SOC_IMX5 || ARM && COMPILE_TEST [=n]) && IOMMU_SUPPORT [=y] && OF [=y] && COMMON_CLK [=y] && (QCOM_OCMEM [=n] || QCOM_OCMEM [=n]=n) && (QCOM_LLCC [=n] || QCOM_LLCC [=n]=n) && (QCOM_COMMAND_DB [=n] || QCOM_COMMAND_DB [=n]=n) && ARCH_QCOM [=y]
   - MMC_SDHCI_MSM [=n] && MMC [=m] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && MMC_SDHCI_PLTFM [=m] && MMC_CRYPTO [=n] && ARCH_QCOM [=y]
   - QCOM_Q6V5_MSS [=n] && REMOTEPROC [=n] && OF [=y] && ARCH_QCOM [=y] && QCOM_SMEM [=n] && (RPMSG_QCOM_SMD [=n] || COMPILE_TEST [=n] && RPMSG_QCOM_SMD [=n]=n) && (RPMSG_QCOM_GLINK_SMEM [=n] || RPMSG_QCOM_GLINK_SMEM [=n]=n) && (QCOM_SYSMON [=n] || QCOM_SYSMON [=n]=n) && (RPMSG_QCOM_GLINK [=n] || RPMSG_QCOM_GLINK [=n]=n)
   - QCOM_Q6V5_PAS [=n] && REMOTEPROC [=n] && OF [=y] && ARCH_QCOM [=y] && QCOM_SMEM [=n] && (RPMSG_QCOM_SMD [=n] || COMPILE_TEST [=n] && RPMSG_QCOM_SMD [=n]=n) && (RPMSG_QCOM_GLINK_SMEM [=n] || RPMSG_QCOM_GLINK_SMEM [=n]=n) && (QCOM_SYSMON [=n] || QCOM_SYSMON [=n]=n) && (RPMSG_QCOM_GLINK [=n] || RPMSG_QCOM_GLINK [=n]=n)
   - QCOM_Q6V5_WCSS [=n] && REMOTEPROC [=n] && OF [=y] && ARCH_QCOM [=y] && QCOM_SMEM [=n] && (RPMSG_QCOM_SMD [=n] || COMPILE_TEST [=n] && RPMSG_QCOM_SMD [=n]=n) && (RPMSG_QCOM_GLINK_SMEM [=n] || RPMSG_QCOM_GLINK_SMEM [=n]=n) && (QCOM_SYSMON [=n] || QCOM_SYSMON [=n]=n) && (RPMSG_QCOM_GLINK [=n] || RPMSG_QCOM_GLINK [=n]=n)
   - QCOM_WCNSS_PIL [=n] && REMOTEPROC [=n] && OF [=y] && ARCH_QCOM [=y] && (RPMSG_QCOM_SMD [=n] || COMPILE_TEST [=n] && RPMSG_QCOM_SMD [=n]=n) && (RPMSG_QCOM_GLINK_SMEM [=n] || RPMSG_QCOM_GLINK_SMEM [=n]=n) && QCOM_SMEM [=n] && (QCOM_SYSMON [=n] || QCOM_SYSMON [=n]=n) && (RPMSG_QCOM_GLINK [=n] || RPMSG_QCOM_GLINK [=n]=n)
   - QCOM_MDT_LOADER [=n]
   - QCOM_OCMEM [=n] && ARCH_QCOM [=y]
   - QCOM_RMTFS_MEM [=n] && ARCH_QCOM [=y]

---

 Symbol: SYSFB_SIMPLEFB [=n]
 Type  : bool
 Defined at drivers/firmware/Kconfig:227
   Prompt: Mark VGA/VBE/EFI FB as generic system framebuffer
   Depends on: SYSFB [=y]
   Location:
     -> Firmware Drivers

---

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 10:20:23 +00:00
Fedora Kernel Team 6181d747c0 [redhat] New configs in drivers/dma-buf
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: DMABUF_SYSFS_STATS [=n]
 Type  : bool
 Defined at drivers/dma-buf/Kconfig:75
   Prompt: DMA-BUF sysfs statistics
   Location:
     -> Device Drivers
       -> DMABUF options
 Selects: DMA_SHARED_BUFFER [=y]

---

Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-02 10:20:22 +00:00
Fedora Kernel Team b8fbca7c8b [redhat] AUTOMATIC: New configs 2021-09-02 10:20:21 +00:00
Fedora Kernel Team a419b8d017 [redhat] AUTOMATIC: New configs 2021-09-02 10:20:03 +00:00
Fedora Kernel Team e4b35cc284 Merge 'master' into 'os-build' 2021-09-02 10:19:19 +00:00
Kamal Heib caa87a6437 redhat/configs: Remove CONFIG_INFINIBAND_I40IW
Now that the CONFIG_INFINIBAND_IRDMA driver is supported, we can remove
the CONFIG_INFINIBAND_I40IW, because the IRDMA driver replaces the I40IW
driver.

Upstream: RHEL-only.

Signed-off-by: Kamal Heib <kheib@redhat.com>
2021-09-02 12:29:02 +03:00
Fedora Kernel Team 2cffd57e96 [redhat] kernel-5.15.0-0.rc0.20210901git9e9fb7655ed5.2
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-01 14:12:11 +00:00
Fedora Kernel Team 0d0cf1085d [redhat] New configs in net/mctp
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: MCTP [=n]
 Type  : tristate
 Defined at net/mctp/Kconfig:2
   Prompt: MCTP core protocol support
   Depends on: NET [=y]
   Location:
     -> Networking support (NET [=y])

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-01 13:25:50 +00:00
Fedora Kernel Team 950e51879e [redhat] New configs in net/ipv6
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: IPV6_IOAM6_LWTUNNEL [=n]
 Type  : bool
 Defined at net/ipv6/Kconfig:331
   Prompt: IPv6: IOAM Pre-allocated Trace insertion support
   Depends on: NET [=y] && INET [=y] && IPV6 [=y]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> TCP/IP networking (INET [=y])
           -> The IPv6 protocol (IPV6 [=y])
 Selects: LWTUNNEL [=y]

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-01 13:25:49 +00:00
Fedora Kernel Team 42cca9532e [redhat] New configs in drivers/net/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: MAXLINEAR_GPHY [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:210
   Prompt: Maxlinear Ethernet PHYs
   Depends on: NETDEVICES [=y] && PHYLIB [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])

---

Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-01 13:25:45 +00:00
Fedora Kernel Team cb3dbf1ba7 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: SENSORS_AQUACOMPUTER_D5NEXT [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:257
   Prompt: Aquacomputer D5 Next watercooling pump
   Depends on: HWMON [=y] && USB_HID [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

 Symbol: SENSORS_SBRMI [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:1564
   Prompt: Emulated SB-RMI sensor
   Depends on: HWMON [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-09-01 13:25:43 +00:00
Fedora Kernel Team ab95c1e0a8 [redhat] AUTOMATIC: New configs 2021-09-01 13:25:42 +00:00
Fedora Kernel Team 77900ee3df [redhat] AUTOMATIC: New configs 2021-09-01 13:25:23 +00:00
Justin M. Forbes 45d04677dc
Merge branch 'master' into os-build
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-09-01 08:02:51 -05:00
Fedora Kernel Team 4f5bf3240c [redhat] kernel-5.15.0-0.rc0.20210831gitb91db6a0b52e.1
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-31 11:19:24 +00:00
Patrick Talbert bc78b42b62 [redhat] configs: Remove pending CONFIG_CHELSIO_IPSEC_INLINE file
The redhat/configs/pending-common/generic/CONFIG_CHELSIO_IPSEC_INLINE
file was left behind. It enables the config item as a module. However,
the common/generic/ directory includes this item as a built-in (=y).

Remove the pending-common CONFIG_CHELSIO_IPSEC_INLINE file AND change
the common/generic/ entry from =y to =m. The result is the generated
kernel config files do not change.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-31 13:02:55 +02:00
Fedora Kernel Team f4d7906a7b [redhat] New configs in lib/Kconfig.kcsan
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: KCSAN [=n]
 Type  : bool
 Defined at lib/Kconfig.kcsan:23
   Prompt: KCSAN: dynamic data race detector
   Depends on: HAVE_ARCH_KCSAN [=y] && HAVE_KCSAN_COMPILER [=y] && DEBUG_KERNEL [=y] && !KASAN [=n] && !KCSAN_KCOV_BROKEN [=n]
   Location:
     -> Kernel hacking
       -> Generic Kernel Debugging Instruments
 Selects: STACKTRACE [=y]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Eugene Syromiatnikov <esyromia@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Oleg Nesterov <onestero@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-31 10:20:42 +00:00
Fedora Kernel Team 05bade0836 [redhat] New configs in drivers/char
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: HW_RANDOM_ARM_SMCCC_TRNG [=y]
 Type  : tristate
 Defined at drivers/char/hw_random/Kconfig:527
   Prompt: Arm SMCCC TRNG firmware interface support
   Depends on: HW_RANDOM [=y] && HAVE_ARM_SMCCC_DISCOVERY [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Hardware Random Number Generator Core support (HW_RANDOM [=y])

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-31 10:20:41 +00:00
Fedora Kernel Team caf795a20b [redhat] New configs in crypto/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: CRYPTO_SM4_AESNI_AVX2_X86_64 [=n]
 Type  : tristate
 Defined at crypto/Kconfig:1594
   Prompt: SM4 cipher algorithm (x86_64/AES-NI/AVX2)
   Depends on: CRYPTO [=y] && X86 [=y] && 64BIT [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
 Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_SIMD [=y] && CRYPTO_ALGAPI [=y] && CRYPTO_LIB_SM4 [=n] && CRYPTO_SM4_AESNI_AVX_X86_64 [=n]

---

 Symbol: CRYPTO_SM4_AESNI_AVX_X86_64 [=n]
 Type  : tristate
 Defined at crypto/Kconfig:1573
   Prompt: SM4 cipher algorithm (x86_64/AES-NI/AVX)
   Depends on: CRYPTO [=y] && X86 [=y] && 64BIT [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
 Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_SIMD [=y] && CRYPTO_ALGAPI [=y] && CRYPTO_LIB_SM4 [=n]
 Selected by [n]:
   - CRYPTO_SM4_AESNI_AVX2_X86_64 [=n] && CRYPTO [=y] && X86 [=y] && 64BIT [=y]

---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Phil Auld <pauld@redhat.com>
Cc: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-31 10:20:40 +00:00
Fedora Kernel Team 2d2bb1cbcd [redhat] New configs in arch/x86
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: PERF_EVENTS_AMD_UNCORE [=y]
 Type  : tristate
 Defined at arch/x86/events/Kconfig:37
   Prompt: AMD Uncore performance events
   Depends on: PERF_EVENTS [=y] && CPU_SUP_AMD [=y]
   Location:
     -> Processor type and features
       -> Performance monitoring

---

Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-31 10:20:38 +00:00
Fedora Kernel Team 4aef45ddd7 [redhat] AUTOMATIC: New configs 2021-08-31 10:20:37 +00:00
Fedora Kernel Team fc37282ef4 [redhat] AUTOMATIC: New configs 2021-08-31 10:20:16 +00:00
Fedora Kernel Team 11e114a092 Merge 'master' into 'os-build' 2021-08-31 10:19:21 +00:00
Mark Salter db5256d639 arm64: use common CONFIG_MAX_ZONEORDER for arm kernel
Now that RHEL9 is using 4K pagesize, MAX_ZONEORDER is defaulting
to 11. Fedora uses an out of tree patch to default to 13 when
building for server class machines. RHEL9 should also be using 13,
so make the MAX_ZONEORDER config and the out of tree patch common
between RHEL9 and Fedora.

Signed-off-by: Mark Salter <msalter@redhat.com>
2021-08-30 15:45:00 -04:00
Justin M. Forbes 23f9d96723 Create Makefile.variables for a single point of configuration change
The existing Makefiles and scripts are hard coded to expect that we are
building from the os-build branch with master being the upstream branch.
This does not work well for fedora-stable releases, and does not offer
flexibility to build different trees without knowing the Makefiles and
scripts well enough to know what to change.  This change creates a
redhat/Makefile.variables which should be a self documented single file
to change when building with a different upstream or dist branch.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:59 -04:00
Herton R. Krzesinski d13c5a6c5d rpmspec: drop traceevent files instead of just excluding them from files list
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1967640

Even if we build perf dynamically against libtraceevent present on the system,
it still builds traceevent plugins. If we only exclude the files from
the perf package, to not conflict with libtraceevent package, its debug files
will still get included in the kernel-debuginfo package. We don't want that,
since libtraceevent already should ship plugins and its debuginfo. Thus
remove all traceevent files instead of partially excluding them through
rpm's package file list, any files there should already ship with
libtraceevent related packages.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:59 -04:00
Gustavo Walbon 855c6b4936 redhat/config: Enablement of CONFIG_PAPR_SCM for PowerPC
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1962936

Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37965649

Upstream Status: RHEL only

This CONFIG option set is needed to enable the Persistent Memory on
PowerPc.

Signed-off-by: Gustavo Walbon <gwalbon@redhat.com>
2021-08-30 15:44:59 -04:00
Fedora Kernel Team 73a8778ba9 [redhat] New configs in fs/zonefs
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ZONEFS_FS:

 zonefs is a simple file system which exposes zones of a zoned block
 device (e.g. host-managed or host-aware SMR disk drives) as files.

 If unsure, say N.

 Symbol: ZONEFS_FS [=n]
 Type  : tristate
 Defined at fs/zonefs/Kconfig:1
   Prompt: zonefs filesystem support
   Depends on: BLOCK [=y] && BLK_DEV_ZONED [=y]
   Location:
     -> File systems
 Selects: FS_IOMAP [=y] && CRC32 [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:59 -04:00
David Arcari 5227fefe7a Attempt to fix Intel PMT code 2021-08-30 15:44:59 -04:00
Fedora Kernel Team 5141c04a87 [redhat] New configs in drivers/vdpa
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VDPA_SIM_BLOCK:

 vDPA block device simulator which terminates IO request in a
 memory buffer.

 Symbol: VDPA_SIM_BLOCK [=n]
 Type  : tristate
 Defined at drivers/vdpa/Kconfig:29
   Prompt: vDPA simulator for block device
   Depends on: VDPA [=m] && VDPA_SIM [=m]
   Location:
     -> Device Drivers
       -> vDPA drivers (VDPA [=m])
         -> vDPA device simulator core (VDPA_SIM [=m])

---

 CONFIG_VDPA_SIM_NET:

 vDPA networking device simulator which loops TX traffic back to RX.

 Symbol: VDPA_SIM_NET [=n]
 Type  : tristate
 Defined at drivers/vdpa/Kconfig:22
   Prompt: vDPA simulator for networking device
   Depends on: VDPA [=m] && VDPA_SIM [=m]
   Location:
     -> Device Drivers
       -> vDPA drivers (VDPA [=m])
         -> vDPA device simulator core (VDPA_SIM [=m])
 Selects: GENERIC_NET_UTILS [=y]

---

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v3:
 - rebase
 - CONFIG_VDPA_SIM_NET remove matching fedora config
v2:
 - CONFIG_VDPA_SIM_BLOCK enabled as a module
 - CONFIG_VDPA_SIM_NET enabled as a module

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 15:44:59 -04:00
Veronika Kabatova 6b24298da7 CI: Enable realtime branch testing
Bugzilla: INTERNAL
Upstream Status: RHEL-only

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 15:44:59 -04:00
Veronika Kabatova 3f5632c5a4 CI: Enable realtime checks for c9s and RHEL9
Upstream Status: RHEL-only
Bugzilla: INTERNAL

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 15:44:58 -04:00
Fedora Kernel Team 8611b5ddce [redhat] New configs in drivers/net/ethernet/stmicro
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DWMAC_LOONGSON:

 This selects the LOONGSON PCI bus support for the stmmac driver,
 Support for ethernet controller on Loongson-2K1000 SoC and LS7A1000 bridge.

 Symbol: DWMAC_LOONGSON [=n]
 Type  : tristate
 Defined at drivers/net/ethernet/stmicro/stmmac/Kconfig:253
   Prompt: Loongson PCI DWMAC support
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=y] && STMMAC_ETH [=m] && PCI [=y] && COMMON_CLK [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
           -> STMicroelectronics devices (NET_VENDOR_STMICRO [=y])
             -> STMicroelectronics Multi-Gigabit Ethernet driver (STMMAC_ETH [=m])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:58 -04:00
Fedora Kernel Team 17b612d11c [redhat] New configs in drivers/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BATTERY_RT5033:

 This adds support for battery fuel gauge in Richtek RT5033 PMIC.
 The fuelgauge calculates and determines the battery state of charge
 according to battery open circuit voltage.

 Symbol: BATTERY_RT5033 [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:713
   Prompt: RT5033 fuel gauge support
   Depends on: POWER_SUPPLY [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])
 Selects: REGMAP_I2C [=m]

---

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:58 -04:00
Bill O'Donnell d98289485c [fs] dax: mark tech preview
Bugzilla: 1995338
Upstream Status: RHEL only
Tested: Local xfstests on ext4 and xfs with and without dax

Make sure to taint the kernel with TAINT_TECH_PREVIEW when a file
system is mounted with "-o dax".

Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
2021-08-30 15:44:58 -04:00
Peter Robinson 2418404249 ark: wireless: enable all rtw88 pcie wirless variants
We already enable a number of Realtek rtw88 pcie wifi
modules, these are widely used on a number of Edge GW
devices so also enable the 8723DE/8821CE modules too.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:58 -04:00
Peter Robinson 46ed44606c wireless: rtw88: move debug options to common/debug
The debug options shouldn't been enabled in the standard kernel. This
is already the case for ark so do the same in Fedora too.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:58 -04:00
Peter Robinson e2f13ec5fc fedora: minor PTP clock driver cleanups
A minor cleanup of the Fedora ptp configs, no functional change

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:58 -04:00
Peter Robinson 77280059b5 common: x86: enable VMware PTP support on ark
We already enable PTP support on Fedora, we would want the
VMware virtual PTP clock suppoort on ARK OSes too.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:57 -04:00
Fedora Kernel Team d808f6d662 [redhat] New configs in block/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BLK_CGROUP_IOPRIO:

 Enable the .prio interface for assigning an I/O priority class to
 requests. The I/O priority class affects the order in which an I/O
 scheduler and block devices process requests. Only some I/O schedulers
 and some block devices support I/O priorities.

 Symbol: BLK_CGROUP_IOPRIO [=n]
 Type  : bool
 Defined at block/Kconfig:165
   Prompt: Cgroup I/O controller for assigning an I/O priority class
   Depends on: BLOCK [=y] && BLK_CGROUP [=y]
   Location:
     -> Enable the block layer (BLOCK [=y])

---

Cc: Ming Lei <ming.lei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:57 -04:00
Matthias Brugger 41801bc70a arm64: dts: rockchip: Disable CDN DP on Pinebook Pro
The CDN DP needs a PHY and a extcon to work correctly. But no extcon is
provided by the device-tree, which leads to an error:
cdn-dp fec00000.dp: [drm:cdn_dp_probe [rockchipdrm]] *ERROR* missing extcon or phy
cdn-dp: probe of fec00000.dp failed with error -22

Disable the CDN DP to make graphic work on the Pinebook Pro.

Reported-by: Guillaume Gardet <guillaume.gardet@arm.com>
Signed-off-by: Matthias Brugger <mbrugger@suse.com>
2021-08-30 15:44:57 -04:00
Dan Johansen 6f37056f1e arm64: dts: rockchip: Setup USB typec port as datarole on
Some chargers try to put the charged device into device data
role. Before this commit this condition caused the tcpm state machine to
issue a hard reset due to a capability missmatch.

Signed-off-by: Dan Johansen <strit@manjaro.org>
2021-08-30 15:44:57 -04:00
Tomas Henzl de7e254b3d [scsi] megaraid_sas: re-add certain pci-ids
A rhel8 commit - 89bf8dd3c57dda93555963e60a3077534062918c
Adding CI_DEVICE_ID_LSI_SAS0079GEN2, PCI_DEVICE_ID_LSI_SAS0073SKINNY
and PCI_DEVICE_ID_LSI_SAS0071SKINNY.

Signed-off-by: Tomas Henzl <thenzl@redhat.com>
2021-08-30 15:44:57 -04:00
Bill O'Donnell e2bd746621 xfs: drop experimental warnings for bigtime and inobtcount
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1995321
Upstream Status: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git

commit f19ee6bb1a
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Fri Aug 6 11:05:44 2021 -0700

    xfs: drop experimental warnings for bigtime and inobtcount

    These two features were merged a year ago, userspace tooling have been
    merged, and no serious errors have been reported by the developers.
    Drop the experimental tag to encourage wider testing.

    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
    Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
    Reviewed-by: Bill O'Donnell <billodo@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>

Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
2021-08-30 15:44:57 -04:00
Herton R. Krzesinski 118daed79c Disable liquidio driver on ark/rhel
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1993393

liquidio driver was already disabled on Fedora, but was still being
enabled on RHEL/ark. This was enabled back in rhel8 but we got a request
to revert that later in rhel8. So there is no reason to keep it enabled
anymore in RHEL/ark too.

Disabling the driver also allowed some simplification/removal of now
uneeded config files and unification of them. While at it, I also
moved CAVIUM_PTP to m in rhel/ark as is already the case in Fedora
(afaik there is no apparent reason to keep it builtin, and was just the
result of default choice of this option looking at the option history),
and I also disabled LIQUIDIO_VF following the liquidio disabling (this
affects Fedora too where it was still enabled).

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:57 -04:00
Justin M. Forbes 14fa25ac50 More Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:56 -04:00
Prarit Bhargava b2aa3185b9 RHMAINTAINERS: Update for Aug 20 2021
Update RHMAINTAINERS.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 15:44:56 -04:00
Fedora Kernel Team 3c2c5a2448 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:56 -04:00
Justin M. Forbes 1faab122f8 Fedora config updates for 5.14
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:56 -04:00
Veronika Kabatova 6eb8590dc0 CI: Rename ARK CI pipeline type
To enable CentOS Stream double pipelines, the pipeline type check now
uses regexes. This means that both "trusted" (c9s) and "trusted-ark"
(ARK) pipelines would get picked and be executed for ARK MRs which is
not what we want. Rename the ARK pipeline type to avoid this.

Bugzilla: INTERNAL
Upstream Status: RHEL-only

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 15:44:56 -04:00
Veronika Kabatova a0692a786a CI: Finish up c9s config
The configuration for c9s was, up till now, a commented out placeholder.
The plans are finished now so we can also update the config accordingly.

We want two pipelines:

- A full c9s pipeline (build and test), publicly available
- A build for RHEL9 (RH internal only), to ensure nothing breaks (this
  should not happen, but better be safe)

Add a new anchor for RHEL build-only and the extra pipelines. As we now
have a lot of pipelines defined in this file, add comments to mark where
the actual definitions start for easier orientation.

Bugzilla: INTERNAL
Upstream Status: RHEL-only

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 15:44:56 -04:00
Veronika Kabatova c5cca77629 CI: Update ppc64le config
The RHEL container is now available so we can unify the architecture
list. We also need to specify which CKI power builder should be used,
as CKI has more of them and not all are supported for c9s/RHEL9.

Bugzilla: INTERNAL
Upstream Status: RHEL-only

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 15:44:56 -04:00
Veronika Kabatova 2a4d17cbfc CI: use more templates
Since the initial implementation, we've added a few more common options
and anchors into the kernel templates. Relevant here is .rhel_common
which we can now use, so we don't forget to update any of the options.

Also split the lines of the "extends" lists to make a visual distinction
between the common (imported) anchors and the ones defined in this CI
file.

Bugzilla: INTERNAL
Upstream Status: RHEL-only

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 15:44:56 -04:00
Justin M. Forbes 05fa6a946d Filter updates for aarch64
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:56 -04:00
Fedora Kernel Team 54f7d01292 [redhat] New configs in drivers/mtd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MTD_MCHP48L640:

 This enables access to Microchip 48L640 EERAM chips, using SPI.

 Symbol: MTD_MCHP48L640 [=n]
 Type  : tristate
 Defined at drivers/mtd/devices/Kconfig:92
   Prompt: Microchip 48L640 EERAM
   Depends on: MTD [=m] && HAS_IOMEM [=y] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> Memory Technology Device (MTD) support (MTD [=m])
         -> Self-contained MTD device drivers

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:55 -04:00
Fedora Kernel Team 8aa9affec8 [redhat] New configs in drivers/reset
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RESET_MCHP_SPARX5:

 This driver supports switch core reset for the Microchip Sparx5 SoC.

 Symbol: RESET_MCHP_SPARX5 [=n]
 Type  : bool
 Defined at drivers/reset/Kconfig:117
   Prompt: Microchip Sparx5 reset driver
   Depends on: RESET_CONTROLLER [=y] && (HAS_IOMEM [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Reset Controller Support (RESET_CONTROLLER [=y])
 Selects: MFD_SYSCON [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:55 -04:00
Chris von Recklinghausen 4e73834511 increase CONFIG_NODES_SHIFT for aarch64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1890304

Upstream status: RHEL-only

Ampere has requested that CONFIG_NODES_SHIFT be increased to allow for a larger
number of nodes on future platforms. Increase from 4 to 6 to allow for up to 32
nodes.
Signed-off-by: Chris von Recklinghausen <crecklin@redhat.com>
2021-08-30 15:44:55 -04:00
Hans de Goede 2f68636418 redhat: configs: Enable CONFIG_WIRELESS_HOTKEY
WIRELESS_HOTKEY is not new, it is a rename of the HP_WIRELESS
Kconfig symbol because the same firmware interface is now also used
on laptops from other vendors.

CONFIG_HP_WIRELESS has always been enabled in RHEL kernels and it
was in fact still enabled in 5.13.0-1.el9. So enabling
CONFIG_WIRELESS_HOTKEY basically restores the old status-quo.

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 15:44:55 -04:00
CKI Gitlab a143f8fa3f [redhat] New configs in drivers/scsi 2021-08-30 15:44:55 -04:00
Desnes A. Nunes do Rosario 7461e2e3bf redhat/configs: Update CONFIG_NVRAM
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1988254
Upstream Status: RHEL only.

Add redhat/configs for CONFIG_NVRAM on regular and debug powerpc kernels.

Signed-off-by: Desnes A. Nunes do Rosario <drosario@redhat.com>
2021-08-30 15:44:55 -04:00
Peter Robinson bac03f6d70 common: serial: build in SERIAL_8250_LPSS for x86
This is the serial driver for Intel Elkhart Lake, plus a few others,
and it needs to be built in for serial console output on x86. This
is no change for ARK, but moves this to common/generic/x86.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:55 -04:00
Diego Domingos 58ad67ba66 powerpc: enable CONFIG_FUNCTION_PROFILER
Bugzilla: http://bugzilla.redhat.com/1831065
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=38473867

Upstream Status: RHEL ONLY

Author: Diego Domingos <didoming@redhat.com>
Date: Tue, 20 Jul 2021 15:09:50 -0400

    Enabling CONFIG_FUNCTION_PROFILER

Signed-off-by: Diego Domingos <didoming@redhat.com>
2021-08-30 15:44:54 -04:00
Herbert Xu 37e0042aaf crypto: rng - Override drivers/char/random in FIPS mode
Upstream: RHEL only
Bugzilla: 1984784

This patch overrides the drivers/char/random RNGs with the FIPS
RNG from Crypto API when FIPS mode is enabled.

Signed-off-by: Herbert Xu <herbert.xu@redhat.com>
2021-08-30 15:44:54 -04:00
Herbert Xu 7734225ddd random: Add hook to override device reads and getrandom(2)
Upstream: RHEL only
Bugzilla: 1984784

This patch introduces a hook mechanism to drivers/char/random
to allow the reads on /dev/*random as well as getrandom(2) to
be overridden by an external RNG.

This will be used to override drivers/char/random with a FIPS
RNG in a subsequent patch.

Signed-off-by: Herbert Xu <herbert.xu@redhat.com>
2021-08-30 15:44:54 -04:00
Kamal Heib 3b3f6819b6 redhat/configs: Disable Soft-RoCE driver
We decided to disable the Soft-RoCE driver due to the current unstable
status of the driver in the upstream kernel, also because the driver is
not fully maintained in the upstream community.

Upstream: RHEL-only.

Signed-off-by: Kamal Heib <kheib@redhat.com>
2021-08-30 15:44:54 -04:00
Justin M. Forbes 2340000e94 update filters for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:54 -04:00
Prarit Bhargava 6933d4ffc5 redhat/configs/evaluate_configs: Update help output
Fix a typo with the .rhel priority in the output, and fix a tab issue.

Update the help output.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 15:44:54 -04:00
Justin M. Forbes 1f9f29c4d4 redhat/configs: Double MAX_LOCKDEP_CHAINS
https://bugzilla.redhat.com/show_bug.cgi?id=1989983

MAX_LOCKDEP_CHAINS is controlled by LOCKDEP_CHAINS_BITS. We are running
into issues with the default of 16, so let's move it to 17 and double
the MAX_LOCKDEP_CHAINS from 64K to 128K.

CONFIG_LOCKDEP_CHAINS_BITS isn't used in generic kernel. It is only used
in debug kernels where CONFIG_PROVE_LOCKING is turned on.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:54 -04:00
Hans de Goede 80877b9d72 fedora: configs: Fix WM5102 Kconfig
Commit 0ec8e4cdd8 ("Build Fedora x86s kernels with bytcr-wm5102"),
tried to enable support for audio on x86_64 device with a WM5102 codec.

But it enabled the CONFIG_MFD_ARIZONA symbol, which is not
user-selectable, so setting it in the fedora config is not necessary
and is in essence a no-op.

The CONFIG_MFD_ARIZONA gets automatically selected as necessary by the
CONFIG_MFD_ARIZONA_I2C/CONFIG_MFD_ARIZONA_SPI Kconfig options.

The x86_64 devices with a WM5102 codec, all use the SPI bus, so this
commit enables CONFIG_MFD_ARIZONA_SPI=m. This commit also a whole bunch
of other symbols which depend on CONFIG_MFD_ARIZONA and thus now
become available. Those necessary for supporting these x86_64 devices
are set to 'm' the rest is left disabled.

Starting with 5.14-rc1 all of the Arizona code can be built as a module
so enabling this will not grow the bzImage size.

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 15:44:54 -04:00
Diego Domingos 54a95aac06 powerpc: enable CONFIG_POWER9_CPU
Bugzilla: http://bugzilla.redhat.com/1876436
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=38753678
Upstream Status: RHEL ONLY

This patch enables CONFIG_POWER9_CPU and disable CONFIG_GENERIC_CPU for
powerpc.

Signed-off-by: Diego Domingos <didoming@redhat.com>
2021-08-30 15:44:54 -04:00
Eric Auger dc9b487055 redhat/configs: Fix CONFIG_VIRTIO_IOMMU to 'y' on aarch64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1972795
Upstream Status: RHEL only
Tested: on ARM with qemu (Jean-Philippe Brucker's qemu branch as the
qemu integration is not yet upstream, with both protected virtio-blk-pci
and a virtio-net-pci devices)

Commit fe6d9534db ("redhat/configs: Set CONFIG_VIRTIO_IOMMU on aarch64")
enabled the compilation of the virtio-iommu driver on ARM but set the
config to 'm'. However if there are devices behind the vIOMMU that are
needed during the boot such as a virtio-blk-pci device, the guest fails
to boot as the driver is not loaded. Let's fix this bootstrap issue
by compiling the driver in-kernel as it is done for other iommu drivers.

Signed-off-by: Eric Auger <eric.auger@redhat.com>
2021-08-30 15:44:54 -04:00
Prarit Bhargava 86d5a0a163 RHMAINTAINERS: Update for Aug 6 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 15:44:53 -04:00
Fedora Kernel Team 1f4eeac486 [redhat] New configs in drivers/crypto
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CRYPTO_DEV_SL3516:

 This option allows you to have support for SL3516 crypto offloader.

 Symbol: CRYPTO_DEV_SL3516 [=n]
 Type  : tristate
 Defined at drivers/crypto/Kconfig:269
   Prompt: Stormlink SL3516 crypto offloader
   Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && HAS_IOMEM [=y] && PM [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Hardware crypto devices (CRYPTO_HW [=y])
 Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_ENGINE [=n] && CRYPTO_ECB [=y] && CRYPTO_AES [=y] && HW_RANDOM [=y]

---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:53 -04:00
Jaroslav Kysela fa8ece4b35 filter-modules.sh: add more sound modules to filter
- add regmap-sdw[-mbq] and arizona-micsupp modules
- add drivers/soundwire directory

Signed-off-by: Jaroslav Kysela <jkysela@redhat.com>
2021-08-30 15:44:53 -04:00
Jaroslav Kysela b389f5e732 redhat/configs: sound configuration cleanups and updates
Ensure that the ARK configuration follows RHEL 8.5. Especially
the Intel SoundWire drivers were not included and many Intel SOF
driver configurations were not in sync.

Also use power save settings for HDA and AC97 drivers from Fedora.
Hopefully, the drivers are fixed now (the problematic hardware
is detected automatically and the power save is turned off unless
the user force this functionality).

The patchset contains also many cleanups (reshuffling) for common tree
for CONFIG_SND and CONFIG_SOUNDWIRE configuration options.

Signed-off-by: Jaroslav Kysela <jkysela@redhat.com>
2021-08-30 15:44:53 -04:00
Fedora Kernel Team 43b2c035d0 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 Symbol: SND_SOC_SSM2518 [=n]
 Type  : tristate
 Defined at sound/soc/codecs/Kconfig:1327
   Prompt: Analog Devices SSM2518 Class-D Amplifier
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> CODEC drivers
 Implied by [n]:
   - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:53 -04:00
CKI Gitlab 22a2faf15f [redhat] New configs in net/netfilter 2021-08-30 15:44:53 -04:00
Peter Robinson 7969943ac1 common: Update for CXL (Compute Express Link) configs
The Compute Express Link is based upon PCI and is a faster
interconnect that will be supported across most modern
architectures so have a single common config.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:52 -04:00
Herton R. Krzesinski 0b06637a8b redhat: configs: disable CRYPTO_SM modules
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1990040

We can't build/ship these modules after export control compliance
review. This was raised in PELC review for RHEL 9.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:52 -04:00
Justin M. Forbes 2a4b987105 Remove fedora version of the LOCKDEP_BITS, we should use common
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:52 -04:00
Justin M. Forbes 19925bde48 Re-enable sermouse for x86 (rhbz 1974002)
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:52 -04:00
Justin M. Forbes 88d327049f Fedora 5.14 configs round 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:52 -04:00
Herton R. Krzesinski 1f3328f35b redhat: add gating configuration for centos stream/rhel9
Right now when we do the dist-git sync, it overrides/deletes everything
which is not on the src.rpm, which might delete any gating configuration
on dist-git. Make sure we always copy the gating configuration for
centos/rhel9. This might need some tweak later if Fedora or future RHEL
uses the same gating file but with different config.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:52 -04:00
Vladis Dronov 3911ede0cc [redhat] Enable CONFIG_RANDOM_TRUST_CPU for all the arches
Many modern cloud instance types have hardware with RDRAND, but the RHEL-9
still do not use it. Enable CONFIG_RANDOM_TRUST_CPU the same way as in the
RHEL-8 and Fedora and add ARM too.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976877
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 15:44:51 -04:00
Vitaly Kuznetsov 9fd46c785b x86: configs: Enable CONFIG_TEST_FPU for debug kernels
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1988384

CONFIG_TEST_FPU selftest is needed to test in-kernel FPU usage.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
2021-08-30 15:44:51 -04:00
root 5639c05df6 redhat/configs: Move CHACHA and POLY1305 to core kernel to allow BIG_KEYS=y
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1983298
Upstream: Config only
Testing: keyutils testsuite

The big-key key type is a bool as it's expected to be built into the core
kernel, however it requires ChaCha20Poly1305 crypto to function.
Currently, the crypto bits are built as modules, so BIG_KEYS doesn't even
get enabled.  BIG_KEYS does a depends-on in Kconfig because using select is
non-transitive and all the dependencies would need selecting - but that's a
variable list, depending on arch.

Fix this by setting the arch-specific ChaCha20 and Poly1305 deps to =y as
well as the direct crypto library modules required by BIG_KEYS.  BIG_KEYS
is already set to =y so that then becomes available automatically.

This was detected by the keyutils testsuite trying to create a big key.

Signed-off-by: David Howells <dhowells@redhat.com>
2021-08-30 15:44:51 -04:00
Jiri Benc f34c503a71 kernel.spec: fix build of samples/bpf
Due to some change of the kernel makefiles, "samples/bpf" does not work
anymore as a make target. Use M= instead.

Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 15:44:51 -04:00
Jerome Marchand 0fa452f0c6 Enable OSNOISE_TRACER and TIMERLAT_TRACER
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1979379

There is actually a need for these tracers.

Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
2021-08-30 15:44:51 -04:00
Herton R. Krzesinski 45e42a0d33 rpmspec: switch iio and gpio tools to use tools_make
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1956988

In the past, some of the kernel tools Makefiles didn't allow the override of
CFLAGS, which made them compiled without stack protector and without position
independent code. This triggers CI failures in RHEL with annocheck.

However, since upstream commits 4ccc98a489
(tools gpio: Allow overriding CFLAGS) and 5729746102
(tools iio: Override CFLAGS assignments), we can override the
compiler flags, so just convert the build of iio and gpio tools to
use tools_make macro as other tools, which passes the correct CFLAGS.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:51 -04:00
Fedora Kernel Team 24a7b1aee7 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:51 -04:00
Fedora Kernel Team 2b886c3658 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:51 -04:00
Patrick Talbert 99175440bd configs/process_configs.sh: Handle config items with no help text
The current config scripts logic expects the helpnewconfig output for
each item to begin with the full config item name followed by a colon.
But if a config item has no help text then the helpnewconfig output does
not follow this format.

Fix this by adjusting the process_configs.sh and gen_config_patches.sh
awk scripts so they get the config item name from the Symbol: line which
is always present in helpnewconfig output

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 15:44:51 -04:00
Peter Robinson f7991d313f fedora: sound config updates for 5.14
Some sound config updates for Fedora.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:50 -04:00
Peter Robinson 47c47ce452 fedora: Only enable FSI drivers on POWER platform
The FSI interface is a POWER specific interface used for BMCs
so only enable it on POWER configs.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:50 -04:00
Peter Robinson 9a9af79693 The CONFIG_RAW_DRIVER has been removed from upstream
No functional change

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:50 -04:00
Peter Robinson c07e1a81d6 fedora: updates for 5.14 with a few disables for common from pending
The changes in common are just disables from pending/common. The
rest are updates for Fedora config updates.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:50 -04:00
Peter Robinson 171b8f8be3 fedora: migrate from MFD_TPS68470 -> INTEL_SKL_INT3472
This is only used on x86 chromebooks for a PMIC for some camera
interfaces so we don't need to support it anywhere else. Let's
migrate from the deleted drivers to the new one. The
MFD_TPS68470 driver has been deleted so no functional change
elsewhere.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:50 -04:00
Peter Robinson d896ac62a7 fedora: Remove STAGING_GASKET_FRAMEWORK
It was removed from upstream staging so can be dropped.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:50 -04:00
Peter Robinson 543d567bf5 Fedora: move DRM_VMWGFX configs from ark -> common
This moved DRM_VMWGFX to common so Fedora can consume the VMWare
Graphics driver too.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:49 -04:00
Peter Robinson 26ed8fa4e5 fedora: arm: disabled unused FB drivers
The FB_XILINX driver isn't used on any of the Xilinx HW we support,
whereas the FB_ARMCLCD driver has long been replaced by DRM_PL111 and
it was only still enabled in Fedora by mistake.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:49 -04:00
Peter Robinson d6bcaa7a82 fedora: don't enable FB_VIRTUAL
The FB_VIRTUAL is for FB stack development, it shouldn't be enabled
in a standard distro kernel.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:49 -04:00
Waiman Long f35c7c360a redhat/configs: Double MAX_LOCKDEP_ENTRIES
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1940075
Upstream: RHEL only

MAX_LOCKDEP_ENTRIES in lockdep is controlled by CONFIG_LOCKDEP_BITS. By
increasing it from a default of 15 to 16, we double MAX_LOCKDEP_ENTRIES
from 32k to 64k. That should be big enough for our internal use by our
QE.

CONFIG_LOCKDEP_BITS isn't used in generic kernel. It is only used
in debug kernel when CONFIG_LOCKDEP is turned on by the enabling of
CONFIG_PROVE_LOCKING.

Signed-off-by: Waiman Long <longman@redhat.com>
2021-08-30 15:44:49 -04:00
Herton R. Krzesinski a48245fe1d rpmspec: fix verbose output on kernel-devel installation
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1981406

The current hardlink implementation that is available on latest
util-linux versions (at least >= 2.37) is verbose by default. Thus
lots of output is printed when hardlink runs at the kernel-devel
install with newer hardlink versions. Avoid that by redirecting
the output to /dev/null. I also could use the -q option, but that
may not be available with hardlink versions eg. on older stable Fedora
versions where current kernels might still be built for them, so the
redirection seems the safest approach.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:49 -04:00
Marius Hoch 86004fa685 Build Fedora x86s kernels with bytcr-wm5102 2021-08-30 15:44:49 -04:00
Patrick Lang 1a76c9ca2f Deleted redhat/configs/fedora/generic/x86/CONFIG_FB_HYPERV 2021-08-30 15:44:49 -04:00
Herton R. Krzesinski 27aa84cdd1 rpmspec: correct the ghost initramfs attributes
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1977056

This is a cherry pick from the following rhel-8 change into kernel-ark:

commit 88049ff66893839cb85731db809b1ba47a3a23f3
Author: Rafael Aquini <aquini@redhat.com>
Date:   Tue Jun 25 19:25:09 2019 -0400

    [rpmspec] correct the ghost initramfs attributes

    Message-id: <0d44bbb391ffd1cee003581ffffb93ad315b4e27.1561490617.git.aquini@redhat.com>
    Patchwork-id: 265851
    O-Subject: [RHEL8 PATCH] redhat: spec: correct the ghost initramfs attributes
    Bugzilla: 1678881
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Jan Stancek <jstancek@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1678881
    Upstream Status: RHEL only
    Build Info: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=22353984

    This patch is a forward port of the following RHEL-7 commit:
    commit f9e549645b10405f8b12f07649327ea293a5a78a
    Author: Kyle Walker <kwalker@redhat.com>
    Date:   Mon Feb 4 19:11:11 2019 -0500

        [redhat] spec: Correct the ghost initramfs attributes

        Message-id: <20190204191110.4217-1-kwalker@redhat.com>
        Patchwork-id: 239860
        O-Subject: [RHEL7 BZ 1571909] spec: Correct the ghost initramfs attributes
        Bugzilla: 1571909
        RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
        RH-Acked-by: Jarod Wilson <jarod@redhat.com>
        RH-Acked-by: Patrick Talbert <ptalbert@redhat.com>

        Bugzilla: 1571909
        Message-id: <20190204191110.4217-1-kwalker@redhat.com>
        Patchwork-id: 239860
        O-Subject: [RHEL7 BZ 1571909] spec: Correct the ghost initramfs attributes
        Bugzilla: 1571909
        RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
        RH-Acked-by: Jarod Wilson <jarod@redhat.com>
        RH-Acked-by: Patrick Talbert <ptalbert@redhat.com>

        Bugzilla: 1571909
        Upstream Status: RHEL only
        Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=20067072

        The initramfs ghost directive doesn't include the necessary attributes
        macro. When generating the initramfs, dracut sets the umask to 0077, which
        will result in 0600 as shown below.

            # dracut -f 2>/dev/null 1>&2
            # ls -l /boot/initramfs-3.10.0-957.1.3.el7.x86_64.img
            -rw-------. 1 root root 21266044 Feb  4 12:09 /boot/initramfs-3.10.0-957.1.3.el7.x86_64.img

        But this doesn't match the specfile which currently assumes 0644 and
        results in RPM verification failures.

            # rpm -V kernel
            .M.......  g /boot/initramfs-3.10.0-957.1.3.el7.x86_64.img

        The issue was masked in previous releases as ghost directives were never
        properly verified as indicated in BZ1395818. Resolved by applying a 0600
        attribute set for ghost initramfs entries.

        Signed-off-by: Kyle Walker <kwalker@redhat.com>
        Signed-off-by: Jan Stancek <jstancek@redhat.com>

    Signed-off-by: Rafael Aquini <aquini@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:48 -04:00
Herton R. Krzesinski 67fff586c4 rpmspec: amend removal of depmod created files to include modules.builtin.alias.bin
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1977056

Right now we don't remove the file modules.builtin.alias.bin from the
list of depmod files we already remove at the kernel build time. This
makes it being included in the kernel-core package and being listed
with rpm -V output, eg.:

$ rpm -V kernel-core
(...)
.......T.    /lib/modules/5.14.0-0.rc2.23.el9.x86_64/modules.builtin.alias.bin

I just redid the removal command to explicitly call each file created by depmod.
We could by mistake do a glob like modules.builtin.* which would wrongly include
modules.builtin.modinfo for example, so seems safest to do it this way. While at
it I removed the *map glob which may be was needed in the past (may
be very distant past?) but this file is not created anymore. I manually
verified the amended list to what is in kmod sources at tools/depmod.c,
at the depmod_output() function.

This also removes the duplicated removal calls, instead of having to
modify two places, just do a single function and call it in the two places
it's needed.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:48 -04:00
Patrick Talbert bb2eee7a73 configs: remove duplicate CONFIG_DRM_HYPERV file
CONFIG_DRM_HYPERV was set for x86 by !1259 and then for everyone by
!1213. It is only needed for x86 so remove the less specific one.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 15:44:48 -04:00
Patrick Talbert 4f95bbf275 [redhat] configs: Enable CONFIG_DRM_HYPERV as a module
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 15:44:48 -04:00
Fedora Kernel Team 5a311453d4 [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DRM_HYPERV:

 This is a KMS driver for Hyper-V synthetic video device. Choose this
 option if you would like to enable drm driver for Hyper-V virtual
 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so
 that DRM driver is used by default.

 If M is selected the module will be called hyperv_drm.

 Symbol: DRM_HYPERV [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/Kconfig:382
   Prompt: DRM Support for Hyper-V synthetic video device
   Depends on: HAS_IOMEM [=y] && DRM [=m] && PCI [=y] && MMU [=y] && HYPERV [=m]
   Location:
     -> Device Drivers
       -> Graphics support
 Selects: DRM_KMS_HELPER [=m] && DRM_GEM_SHMEM_HELPER [=y]

---

 CONFIG_DRM_ITE_IT66121:

 Support for ITE IT66121 HDMI bridge.

 Symbol: DRM_ITE_IT66121 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:121
   Prompt: ITE IT66121 HDMI bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]

---

 CONFIG_DRM_SIMPLEDRM:

 DRM driver for simple platform-provided framebuffers.

 This driver assumes that the display hardware has been initialized
 by the firmware or bootloader before the kernel boots. Scanout
 buffer, size, and display format must be provided via device tree,
 UEFI, VESA, etc.

 On x86 and compatible, you should also select CONFIG_X86_SYSFB to
 use UEFI and VESA framebuffers.

 Symbol: DRM_SIMPLEDRM [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/tiny/Kconfig:41
   Prompt: Simple framebuffer driver
   Depends on: HAS_IOMEM [=y] && DRM [=m]
   Location:
     -> Device Drivers
       -> Graphics support
 Selects: DRM_GEM_SHMEM_HELPER [=y] && DRM_KMS_HELPER [=m]

---

 CONFIG_DRM_TI_SN65DSI83:

 Texas Instruments SN65DSI83 and SN65DSI84 DSI to LVDS Bridge driver

 Symbol: DRM_TI_SN65DSI83 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:288
   Prompt: TI SN65DSI83 and SN65DSI84 DSI to LVDS bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]

---

 CONFIG_HSA_AMD_SVM:

 Enable this to use unified memory and managed memory in HIP. This
 memory manager supports two modes of operation. One based on
 preemptions and one based on page faults. To enable page fault
 based memory management on most GFXv9 GPUs, set the module
 parameter amdgpu.noretry=0.

 Symbol: HSA_AMD_SVM [=y]
 Type  : bool
 Defined at drivers/gpu/drm/amd/amdkfd/Kconfig:16
   Prompt: Enable HMM-based shared virtual memory manager
   Depends on: HAS_IOMEM [=y] && HSA_AMD [=y] && DEVICE_PRIVATE [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> AMD GPU (DRM_AMDGPU [=m])
           -> HSA kernel driver for AMD GPU devices (HSA_AMD [=y])
 Selects: HMM_MIRROR [=y] && MMU_NOTIFIER [=y]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:48 -04:00
Don Zickus e5e77fd040 CI: use common code for merge and release
Small cleanup to simplify code by re-using duplicated sections through
extends.

Also remove legacy config branch push (now done through merge_upstream).

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 15:44:48 -04:00
Jan Stancek 78a13478b8 rpmspec: add release string to kernel doc directory name
https://fedoraproject.org//wiki/Changes/UnversionedDocdirs says:
  Packages for which multiple versions are intended to be installed need to
  be changed to install their docs into appropriately versioned subdirs.

kernel docs are currently installed to /usr/share/doc/kernel-doc-$VERSION
(for example: /usr/share/doc/kernel-doc-5.14.0), which prevents user
from having kernel docs installed for multiple releases if they happen
to share same $VERSION. This is more visible in downstream releases,
where $VERSION is same for entire lifetime of stream.

This patch adds $RELEASE to kernel doc directory name to allow installing
multiple versions in parallel.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
2021-08-30 15:44:48 -04:00
Michael Petlan 12f99f62c7 redhat/configs: Add CONFIG_INTEL_PMT_CRASHLOG
Bugzilla: http://bugzilla.redhat.com/1880486
Upstream Status: RHEL only.

Add redhat/configs for new CONFIG_INTEL_PMT_CRASHLOG.

Autogenerated & verified by editconfig.

Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 15:44:48 -04:00
Michael Petlan bd880b0b0a redhat/configs: Add CONFIG_INTEL_PMT_TELEMETRY
Bugzilla: http://bugzilla.redhat.com/1880486
Upstream Status: RHEL only.

Add redhat/configs for new CONFIG_INTEL_PMT_TELEMETRY.

Autogenerated & verified by editconfig.

Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 15:44:48 -04:00
Michael Petlan 4e7568dac5 redhat/configs: Add CONFIG_MFD_INTEL_PMT
Bugzilla: http://bugzilla.redhat.com/1880486
Upstream Status: RHEL only.

Add redhat/configs for new CONFIG_MFD_INTEL_PMT.

Autogenerated & verified by editconfig.

Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 15:44:47 -04:00
Fedora Kernel Team f2bb1ab254 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:47 -04:00
Ming Lei f6d9c3d99d redhat/configs: enable CONFIG_BLK_DEV_ZONED
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1638087

This option has been enabled in Fedora already.

Also it is mentioned in this BZ that 'our current plan is to enable this
in RHEL 9 first', so enable this option in redhat/configs/common so that
people can use ZNS via userspace or play it via nvme-cli.

Signed-off-by: Ming Lei <ming.lei@redhat.com>
2021-08-30 15:44:47 -04:00
Fedora Kernel Team c138474717 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_STACKTRACE_BUILD_ID:

 Selecting this option adds build ID information for symbols in
 stacktraces printed with the printk format '%p[SR]b'.

 This option is intended for distros where debuginfo is not easily
 accessible but can be downloaded given the build ID of the vmlinux or
 kernel module where the function is located.

 Symbol: STACKTRACE_BUILD_ID [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:38
   Prompt: Show build ID information in stacktraces
   Depends on: PRINTK [=y]
   Location:
     -> Kernel hacking
       -> printk and dmesg options

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Christoph von Recklinghausen <crecklin@redhat.com>
Cc: Eugene Syromiatnikov <esyromia@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Oleg Nesterov <onestero@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:47 -04:00
Tom Stellard bd969d138b Add --with clang_lto option to build the kernel with Link Time Optimizations
This also requires the --with toolchain_clang option in order to be
fully enabled.  Currently only supported with x86_64 and aarch64.

As a part of this change, the process_configs.sh script has been updated
so that it can be passed additional make options via the -m flag.  The
LTO related config options depend on CONFIG_CC_IS_CLANG, and so the make
invocations in this script need to be passed CC=clang in order for the LTO
options to be enabled.

Signed-off-by: Tom Stellard <tstellar@redhat.com>
2021-08-30 15:44:47 -04:00
Peter Robinson 7c85ed9ff0 common: disable DVB_AV7110 and associated pieces
Upstream is preparing to remove DVB_AV7110 as it only supports
MPEG2 and most DVB stream require newer codecs, and has other
issues. Upstream commits are 989cf18 and b998a59.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:47 -04:00
Don Zickus d4922c0952 Fix fedora-only config updates
After every scheduled upstream merge, a script is run to find new
configs, generate pending-* files for them and for ark, create
branches to push MRs.

However, there is a case where new Fedora configs are found but not
new ARK configs.  This case had issues.

When the merge is done, make dist-configs-commit is called for Fedora
and RHEL.  This results in a possible new commit if configs are found.

The command is run twice and creates the following matrix:

1. Both Fedora and RHEL have new configs.
2. Neither Fedora nor RHEL have new configs.
3. Fedora does not have new configs, but RHEL does.
4. Fedora has new configs, bug RHEL does not.

1 and 2 are common and 1-3 are handled correctly.

Scenario 4 is not.

When the configs are committed, the next script gen_config_patches.sh
looks for a special commit 'AUTOMATIC'.  It doesn't care if that commit
comes from Fedora or RHEL.

The gen_config_patches.sh can not handle pending-fedora changes, so
those changes are filtered in the script.

In scenario 4 that leaves an empty file to process, which the script
aborts on.  Further no print out was displayed which slowed down
debugging.

The are multiple ways to address this.  This patch does multiple things.

* Adds a print statement on the failure for future debugging.
* Exits on success if there are no changes to process after filtering.
* Reduces the risk of calling gen_config_patches.sh by only calling
  the script when RHEL adds new configs.

Tested scenario 4 with last week's os-build HEAD.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 15:44:47 -04:00
Justin M. Forbes b750f4c76f Fedor config update for new option
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:47 -04:00
Fedora Kernel Team c03d31158d [redhat] New configs in kernel/trace
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_OSNOISE_TRACER:

 In the context of high-performance computing (HPC), the Operating
 System Noise (osnoise) refers to the interference experienced by an
 application due to activities inside the operating system. In the
 context of Linux, NMIs, IRQs, SoftIRQs, and any other system thread
 can cause noise to the system. Moreover, hardware-related jobs can
 also cause noise, for example, via SMIs.

 The osnoise tracer leverages the hwlat_detector by running a similar
 loop with preemption, SoftIRQs and IRQs enabled, thus allowing all
 the sources of osnoise during its execution. The osnoise tracer takes
 note of the entry and exit point of any source of interferences,
 increasing a per-cpu interference counter. It saves an interference
 counter for each source of interference. The interference counter for
 NMI, IRQs, SoftIRQs, and threads is increased anytime the tool
 observes these interferences' entry events. When a noise happens
 without any interference from the operating system level, the
 hardware noise counter increases, pointing to a hardware-related
 noise. In this way, osnoise can account for any source of
 interference. At the end of the period, the osnoise tracer prints
 the sum of all noise, the max single noise, the percentage of CPU
 available for the thread, and the counters for the noise sources.

 In addition to the tracer, a set of tracepoints were added to
 facilitate the identification of the osnoise source.

 The output will appear in the trace and trace_pipe files.

 To enable this tracer, echo in "osnoise" into the current_tracer
 file.

 Symbol: OSNOISE_TRACER [=n]
 Type  : bool
 Defined at kernel/trace/Kconfig:359
   Prompt: OS Noise tracer
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])
 Selects: GENERIC_TRACER [=y]
 Selected by [n]:
   - TIMERLAT_TRACER [=n] && TRACING_SUPPORT [=y] && FTRACE [=y]

---

 CONFIG_TIMERLAT_TRACER:

 The timerlat tracer aims to help the preemptive kernel developers
 to find sources of wakeup latencies of real-time threads.

 The tracer creates a per-cpu kernel thread with real-time priority.
 The tracer thread sets a periodic timer to wakeup itself, and goes
 to sleep waiting for the timer to fire. At the wakeup, the thread
 then computes a wakeup latency value as the difference between
 the current time and the absolute time that the timer was set
 to expire.

 The tracer prints two lines at every activation. The first is the
 timer latency observed at the hardirq context before the
 activation of the thread. The second is the timer latency observed
 by the thread, which is the same level that cyclictest reports. The
 ACTIVATION ID field serves to relate the irq execution to its
 respective thread execution.

 The tracer is build on top of osnoise tracer, and the osnoise:
 events can be used to trace the source of interference from NMI,
 IRQs and other threads. It also enables the capture of the
 stacktrace at the IRQ context, which helps to identify the code
 path that can cause thread delay.

 Symbol: TIMERLAT_TRACER [=n]
 Type  : bool
 Defined at kernel/trace/Kconfig:393
   Prompt: Timerlat tracer
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])
 Selects: OSNOISE_TRACER [=n] && GENERIC_TRACER [=y]

---

Cc: Jerome Marchand <jmarchan@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:46 -04:00
Fedora Kernel Team 86a227e2c6 [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FXLS8962AF_I2C:

 Say yes here to build support for the NXP 3-axis automotive
 accelerometer FXLS8962AF/FXLS8964AF with I2C support.

 To compile this driver as a module, choose M here: the module
 will be called fxls8962af_i2c.

 Symbol: FXLS8962AF_I2C [=n]
 Type  : tristate
 Defined at drivers/iio/accel/Kconfig:235
   Prompt: NXP FXLS8962AF/FXLS8964AF Accelerometer I2C Driver
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Accelerometers
 Selects: FXLS8962AF [=n] && REGMAP_I2C [=m]

---

 CONFIG_FXLS8962AF_SPI:

 Say yes here to build support for the NXP 3-axis automotive
 accelerometer FXLS8962AF/FXLS8964AF with SPI support.

 To compile this driver as a module, choose M here: the module
 will be called fxls8962af_spi.

 Symbol: FXLS8962AF_SPI [=n]
 Type  : tristate
 Defined at drivers/iio/accel/Kconfig:247
   Prompt: NXP FXLS8962AF/FXLS8964AF Accelerometer SPI Driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Accelerometers
 Selects: FXLS8962AF [=n] && REGMAP_SPI [=m]

---

 CONFIG_IIO_ST_LSM9DS0:

 Say yes here to build support for STMicroelectronics LSM9DS0 IMU
 sensor. Supported devices: accelerometer/magnetometer of lsm9ds0.

 To compile this driver as a module, choose M here: the module
 will be called st_lsm9ds0.

 Symbol: IIO_ST_LSM9DS0 [=n]
 Type  : tristate
 Defined at drivers/iio/imu/st_lsm9ds0/Kconfig:3
   Prompt: STMicroelectronics LSM9DS0 IMU driver
   Depends on: IIO [=m] && (I2C [=y] || SPI_MASTER [=y]) && SYSFS [=y] && !SENSORS_LIS3_I2C [=m] && !SENSORS_LIS3_SPI [=n]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Inertial measurement units
 Selects: IIO_ST_LSM9DS0_I2C [=n] && IIO_ST_LSM9DS0_SPI [=n] && IIO_ST_ACCEL_3AXIS [=n] && IIO_ST_MAGN_3AXIS [=n]

---

 CONFIG_SCA3300:

 Say yes here to build support for Murata SCA3300 3-Axis
 accelerometer.

 To compile this driver as a module, choose M here: the module will be
 called sca3300.

 Symbol: SCA3300 [=n]
 Type  : tristate
 Defined at drivers/iio/accel/Kconfig:482
   Prompt: Murata SCA3300 3-Axis Accelerometer Driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Accelerometers
 Selects: CRC8 [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

 CONFIG_SPS30_I2C:

 Say Y here to build support for the Sensirion SPS30 I2C interface
 driver.

 To compile this driver as a module, choose M here: the module will
 be called sps30_i2c.

 Symbol: SPS30_I2C [=n]
 Type  : tristate
 Defined at drivers/iio/chemical/Kconfig:139
   Prompt: SPS30 particulate matter sensor I2C driver
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Chemical Sensors
 Selects: SPS30 [=n] && CRC8 [=m]

---

 CONFIG_TI_TSC2046:

 Say yes here to build support for ADC functionality of Texas
 Instruments TSC2046 touch screen controller.

 This driver can also be built as a module. If so, the module will be
 called ti-tsc2046.

 Symbol: TI_TSC2046 [=n]
 Type  : tristate
 Defined at drivers/iio/adc/Kconfig:1193
   Prompt: Texas Instruments TSC2046 ADC driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

 CONFIG_TMP117:

 If you say yes here you get support for the Texas Instruments
 TMP117 Digital temperature sensor with integrated NV memory.

 This driver can also be built as a module. If so, the module will
 be called tmp117.

 Symbol: TMP117 [=n]
 Type  : tristate
 Defined at drivers/iio/temperature/Kconfig:99
   Prompt: TMP117 Digital temperature sensor with integrated NV memory
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Temperature sensors

---

 CONFIG_TSL2591:

 Select Y here for support of the AMS/TAOS TSL2591 ambient light sensor,
 featuring channels for combined visible + IR intensity and lux illuminance.
 Access data via iio and sysfs. Supports iio_events.

 To compile this driver as a module, select M: the
 module will be called tsl2591.

 Symbol: TSL2591 [=n]
 Type  : tristate
 Defined at drivers/iio/light/Kconfig:502
   Prompt: TAOS TSL2591 ambient light sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Light sensors

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:46 -04:00
Fedora Kernel Team 9f0dae5ac2 [redhat] New configs in drivers/clk
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_COMMON_CLK_HI3559A:

 Build the clock driver for hi3559a.

 Symbol: COMMON_CLK_HI3559A [=y]
 Type  : bool
 Defined at drivers/clk/hisilicon/Kconfig:18
   Prompt: Hi3559A Clock Driver
   Depends on: COMMON_CLK [=y] && (ARCH_HISI [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Common Clock Framework (COMMON_CLK [=y])

---

 CONFIG_LMK04832:

 Say yes here to build support for Texas Instruments' LMK04832 Ultra
 Low-Noise JESD204B Compliant Clock Jitter Cleaner With Dual Loop PLLs

 Symbol: LMK04832 [=n]
 Type  : tristate
 Defined at drivers/clk/Kconfig:54
   Prompt: Ti LMK04832 JESD204B Compliant Clock Jitter Cleaner
   Depends on: COMMON_CLK [=y] && SPI [=y]
   Location:
     -> Device Drivers
       -> Common Clock Framework (COMMON_CLK [=y])
 Selects: REGMAP_SPI [=m]

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v3:
 - CONFIG_COMMON_CLK_HI3559A enabled for fedora.
v2:
 - CONFIG_COMMON_CLK_HI3559A moved to arm/aarch64 and disabled.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 15:44:46 -04:00
Mark Salter 67368496da redhat/configs: Enable stmmac NIC for x86_64
Turn on DWMAC_INTEL for x86_64.

 Also adds files for:
    CONFIG_NET_VENDOR_STMICRO
    CONFIG_PCS_XPCS
    CONFIG_PHYLINK
    CONFIG_RESET_CONTROLLER
    CONFIG_SFP
    CONFIG_STMMAC_ETH
    CONFIG_STMMAC_PCI
    CONFIG_STMMAC_PLATFORM
    CONFIG_STMMAC_SELFTESTS

Signed-off-by: Mark Salter <msalter@redhat.com>
2021-08-30 15:44:46 -04:00
Peter Robinson 59c9e61a55 all: hyperv: use the DRM driver rather than FB
The Linux framebuffer device stack is EOL so we should use the
HyperV drm driver rather than the FB driver.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:46 -04:00
Peter Robinson e41d03c816 all: hyperv: unify the Microsoft HyperV configs
There's no functional change here for either ARK or Fedora as the
configs were the same, this just cleans them up and unifies them
for easier mangmement.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:46 -04:00
Peter Robinson f30cdb9bb6 all: VMWare: clean up VMWare configs
Unify the VMware configuration across ark/fedora, purely de-dupe.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:46 -04:00
Patrick Talbert 9978c3f3b8 Update CONFIG_ARM_FFA_TRANSPORT 2021-08-30 15:44:45 -04:00
Fedora Kernel Team 60910fcb3b [redhat] New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_FFA_TRANSPORT:

 This Firmware Framework(FF) for Arm A-profile processors describes
 interfaces that standardize communication between the various
 software images which includes communication between images in
 the Secure world and Normal world. It also leverages the
 virtualization extension to isolate software images provided
 by an ecosystem of vendors from each other.

 This driver provides interface for all the client drivers making
 use of the features offered by ARM FF-A.

 Symbol: ARM_FFA_TRANSPORT [=n]
 Type  : tristate
 Defined at drivers/firmware/arm_ffa/Kconfig:2
   Prompt: Arm Firmware Framework for Armv8-A
   Depends on: OF [=y] && ARM64 [=y]
   Location:
     -> Firmware Drivers

---

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:45 -04:00
Veronika Kabatova a83f6a318d CI: Handle all mirrors
Add CI for mirrored c9s and future RHEL9 repositories. Make use of the
new defaults and templates so we don't have to define everything all
over again.

The c9s/RHEL9 specific parts can be extracted into the repos when the
ARK mirror stops and be removed from here.

Upstream Status: RHEL-only
Bugzilla: INTERNAL

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 15:44:45 -04:00
Justin M. Forbes 4cce9c2c47 Turn on CONFIG_STACKTRACE for s390x zfpcdump kernels
Upstream commit 788691464c has changed SLUB_DEBUG to select
STACKDEPOT if STACKTRACE_SUPPORT. STACKDEPOT in turn selects STACKTRACE.
As s390x has stacktrace support, this leaves us with the option of
turning on STACKTRACE for s390x zfcpdump kernels or turning off
SLUB_DEBUG on those kernels.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:45 -04:00
Mark Salter 49866809ff arm64: switch ark kernel to 4K pagesize
RHEL9 for Aarch64 will use 4K pages. Shuffle the related configs
around so that they are shared by both ark and fedora.

Signed-off-by: Mark Salter <msalter@redhat.com>
2021-08-30 15:44:45 -04:00
Prarit Bhargava 3de801e9cd Disable AMIGA_PARTITION and KARMA_PARTITION
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1802694

The kernel FAST team wants these disabled for RHEL.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 15:44:45 -04:00
Peter Robinson fac25d1cff all: unify and cleanup i2c TPM2 modules
Enable the I2C based TPM2 modules on all Fedora arches except s390x.
They're needed on POWER64 for various security functions and we need
them on x86/aarch64 for IoT and other bits.

Also enable them on aarch64 for RHEL as we need them for RHEL for Edge.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:44 -04:00
Eric Auger 3085d6a068 redhat/configs: Set CONFIG_VIRTIO_IOMMU on aarch64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1972795

Upstream Status: RHEL only
Tested: on ARM with qemu (Jean-Philippe Brucker's qemu branch as the
qemu integration is not yet upstream)

We want to support the virtio-iommu on ARM. So let's compile it.

Signed-off-by: Eric Auger <eric.auger@redhat.com>

---

v1 -> v2:
- do not set the config in ark/generic/arm/aarch64 but rather
  in common/generic/arm/aarch64  and just cares about the setting
  for ARM as the default already is set to false in common.
2021-08-30 15:44:44 -04:00
Phil Auld 7524bcf31c redhat/configs: Disable CONFIG_RT_GROUP_SCHED in rhel config
Fedora and rhel-rt config already have CONFIG_RT_GROUP_SCHED disabled.
RT_GROUP_SCHED does not play well with cgroups v2. Rather than keep
this enabled, disable it in rhel going forward.

Signed-off-by: Phil Auld <pauld@redhat.com>
2021-08-30 15:44:44 -04:00
Fedora Kernel Team eb32614078 [redhat] New configs in drivers/video
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FB_SSD1307:

 This driver implements support for the Solomon SSD1307
 OLED controller over I2C.

 Symbol: FB_SSD1307 [=n]
 Type  : tristate
 Defined at drivers/video/fbdev/Kconfig:2209
   Prompt: Solomon SSD1307 framebuffer support
   Depends on: HAS_IOMEM [=y] && FB [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Graphics support
         -> Frame buffer Devices
           -> Support for frame buffer devices (FB [=y])
 Selects: FB_SYS_FOPS [=m] && FB_SYS_FILLRECT [=m] && FB_SYS_COPYAREA [=m] && FB_SYS_IMAGEBLIT [=m] && FB_DEFERRED_IO [=y] && PWM [=y] && FB_BACKLIGHT [=n]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: "Michel Dänzer" <mdaenzer@redhat.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Karol Herbst <kherbst@redhat.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:44 -04:00
Fedora Kernel Team aa10805eb7 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:44 -04:00
Fedora Kernel Team e5330d5a4d [redhat] AUTOMATIC: New configs 2021-08-30 15:44:44 -04:00
Fedora Kernel Team 512ad9bcec [redhat] AUTOMATIC: New configs 2021-08-30 15:44:44 -04:00
Fedora Kernel Team 4942a68840 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:44 -04:00
Prarit Bhargava 0d65a030b6 RHMAINTAINERS: Update for Jul 8 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 15:44:43 -04:00
Coiby Xu 0b9f8710df redhat/configs: enable KEXEC_SIG which is already enabled in RHEL8 for s390x and x86_64
Enable KEXEC_SIG for s390x and x86_64 which is already enabled in RHEL8.

Note when building .src.rpm, process_configs.sh would error on unset config
options. So CONFIG_KEXEC_SIG_FORCE files are added as well.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976835
Signed-off-by: Coiby Xu <coxu@redhat.com>
2021-08-30 15:44:43 -04:00
Fedora Kernel Team 9a0d91c4c1 [redhat] New configs in drivers/watchdog
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT:

 Enable this if you want to use a hrtimer timer based pretimeout for
 watchdogs that do not natively support pretimeout support. Be aware
 that because this pretimeout functionality uses hrtimers, it may not
 be able to fire before the actual watchdog fires in some situations.

 Symbol: WATCHDOG_HRTIMER_PRETIMEOUT [=n]
 Type  : bool
 Defined at drivers/watchdog/Kconfig:76
   Prompt: Enable watchdog hrtimer-based pretimeouts
   Depends on: WATCHDOG [=y]
   Location:
     -> Device Drivers
       -> Watchdog Timer Support (WATCHDOG [=y])

---

Cc: Jonathan Toppins <jtoppins@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:43 -04:00
Fedora Kernel Team aefcb99a0c [redhat] AUTOMATIC: New configs 2021-08-30 15:44:43 -04:00
Fedora Kernel Team ec3c3747de [redhat] AUTOMATIC: New configs 2021-08-30 15:44:43 -04:00
Fedora Kernel Team e232fc7571 [redhat] New configs in drivers/infiniband
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INFINIBAND_IRDMA:

 This is an Intel(R) Ethernet Protocol Driver for RDMA driver
 that support E810 (iWARP/RoCE) and X722 (iWARP) network devices.

 Symbol: INFINIBAND_IRDMA [=n]
 Type  : tristate
 Defined at drivers/infiniband/hw/irdma/Kconfig:2
   Prompt: Intel(R) Ethernet Protocol Driver for RDMA
   Depends on: INFINIBAND [=m] && (INFINIBAND_USER_ACCESS [=m] || !INFINIBAND_USER_ACCESS [=m]) && INET [=y] && (IPV6 [=y] || !IPV6 [=y]) && PCI [=y] && ICE [=m] && I40E [=m]
   Location:
     -> Device Drivers
       -> InfiniBand support (INFINIBAND [=m])
 Selects: GENERIC_ALLOCATOR [=y] && CONFIG_AUXILIARY_BUS

---

Cc: Kamal Heib <kheib@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 CONFIG_INFINIBAND_IRDMA enabled as a module.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 15:44:43 -04:00
Herton R. Krzesinski 0429b4cc81 rpmspec: do not BuildRequires bpftool on noarch
Turns out we also need to keep bpftool BuildRequires out of noarch as
well, at least on a recent centos koji build I bumped into it:

BuildError: error building package (arch noarch), mock exited with status (...)

Executing command: ['/usr/bin/dnf', 'builddep', '--installroot', (...)
(...)
DEBUG util.py:444:  No matching package to install: 'bpftool'
(...)
DEBUG util.py:444:  Not all dependencies satisfied
DEBUG util.py:444:  Error: Some packages could not be found.
DEBUG util.py:598:  Child return code was: 1
DEBUG util.py:169:  kill orphans

noarch doesn't build any kernel of course so just keep it out too.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 15:44:43 -04:00
Bruno Meneguele e3ccdda3ae redhat/configs: disable {IMA,EVM}_LOAD_X509
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1977529

This option was enabled by mistake (from my own part): this is only used for
allowing the option {IMA,EVM}_X509_PATH to be set with a specific path in
the system pointing to a valid X509 certificate, specific built for the
integrity subsystem. It turns out that we don't have such certificate and am
not sure it's going to be used anytime soon. In RHEL-8 we've allowed trusted
certificates to the integrity subsystem using the secure boot CA and the
certs used for the kernel build.

With these options set we have the following two error lines in dmesg:

integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
integrity: Unable to open file: /etc/keys/x509_evm.der (-2)

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 15:44:43 -04:00
Čestmír Kalina 7e408b0be3 [redhat] kabi: rename legacy terminology
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1953486
Upstream Status: RHEL only

As part of Red Hat’s commitment to remove problematic language from
our code, documentation, websites, and open source projects that we
are involved with, this patch renames kABI whitelist to stablelist.

Signed-off-by: Čestmír Kalina <ckalina@redhat.com>
2021-08-30 15:44:43 -04:00
Fedora Kernel Team 8cfc3f2d78 [redhat] New configs in drivers/net/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MEDIATEK_GE_PHY:

 Supports the MediaTek Gigabit Ethernet PHYs.

 Symbol: MEDIATEK_GE_PHY [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:210
   Prompt: MediaTek Gigabit Ethernet PHYs
   Depends on: NETDEVICES [=y] && PHYLIB [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])

---

 CONFIG_MOTORCOMM_PHY:

 Enables support for Motorcomm network PHYs.
 Currently supports the YT8511 gigabit PHY.

 Symbol: MOTORCOMM_PHY [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:237
   Prompt: Motorcomm PHYs
   Depends on: NETDEVICES [=y] && PHYLIB [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])

---

Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:42 -04:00
Fedora Kernel Team 1e1e6328ae [redhat] New configs in fs/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON:

 When using HUGETLB_PAGE_FREE_VMEMMAP, the freeing unused vmemmap
 pages associated with each HugeTLB page is default off. Say Y here
 to enable freeing vmemmap pages of HugeTLB by default. It can then
 be disabled on the command line via hugetlb_free_vmemmap=off.

 Symbol: HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON [=n]
 Type  : bool
 Defined at fs/Kconfig:248
   Prompt: Default freeing vmemmap pages of HugeTLB to on
   Depends on: HUGETLB_PAGE_FREE_VMEMMAP [=y]
   Location:
     -> File systems
       -> Pseudo filesystems

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:42 -04:00
Bruno Meneguele 185fc9da14 redhat: add secureboot CA certificate to trusted kernel keyring
This patch is a forward-port from what we already have in RHEL-8 kernels and
should also be done in RHEL-9 to avoid unexpected failures on customers.

Add the secure boot key certificate to the trusted kernel keyring
(.builtin_trusted_keys) to allow the placement of the kernel signing key
(shipped with the distro) in other kernel trusted keyrings, i.e. .ima
trusted keyring.

The need for adding the secure boot CA cert in the trusted kernel keyring
exists only for arches without UEFI support which don't support adding certs
to .platform_keyring and, consequently, can't add our own kernel image
signing key to trusted keyrings.

The biggest usage of that is for loading signed kernel images during
kexec/kdump process in arches that depends on the IMA infrastructure to
check the signatures, which has the ability to verify appended signatures
instead of the UEFI PE format. Said arches are PowerPC and S390X.

Cc: Justin M. Forbes <jforbes@fedoraproject.org>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Patrick Talbert <ptalbert@redhat.com>
Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 15:44:42 -04:00
Bruno Meneguele 5698b61516 redhat/configs: enable IMA_ARCH_POLICY for aarch64 and s390x
IMA_ARCH_POLICY was already enabled for x86_64 and ppc64le. Recently,
the IMA code handling EFI was unified under
security/integrity/ima/ima_efi.c and aarch64 with CONFIG_EFI can use it
for the IMA_ARCH_POLICY logic.

In somewhat the same way, s390x has all the bits in upstream to enable
IMA_ARCH_POLICY, which is tied with the IMA_SECURE_AND_OR_TRUSTED_BOOT
that s390x supports with its IPL mode and also make use during KEXEC'ing
a kernel image in their secure boot. With that, I'm proactivelly
enabling IMA_ARCH_POLICY for s390x as well.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 15:44:42 -04:00
Alaa Hleihel 1d1cf37c90 redhat/configs: Enable CONFIG_MLXBF_GIGE on aarch64
Bugzilla: http://bugzilla.redhat.com/1858599
Upstream: RHEL-only

Build the mlxbf_gige driver on aarch64 systems for BlueField-2 systems.

The second generation BlueField SoC supports an out-of-band Gigabit
Ethernet management port to the Arm subsystem. This driver supports
TCP/IP network connectivity for that port, and provides back-end routines
to handle basic ethtool requests.

Signed-off-by: Alaa Hleihel <ahleihel@redhat.com>
2021-08-30 15:44:42 -04:00
Kairui Song 0ee68eeebc [redhat] Generate a crashkernel.default for each kernel build
It has been a long-term demand for having a default crashkernel
value for each kernel build. This helps to manage kernel's
crashkernel usage by kernel version and provide users a reference
default value.

RHEL kernels support a `crashkernel=auto` cmdline param. And kernel
have a built-in default value used when `auto` is specified.
Many attempts are made to push this upstream. Recent attempt to
push this upstream raised a lot of discussions [1].

Upstream is not accepting this `crashkernel=auto` design. So after
more discussions, instead of adding a default value in kernel, just
add a config that packaged with kernel is more doable. Other packages,
like kexec-tools[2], can use this as a reference and update kernel
cmdline param.

[1]: https://lore.kernel.org/linux-mm/20210507010432.IN24PudKT%25akpm@linux-foundation.org/
[2]: https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/RXOEJD6NLLELYAT3VAHS5S56SO5AT7WN/

Signed-off-by: Kairui Song <kasong@redhat.com>
2021-08-30 15:44:42 -04:00
Fedora Kernel Team 2e05a7a097 [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DELL_WMI_PRIVACY:

 This option adds integration with the "Dell Hardware Privacy"
 feature of Dell laptops to the dell-wmi driver.

 Symbol: DELL_WMI_PRIVACY [=n]
 Type  : bool
 Defined at drivers/platform/x86/dell/Kconfig:167
   Prompt: Dell WMI Hardware Privacy Support
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_PLATFORM_DRIVERS_DELL [=y] && DELL_WMI [=m] && LEDS_TRIGGER_AUDIO [=m]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
         -> Dell X86 Platform Specific Device Drivers (X86_PLATFORM_DRIVERS_DELL [=y])
           -> Dell WMI notifications (DELL_WMI [=m])

---

 CONFIG_THINKPAD_LMI:

 This driver allows changing BIOS settings on Lenovo machines whose
 BIOS support the WMI interface.

 To compile this driver as a module, choose M here: the module will
 be called think-lmi.

 Symbol: THINKPAD_LMI [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:643
   Prompt: Lenovo WMI-based systems management driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
 Selects: FW_ATTR_CLASS [=m]

---

 CONFIG_WIRELESS_HOTKEY:

 This driver provides supports for the wireless buttons found on some AMD,
 HP, & Xioami laptops.
 On such systems the driver should load automatically (via ACPI alias).

 To compile this driver as a module, choose M here: the module will
 be called wireless-hotkey.

 Symbol: WIRELESS_HOTKEY [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:418
   Prompt: Wireless hotkey button
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && INPUT [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---

 CONFIG_X86_PLATFORM_DRIVERS_INTEL:

 Say Y here to get to see options for device drivers for
 various Intel x86 platforms, including vendor-specific
 drivers. This option alone does not add any kernel code.

 If you say N, all options in this submenu will be skipped
 and disabled.

 Symbol: X86_PLATFORM_DRIVERS_INTEL [=y]
 Type  : bool
 Defined at drivers/platform/x86/intel/Kconfig:6
   Prompt: Intel x86 Platform Specific Device Drivers
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:42 -04:00
Fedora Kernel Team bae7fd67a5 [redhat] New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_QCOM_PM8008:

 Select this option to get support for the Qualcomm Technologies, Inc.
 PM8008 PMIC chip. PM8008 is a dedicated camera PMIC that integrates
 all the necessary power management, housekeeping, and interface
 support functions into a single IC. This driver provides common
 support for accessing the device by instantiating all the child nodes
 under it in the device tree. Additional drivers must be enabled in
 order to use the functionality of the device.

 Symbol: MFD_QCOM_PM8008 [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:2103
   Prompt: QCOM PM8008 Power Management IC
   Depends on: HAS_IOMEM [=y] && I2C [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: REGMAP_I2C [=m] && REGMAP_IRQ [=n]

---

 CONFIG_MFD_RT4831:

 This enables support for the Richtek RT4831 that includes 4 channel
 WLED driving and Display Bias Voltage. It's commonly used to provide
 power to the LCD display and LCD backlight.

 Symbol: MFD_RT4831 [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:1081
   Prompt: Richtek RT4831 four channel WLED and Display Bias Voltage
   Depends on: HAS_IOMEM [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_CORE [=y] && REGMAP_I2C [=m]

---

Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:41 -04:00
Fedora Kernel Team ec67ce148e [redhat] New configs in drivers/net/wwan
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_IOSM:

 This driver enables Intel M.2 WWAN Device communication.

 If you have one of those Intel M.2 WWAN Modules and wish to use it in
 Linux say Y/M here.

 If unsure, say N.

 Symbol: IOSM [=n]
 Type  : tristate
 Defined at drivers/net/wwan/Kconfig:59
   Prompt: IOSM Driver for Intel M.2 WWAN Device
   Depends on: NETDEVICES [=y] && WWAN [=y] && INTEL_IOMMU [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless WAN
           -> WWAN Driver Core (WWAN [=y])

---

 CONFIG_WWAN_HWSIM:

 This driver is a developer testing tool that can be used to test WWAN
 framework.

 To compile this driver as a module, choose M here: the module will be
 called wwan_hwsim.  If unsure, say N.

 Symbol: WWAN_HWSIM [=n]
 Type  : tristate
 Defined at drivers/net/wwan/Kconfig:19
   Prompt: Simulated WWAN device
   Depends on: NETDEVICES [=y] && WWAN [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless WAN
           -> WWAN Driver Core (WWAN [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:41 -04:00
Fedora Kernel Team 40e2251e56 [redhat] New configs in drivers/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PHY_CAN_TRANSCEIVER:

 This option enables support for CAN transceivers as a PHY. This
 driver provides function for putting the transceivers in various
 functional modes using gpios and sets the attribute max link
 rate, for CAN drivers.

 Symbol: PHY_CAN_TRANSCEIVER [=n]
 Type  : tristate
 Defined at drivers/phy/Kconfig:64
   Prompt: CAN transceiver PHY
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=n]

---

 CONFIG_PHY_HI3670_USB:

 Enable this to support the HISILICON HI3670 USB PHY.

 To compile this driver as a module, choose M here.

 Symbol: PHY_HI3670_USB [=n]
 Type  : tristate
 Defined at drivers/phy/hisilicon/Kconfig:26
   Prompt: hi3670 USB PHY support
   Depends on: ARCH_HISI [=y] && ARM64 [=y] || COMPILE_TEST [=n]
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=y] && MFD_SYSCON [=y]

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:41 -04:00
Fedora Kernel Team 09fe2f5b72 [redhat] New configs in drivers/char
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_XILLYUSB:

 XillyUSB is the Xillybus variant which uses USB for communicating
 with the FPGA.

 Set to M if you want Xillybus to use USB for communicating with
 the FPGA. The module will be called xillyusb.

 Symbol: XILLYUSB [=n]
 Type  : tristate
 Defined at drivers/char/xillybus/Kconfig:42
   Prompt: XillyUSB: Xillybus generic FPGA interface for USB
   Depends on: USB [=y]
   Location:
     -> Device Drivers
       -> Character devices
 Selects: CRC32 [=y] && XILLYBUS_CLASS [=n]

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:41 -04:00
Fedora Kernel Team 96aee33af1 [redhat] New configs in kernel/Kconfig.preempt
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SCHED_CORE:

 This option permits Core Scheduling, a means of coordinated task
 selection across SMT siblings. When enabled -- see
 prctl(PR_SCHED_CORE) -- task selection ensures that all SMT siblings
 will execute a task from the same 'core group', forcing idle when no
 matching task is found.

 Use of this feature includes:
  - mitigation of some (not all) SMT side channels;
  - limiting SMT interference to improve determinism and/or performance.

 SCHED_CORE is default enabled when SCHED_SMT is enabled -- when
 unused there should be no impact on performance.

 Symbol: SCHED_CORE [=y]
 Type  : bool
 Defined at kernel/Kconfig.preempt:103
   Prompt: Core Scheduling for SMT
   Depends on: SCHED_SMT [=y]
   Location:
     -> General setup

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 15:44:41 -04:00
Peter Robinson 7733e3601f common: enable STRICT_MODULE_RWX everywhere
This option sets module text and rodata memory will be made read-only,
and non-text memory will be made non-executable. This helps to protect
against against certain security exploits and doesn't affect
performance. We've also had it enabled on ARMv7 for some time without
issues.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 15:44:41 -04:00
Fedora Kernel Team 1685cca663 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Fedora Kernel Team 3d45437b1e [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Fedora Kernel Team 249bcaac58 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Fedora Kernel Team 2f5e3a6626 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Tom Stellard de462ba455 [redhat] Add (unset) config options that are only available when compiling with clang
The prevents the process_configs.sh script from failing when compiling
with clang.

Signed-off-by: Tom Stellard <tstellar@redhat.com>
2021-08-30 15:44:40 -04:00
Fedora Kernel Team 93891aca37 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Fedora Kernel Team 57eb6830d3 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Fedora Kernel Team 586e8b6a40 [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Fedora Kernel Team 0b88b5c12b [redhat] AUTOMATIC: New configs 2021-08-30 15:44:40 -04:00
Justin M. Forbes 23d465e491 COMMON_CLK_STM32MP157_SCMI is bool and selects COMMON_CLK_SCMI
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 15:44:40 -04:00
Timothée Ravier 6b27d69193 kernel.spec: Add kernel{,-debug}-devel-matched meta packages
This introduce two empty packages which requires both
kernel{,-debug}-core & kernel{,-debug}-devel for a given package
version. This is usefull for installing version matching packages when
you already have the kernel{,-debug}-core package installed and want to
install the matching {,-debug}-devel package without specifying the
version nor updating the already installed package.

We can not have the kernel{,-debug}-devel packages require the version
matching kernel{,-debug}-core package has this breaks building modules
inside a container:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1083

This is an enhancement for rpm-ostree based Fedora variants such as
Fedora Silverblue. See the full discussion in:
https://pagure.io/workstation-ostree-config/pull-request/214

Signed-off-by: Timothée Ravier <travier@redhat.com>
2021-08-30 15:44:39 -04:00
Fedora Kernel Team 40e7df242e [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TEST_CLOCKSOURCE_WATCHDOG:

 Enable this option to create a kernel module that will trigger
 a test of the clocksource watchdog.  This module may be loaded
 via modprobe or insmod in which case it will run upon being
 loaded, or it may be built in, in which case it will run
 shortly after boot.

 If unsure, say N.

 Symbol: TEST_CLOCKSOURCE_WATCHDOG [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:2591
   Prompt: Test clocksource watchdog in kernel space
   Depends on: RUNTIME_TESTING_MENU [=y] && CLOCKSOURCE_WATCHDOG [=y]
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Runtime Testing (RUNTIME_TESTING_MENU [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:31 -04:00
Fedora Kernel Team 81ff8abec1 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:31 -04:00
Fedora Kernel Team a0ea4daedf [redhat] AUTOMATIC: New configs 2021-08-30 14:31:31 -04:00
Justin M. Forbes fe66d3b2fc Turn off with_selftests for Fedora
As of MR 1155 building with_selftests turns on with_bpftool.  In order
to properly turn off with_bpftool we must also turn off with_selftests.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:31 -04:00
Justin M. Forbes e70bc73ed6 Don't build bpftool on Fedora
The MR 1153 change which generates the vmlinux.h as an artifact in
kernel-devel seems to have also removed the '%define with_bpftool 0'
from the Fedora section, resulting in a bpftool subpackage being created
in Fedora kernel builds.  This is unnecessary for the vmlinux.h
generation and undesired from a Fedora packaging standpoint.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:31 -04:00
Justin M. Forbes 79f9b16f0c Fix location of syscall scripts for kernel-devel
The most recent pull of tip included changes to switch from using
syscalltbl.sh and syscallhdr.sh in arch/x86/entry/syscalls/ to the
generic versions in scripts/.  As those were included in kernel-devel we
need to move the locations in the spec or the build will fail.

Upstream commits for reference:
6218d0f6b8
3cba325b35

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:31 -04:00
Fedora Kernel Team 5149ae5c44 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:31 -04:00
Fedora Kernel Team 43da8cf4ee [redhat] AUTOMATIC: New configs 2021-08-30 14:31:31 -04:00
Peter Robinson 6e225a98a6 fedora: arm: Enable some i.MX8 options
Enable a few new and missed i.MX8 options, in particular for the
i.MX8MP and i.MX8DXL SoCs.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:30 -04:00
Justin M. Forbes d4effe910c Enable Landlock for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:30 -04:00
Justin M. Forbes 21f892f7c9 Filter update for Fedora aarch64
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:30 -04:00
Fedora Kernel Team 74a3bacbec [redhat] AUTOMATIC: New configs 2021-08-30 14:31:30 -04:00
Fedora Kernel Team f1323199a1 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:30 -04:00
Herton R. Krzesinski f0b89ca16a rpmspec: only build debug meta packages where we build debug ones
Previous commit "rpmspec: build debug-* meta-packages if debug
builds are disabled" failed to consider the architectures or
cases where we disable debug packages, and made meta packages
being built for them even if real debug package build was
disabled in the normal case. So eg. for arches we don't build
kernels (eg. i686) debug meta packages could appear even if we
don't have kernel/kernel-debug being built.

This adds some logic to see if really with_debug was enabled,
and creating the meta-package only when it is enabled/set.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:31:30 -04:00
Fedora Kernel Team 832716ced2 [redhat] New configs in security/integrity
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_IMA_DISABLE_HTABLE:

 This option disables htable to allow measurement of duplicate records.

 Symbol: IMA_DISABLE_HTABLE [=n]
 Type  : bool
 Defined at security/integrity/ima/Kconfig:338
   Prompt: Disable htable to allow measurement of duplicate records
   Depends on: INTEGRITY [=y] && IMA [=y]
   Location:
     -> Security options
       -> Integrity subsystem (INTEGRITY [=y])

---

Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:30 -04:00
Herton R. Krzesinski 45b9f23198 rpmspec: do not BuildRequires bpftool on nobuildarches
Kernel builds are failing on i686 due missing or not available bpftool.
It does not make sense to require it on arches that we only build
headers and don't need bpftool, so make it not required on this case.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:31:30 -04:00
Thomas Huth c152ade97d redhat/configs: Consolidate CONFIG_HMC_DRV in the common s390x folder
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270

The CONFIG_HMC_DRV switch is specific to s390x, and uses the same
setting in Fedora and ARK, so we should consolidate this setting
in the redhat/configs/common/generic/s390x/ folder.

Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:30 -04:00
Thomas Huth 594844ac08 redhat/configs: Consolidate CONFIG_EXPOLINE_OFF in the common folder
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270

The other CONFIG_EXPOLINE_* options already reside in the folder
redhat/configs/common/generic/s390x/, so we should move the
CONFIG_EXPOLINE_OFF switch here, too.

Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:29 -04:00
Thomas Huth e3e037e7e7 redhat/configs: Move CONFIG_HW_RANDOM_S390 into the s390x/ subfolder
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270

This switch is specific to s390x, so it should reside in the
s390x/ folder.

Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:29 -04:00
Thomas Huth 13d0d54335 redhat/configs: Disable CONFIG_HOTPLUG_PCI_SHPC in the Fedora settings
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270

We never enabled this for the RHEL/ARK kernel, so this setting in
Fedora looked suspicious... and after asking some people from IBM,
they confirmed that this is unused on s390x, so we can disable this
now.

Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:29 -04:00
Thomas Huth 8c80152b74 redhat/configs: Remove the non-existent CONFIG_NO_BOOTMEM switch
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270

The CONFIG_NO_BOOTMEM switch has been removed upstream in commit
b4a991ec58 ("mm: remove CONFIG_NO_BOOTMEM"), so we can drop this
setting in the ARK kernel config now, too.

Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:29 -04:00
Thomas Huth 9d4de6fdfb redhat/configs: Compile the virtio-console as a module on s390x
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270

Since upstream commit bb533ec8ba ("s390/config: do not select VIRTIO_CONSOLE
via Kconfig"), it's possible to build the virtio-console driver as a module
on s390x, too. We've switch the RHEL8 setting to "m" in BZ 1954119, so we
should adapt the Fedora / ARK / RHEL9 setting accordingly now, too (by
disabling the s390x-specific setting, so that we fall back to the generic
CONFIG_VIRTIO_CONSOLE=m setting).

Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:29 -04:00
Thomas Huth 9c659ce4e7 redhat/configs: Enable CONFIG_S390_CCW_IOMMU and CONFIG_VFIO_CCW for ARK, too
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976270

These two options have been enabled for RHEL8 in BZ 1660917, so we should
enable those now in RHEL9/ARK, too.

Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:29 -04:00
CKI Gitlab d1c0131ded [redhat] New configs in arch/arm64 2021-08-30 14:31:28 -04:00
Fedora Kernel Team d62ec4aa3d [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_DPS920AB:

 If you say yes here you get hardware monitoring support for Delta
 DPS920AB Power Supplies.

 This driver can also be built as a module. If so, the module will
 be called dps920ab.

 Symbol: SENSORS_DPS920AB [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:89
   Prompt: Delta DPS920AB Power Supply
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_MP2888:

 If you say yes here you get hardware monitoring support for MPS
 MP2888 Digital, Multi-Phase, Pulse-Width Modulation Controller.

 This driver can also be built as a module. If so, the module will
 be called mp2888.

 Symbol: SENSORS_MP2888 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:261
   Prompt: MPS MP2888
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_PIM4328:

 If you say yes here you get hardware monitoring support for Flex
 PIM4328, PIM4820 and PIM4006 Power Interface Modules.

 This driver can also be built as a module. If so, the module will
 be called pim4328.

 Symbol: SENSORS_PIM4328 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:279
   Prompt: Flex PIM4328 and compatibles
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_SHT4x:

 If you say yes here you get support for the Sensiron SHT40, SHT41 and
 SHT45 humidity and temperature sensors.

 This driver can also be built as a module. If so, the module
 will be called sht4x.

 Symbol: SENSORS_SHT4x [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:1586
   Prompt: Sensiron humidity and temperature sensors. SHT4x and compat.
   Depends on: HWMON [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
 Selects: CRC8 [=m]

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:28 -04:00
Vladis Dronov 9a8dc4cada Revert "Merge branch 'ec_fips' into 'os-build'"
We need to revert the merge request !1150 and make CONFIG_CRYPTO_ECDH
and CONFIG_CRYPTO_ECDSA back to =m. Current =y setting prevents a kernel
booting in FIPS mode. This blocks some processes, see bz1915290#c23. This
is an upstream issue and we need this revert until a proposed upstream
solution is fully tested.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Link: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1150
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:31:28 -04:00
Fedora Kernel Team 9fa4c3deca [redhat] AUTOMATIC: New configs 2021-08-30 14:31:28 -04:00
Fedora Kernel Team 2978030efa [redhat] AUTOMATIC: New configs 2021-08-30 14:31:28 -04:00
Justin M. Forbes aaa70c0907 Fix typos in fedora filters
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:28 -04:00
Justin M. Forbes 445ce09fc5 More filtering for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:28 -04:00
Justin M. Forbes 64e004afd8 Fix Fedora module filtering for spi-altera-dfl
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:28 -04:00
Justin M. Forbes f74c9b56d2 Fedora 5.13 config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:27 -04:00
Peter Robinson 6530470d5c fedora: cleanup TCG_TIS_I2C_CR50
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:27 -04:00
Peter Robinson 32baf939f1 fedora: drop duplicate configs
The module compress options are already in common and are the
same so just drop them. No functional change.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:27 -04:00
Justin M. Forbes 0ce547bdd5 More Fedora config updates for 5.13
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:27 -04:00
Alaa Hleihel f89a654748 redhat/configs: Enable needed drivers for BlueField SoC on aarch64
Enable the needed configs on aarch64 for enabling the following
on BlueField SoC:

 - TmFifo driver to provide console and network access to the external host.

 - bootctl platform driver to provide the ability to query secure state
   and control the eMMC boot partition swapping by sending SMC calls to
   ATF running at EL3.

 - ipmb-dev-int driver and it's dependencies for supporting receiving IPMB
   requests on a Satellite MC from the BMC. Once a response is ready, this
   driver will send back a response to the BMC via the IPMB channel.

Bugzilla: http://bugzilla.redhat.com/1858592
Bugzilla: http://bugzilla.redhat.com/1858594
Bugzilla: http://bugzilla.redhat.com/1858596
Upstream: RHEL-only

Signed-off-by: Alaa Hleihel <ahleihel@redhat.com>
2021-08-30 14:31:27 -04:00
Prarit Bhargava 66594c3934 redhat: Rename mod-blacklist.sh to mod-denylist.sh
In the spirit of inclusivity, rename mod-blacklist.sh to
mod-denylist.sh.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:31:27 -04:00
Marcelo Ricardo Leitner d4af1b0ff3 redhat/configs: enable CONFIG_NET_ACT_MPLS
It's enabled on RHEL8 and it's going to be needed on RHEL9 as well.

Cc: Guillaume Nault <gnault@redhat.com>
Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
2021-08-30 14:31:26 -04:00
Tom Stellard 102acc39b8 [redhat] spec: Enable config checks when building with clang
The config checks pass on clang now that the CONFIG_INIT_STACK_ALL_PATTERN
and CONFIG_INIT_STACK_ALL_ZERO have been added to the config files.

Signed-off-by: Tom Stellard <tstellar@redhat.com>
2021-08-30 14:31:26 -04:00
Patrick Talbert 6c717dc023 [redhat] configs: Add a generic facility for providing custom config options
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:26 -04:00
Jiri Olsa fd3670e87c configs: Enable CONFIG_DEBUG_KERNEL for zfcpdump
Enabling CONFIG_DEBUG_KERNEL for zfcpdump otherwise
CONFIG_DEBUG_INFO_BTF won't be enabled.

The CONFIG_DEBUG_KERNEL rnabled several other generic
options. Disabling them so the zfcp config stays the
same (apart from CONFIG_DEBUG_INFO_BTF enablement).

Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:26 -04:00
Don Zickus 673716aed1 kernel.spec: Add support to use vmlinux.h
For split environments where the kernel and userspace tools are not
built together, take the -devel packaged vmlinux.h file and use it
to build bpftools.

Use the VMLINUX_H= env variable to tell the tools which file to use.

Orginally done by Jiri Olsa <jolsa@redhat.com>

Updated to transition from artifacts to -devel package.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:31:26 -04:00
Jiri Olsa 0d997b96e8 spec: Add vmlinux.h to kernel-devel package
Adding/generating vmlinux.h by bpftool to the kernel-devel
package:

  $ rpm -ql -p kernel-devel-5.13.0-0.rc...x86_64.rpm | grep vmlinux.h
  /usr/src/kernels/5.13.0-0.rc...x86_64/vmlinux.h

Some tools like bpftool or selftest need vmlinux.h to properly
compile. The vmlinux.h will be used by build system to compile
tools separately.

Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:26 -04:00
Fedora Kernel Team 9394b8bde6 [redhat] New configs in drivers/net/usb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_USB_RTL8153_ECM:

 This option supports ECM mode for RTL8153 ethernet adapter, when
 CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not
 supported by r8152 driver.

 Symbol: USB_RTL8153_ECM [=m]
 Type  : tristate
 Defined at drivers/net/usb/Kconfig:631
   Prompt: RTL8153 ECM support
   Depends on: NETDEVICES [=y] && USB_NET_DRIVERS [=y] && USB_NET_CDCETHER [=m] && (USB_RTL8152 [=m] || USB_RTL8152 [=m]=n)
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> USB Network Adapters (USB_NET_DRIVERS [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:26 -04:00
Justin M. Forbes 5a3ee792cf Turn off DRM_XEN_FRONTEND for Fedora as we had DRM_XEN off already
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:26 -04:00
Fedora Kernel Team e8ef10c322 [redhat] New configs in drivers/net/can
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CAN_ETAS_ES58X:

 This driver supports the ES581.4, ES582.1 and ES584.1 interfaces
 from ETAS GmbH (https://www.etas.com/en/products/es58x.php).

 To compile this driver as a module, choose M here: the module
 will be called etas_es58x.

 Symbol: CAN_ETAS_ES58X [=n]
 Type  : tristate
 Defined at drivers/net/can/usb/Kconfig:23
   Prompt: ETAS ES58X CAN/USB interfaces
   Depends on: NET [=y] && CAN [=m] && CAN_DEV [=m] && USB [=y]
   Location:
     -> Networking support (NET [=y])
       -> CAN bus subsystem support (CAN [=m])
         -> CAN Device Drivers
           -> Platform CAN drivers with Netlink support (CAN_DEV [=m])
             -> CAN USB interfaces
 Selects: CRC16 [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:26 -04:00
Fedora Kernel Team a1aa8ca44a [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BMI088_ACCEL:

 Say yes here to build support for the Bosch BMI088 accelerometer.

 This is a combo module with both accelerometer and gyroscope. This
 driver only implements the accelerometer part, which has its own
 address and register map. BMG160 provides the gyroscope driver.

 Symbol: BMI088_ACCEL [=n]
 Type  : tristate
 Defined at drivers/iio/accel/Kconfig:160
   Prompt: Bosch BMI088 Accelerometer Driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Accelerometers
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && REGMAP [=y] && BMI088_ACCEL_SPI [=n]

---

 CONFIG_TI_ADS131E08:

 Say yes here to get support for Texas Instruments ADS131E04, ADS131E06
 and ADS131E08 chips.

 This driver can also be built as a module. If so, the module will be
 called ti-ads131e08.

 Symbol: TI_ADS131E08 [=n]
 Type  : tristate
 Defined at drivers/iio/adc/Kconfig:1157
   Prompt: Texas Instruments ADS131E08
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:25 -04:00
Fedora Kernel Team 46102bd7f4 [redhat] New configs in drivers/extcon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EXTCON_USBC_TUSB320:

 Say Y here to enable support for USB Type C cable detection extcon
 support using a TUSB320.

 Symbol: EXTCON_USBC_TUSB320 [=n]
 Type  : tristate
 Defined at drivers/extcon/Kconfig:189
   Prompt: TI TUSB320 USB-C extcon support
   Depends on: EXTCON [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> External Connector Class (extcon) support (EXTCON [=y])
 Selects: REGMAP_I2C [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:25 -04:00
Fedora Kernel Team f0721bd235 [redhat] New configs in drivers/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BATTERY_GOLDFISH:

 Say Y to enable support for the Goldfish battery and AC power
 driver. Originated in the Android Studio Emulator (goldfish) it is
 going to be used in other emulators.

 Symbol: BATTERY_GOLDFISH [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:705
   Prompt: Goldfish battery driver
   Depends on: POWER_SUPPLY [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])

---

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:25 -04:00
Fedora Kernel Team b95c5b8af5 [redhat] New configs in drivers/pwm
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PWM_ATMEL_TCB:

 Generic PWM framework driver for Atmel Timer Counter Block.

 A Timer Counter Block provides 6 PWM devices grouped by 2.
 Devices in a given group must have the same period.

 To compile this driver as a module, choose M here: the module
 will be called pwm-atmel-tcb.

 Symbol: PWM_ATMEL_TCB [=n]
 Type  : tristate
 Defined at drivers/pwm/Kconfig:76
   Prompt: Atmel TC Block PWM support
   Depends on: PWM [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Pulse-Width Modulation (PWM) Support (PWM [=y])
 Selects: REGMAP_MMIO [=n]

---

 CONFIG_PWM_DWC:

 PWM driver for Synopsys DWC PWM Controller attached to a PCI bus.

 To compile this driver as a module, choose M here: the module
 will be called pwm-dwc.

 Symbol: PWM_DWC [=n]
 Type  : tristate
 Defined at drivers/pwm/Kconfig:167
   Prompt: DesignWare PWM Controller
   Depends on: PWM [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> Pulse-Width Modulation (PWM) Support (PWM [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:25 -04:00
Fedora Kernel Team e85c2cf6ca [redhat] New configs in drivers/mtd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MTD_NAND_ECC_SW_BCH:

 This enables support for software BCH error correction. Binary BCH
 codes are more powerful and cpu intensive than traditional Hamming
 ECC codes. They are used with NAND devices requiring more than 1 bit
 of error correction.

 Symbol: MTD_NAND_ECC_SW_BCH [=n]
 Type  : bool
 Defined at drivers/mtd/nand/Kconfig:38
   Prompt: Software BCH ECC engine
   Depends on: MTD [=m]
   Location:
     -> Device Drivers
       -> Memory Technology Device (MTD) support (MTD [=m])
         -> NAND
           -> ECC engine support
 Selects: BCH [=n] && MTD_NAND_ECC [=n]

---

 CONFIG_MTD_NAND_ECC_SW_HAMMING:

 This enables support for software Hamming error
 correction. This correction can correct up to 1 bit error
 per chunk and detect up to 2 bit errors. While it used to be
 widely used with old parts, newer NAND chips usually require
 more strength correction and in this case BCH or RS will be
 preferred.

 Symbol: MTD_NAND_ECC_SW_HAMMING [=n]
 Type  : bool
 Defined at drivers/mtd/nand/Kconfig:18
   Prompt: Software Hamming ECC engine
   Depends on: MTD [=m]
   Location:
     -> Device Drivers
       -> Memory Technology Device (MTD) support (MTD [=m])
         -> NAND
           -> ECC engine support
 Selects: MTD_NAND_ECC [=n]
 Selected by [n]:
   - SM_FTL [=n] && MTD [=m] && BLOCK [=y]
   - MTD_NAND_NDFC [=n] && MTD [=m] && MTD_RAW_NAND [=n] && 4xx

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:25 -04:00
Fedora Kernel Team 661b8a8473 [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ADXRS290:

 Say yes here to build support for Analog Devices ADXRS290 programmable
 digital output gyroscope.

 This driver can also be built as a module. If so, the module will be
 called adxrs290.

 Symbol: ADXRS290 [=n]
 Type  : tristate
 Defined at drivers/iio/gyro/Kconfig:44
   Prompt: Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Digital gyroscope sensors
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

 CONFIG_AS73211:

 If you say yes here you get support for the AMS AS73211
 JENCOLOR(R) Digital XYZ Sensor.

 For triggered measurements, you will need an additional trigger driver
 like IIO_HRTIMER_TRIGGER or IIO_SYSFS_TRIGGER.

 This driver can also be built as a module.  If so, the module
 will be called as73211.

 Symbol: AS73211 [=n]
 Type  : tristate
 Defined at drivers/iio/light/Kconfig:89
   Prompt: AMS AS73211 XYZ color sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Light sensors
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

 CONFIG_HDC2010:

 Say yes here to build support for the Texas Instruments
 HDC2010 and HDC2080 relative humidity and temperature sensors.

 To compile this driver as a module, choose M here: the module
 will be called hdc2010.

 Symbol: HDC2010 [=n]
 Type  : tristate
 Defined at drivers/iio/humidity/Kconfig:41
   Prompt: TI HDC2010 relative humidity and temperature sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Humidity sensors

---

 CONFIG_IIO_BUFFER_DMA:

 Provides the generic IIO DMA buffer infrastructure that can be used by
 drivers for devices with DMA support to implement the IIO buffer.

 Should be selected by drivers that want to use the generic DMA buffer
 infrastructure.

 Symbol: IIO_BUFFER_DMA [=n]
 Type  : tristate
 Defined at drivers/iio/buffer/Kconfig:13
   Prompt: Industrial I/O DMA buffer infrastructure
   Depends on: IIO [=m] && IIO_BUFFER [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Enable buffer support within IIO (IIO_BUFFER [=y])
 Selected by [n]:
   - IIO_BUFFER_DMAENGINE [=n] && IIO [=m] && IIO_BUFFER [=y]

---

 CONFIG_IIO_BUFFER_DMAENGINE:

 Provides a bonding of the generic IIO DMA buffer infrastructure with the
 DMAEngine framework. This can be used by converter drivers with a DMA port
 connected to an external DMA controller which is supported by the
 DMAEngine framework.

 Should be selected by drivers that want to use this functionality.

 Symbol: IIO_BUFFER_DMAENGINE [=n]
 Type  : tristate
 Defined at drivers/iio/buffer/Kconfig:22
   Prompt: Industrial I/O DMA buffer integration with DMAEngine
   Depends on: IIO [=m] && IIO_BUFFER [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Enable buffer support within IIO (IIO_BUFFER [=y])
 Selects: IIO_BUFFER_DMA [=n]
 Selected by [n]:
   - ADI_AXI_ADC [=n] && IIO [=m]

---

 CONFIG_IIO_TRIGGERED_EVENT:

 Provides helper functions for setting up triggered events.

 Symbol: IIO_TRIGGERED_EVENT [=n]
 Type  : tristate
 Defined at drivers/iio/Kconfig:65
   Prompt: Enable triggered events support
   Depends on: IIO [=m]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
 Selects: IIO_TRIGGER [=y]
 Selected by [n]:
   - HI8435 [=n] && IIO [=m] && SPI [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:25 -04:00
Justin M. Forbes be8cf348d2 Fedora 5.13 config updates pt 3
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:24 -04:00
Fedora Kernel Team ca7040b4ca [redhat] New configs in drivers/usb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_USB_CDNS_SUPPORT:

 Say Y here if your system has a Cadence USBSS or USBSSP
 dual-role controller.
 It supports: dual-role switch, Host-only, and Peripheral-only.

 Symbol: USB_CDNS_SUPPORT [=n]
 Type  : tristate
 Defined at drivers/usb/cdns3/Kconfig:1
   Prompt: Cadence USB Support
   Depends on: USB_SUPPORT [=y] && (USB [=y] || USB_GADGET [=n]) && HAS_DMA [=y]
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
 Selects: USB_XHCI_PLATFORM [=n] && USB_ROLE_SWITCH [=m]

---

 CONFIG_USB_SERIAL_XR:

 Say Y here if you want to use MaxLinear/Exar USB to Serial converter
 devices.

 To compile this driver as a module, choose M here: the
 module will be called xr_serial.

 Symbol: USB_SERIAL_XR [=n]
 Type  : tristate
 Defined at drivers/usb/serial/Kconfig:636
   Prompt: USB MaxLinear/Exar USB to Serial driver
   Depends on: USB_SUPPORT [=y] && USB [=y] && USB_SERIAL [=y]
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
         -> USB Serial Converter support (USB_SERIAL [=y])

---

Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:24 -04:00
Peter Robinson ea5a87b4c8 all: enable ath11k wireless modules
Enable the QCom ath11k wireless module that ships with a number of
modern devices/laptpos. We enable the PCI module, and MHI/QRTR deps,
plus the AHB module for Fedora Arm but disable all for POWER/s390x.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:24 -04:00
Peter Robinson 9e840c6303 all: Enable WWAN and associated MHI bus pieces
The Modem Host Interface (MHI) is used for most newer 4G/LTE and 5G
modems. It's basically virtual ethernet over a PCI <-> PCIE-endpoint
with a control over a TTY interface. These modems are already in the
latest Lenovo laptops and likely others, as well as Edge gateways.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:24 -04:00
Jiri Olsa b3d89b822e spec: Enable sefltests rpm build
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:24 -04:00
Jiri Olsa 83987025a7 spec: Allow bpf selftest/samples to fail
The bpf selftest and samples suites are quite unstable and might
fail to compile.  Make sure that won't break the rpm build and
enable their build.

Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:24 -04:00
Toke Høiland-Jørgensen 7ffb8896c8 bpf, selftests: Disable tests that need clang13
ARK kernel specific change.

Disabling test that won't compile under clang-12.

Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2021-08-30 14:31:24 -04:00
Jiri Benc 2e2e4c0855 kvm: Add kvm_stat.service file and kvm_stat logrotate config to the tools
Backport of RHEL8 commit.
  - skipping redhat/git/files hunk

commit 9e682a5da6015f4357aca94592d0a6a9444322bf
Author: Thomas Huth <thuth@redhat.com>
Date:   Mon Feb 22 12:20:36 2021 +0100

    kvm: Add kvm_stat.service file and kvm_stat logrotate config to the tools

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1919930
    Upstream Status: RHEL only

    Install the kvm_stat.service systemd file and add a logrotate config
    to avoid that the logs fill up the disk space.

    Signed-off-by: Thomas Huth <thuth@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc fc22544578 kernel.spec: Add missing source files to kernel-selftests-internal
Backport of RHEL8 commit.
  - small context conflict

commit 0d1e93c8ad2d59ce8a775ebb4e2f5f98363e84be
Author: Jiri Olsa <jolsa@redhat.com>
Date:   Fri Feb 12 13:54:27 2021 -0500

    [redhat] kernel.spec: Add missing source files to kernel-selftests-internal

    Message-id: <20210212135427.1250224-1-jolsa@redhat.com>
    Patchwork-id: 352955
    Patchwork-instance: patchwork
    O-Subject: [PATCHv2 RHEL8.4 1925911] kernel.spec: Add missing source files to kernel-selftests-internal
    Bugzilla: 1925911
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
    RH-Acked-by: Jiri Benc <jbenc@redhat.com>

    Bugzilla: 1925911
    https://bugzilla.redhat.com/show_bug.cgi?id=1925911
    Upstream: RHEL-only
    Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=34912232

    description
    ===========
    The test_progs -t btf_dump needs also some of the source files,
    installing them manually.

    Signed-off-by: Jiri Olsa <jolsa@redhat.com>
    Signed-off-by: Jan Stancek <jstancek@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc 6a4f3d89a7 kernel.spec: selftests: add net/forwarding to TARGETS list
Backport of RHEL8 commit.

commit 89f64e99dc9cc67f072621d1016f771302d02c14
Author: Hangbin Liu <haliu@redhat.com>
Date:   Wed Dec 16 13:23:29 2020 -0500

    [redhat] kernel.spec: add net/forwarding to TARGETS list

    Message-id: <20201216132329.2294096-1-haliu@redhat.com>
    Patchwork-id: 345158
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.4 net PATCH] kernel.spec: add net/forwarding to TARGETS list
    Bugzilla: 1908340
    RH-Acked-by: Andrea Claudi <aclaudi@redhat.com>
    RH-Acked-by: Antoine Tenart <atenart@redhat.com>
    RH-Acked-by: Jiri Benc <jbenc@redhat.com>
    RH-Acked-by: Ivan Vecera <ivecera@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1908340
    Upstream Status: RHEL Only

    Since RHEL8 commit 771c0c0fcd28 ("[tools] selftests: Extract
    run_kselftest.sh and generate stand-alone test list") the selftest
    list will be generated to a separate file kselftest-list.txt based on
    TARGETS.

    But net/forwarding is not in TARGETS. So the final list will not
    contain any forwarding test. This will block the kselftest
    in beaker as we can't find forwarding tests in list file.

    Signed-off-by: Hangbin Liu <haliu@redhat.com>
    Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>
    Signed-off-by: Jan Stancek <jstancek@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc 3d8b614499 kernel.spec: selftests: add build requirement on libmnl-devel
Backport of RHEL8 commit.

commit fa8111b6e3e61955fb9fb67a3e431f9dd48c00ea
Author: Andrea Claudi <aclaudi@redhat.com>
Date:   Fri Dec 11 15:16:26 2020 -0500

    [redhat] rpmspec: add build requirement on libmnl-devel

    Message-id: <20201211151626.65812-1-aclaudi@redhat.com>
    Patchwork-id: 344123
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.4 net PATCH] redhat: add build requirement on libmnl-devel
    Bugzilla: 1899374
    RH-Acked-by: Hangbin Liu <haliu@redhat.com>
    RH-Acked-by: Paolo Abeni <pabeni@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1899374
    Build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=33680624
    Upstream status: RHEL only

    libmnl-devel is needed by netfilter/nf-queue.c, after Hangbin's patchset
    backporting latest set of netfiter selftests.

    Signed-off-by: Andrea Claudi <aclaudi@redhat.com>
    Signed-off-by: Jan Stancek <jstancek@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc 0234d1a95c kernel.spec: add action.o to kernel-selftests-internal
Backport of RHEL8 commit.

commit 0fd69ec14a91d1bc889e2f9abf1ceb9233334eeb
Author: Davide Caratti <dcaratti@redhat.com>
Date:   Tue Nov 24 17:03:55 2020 -0500

    [redhat] redhat: kernel.spec: selftests: add action.o to kernel-selftests-internal

    Message-id: <fcda1fa45c5388e2eda623530832fc497124837d.1606234520.git.dcaratti@redhat.com>
    Patchwork-id: 341690
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.4 PATCH] redhat: kernel.spec: selftests: add action.o to kernel-selftests-internal
    Bugzilla: 1900944
    RH-Acked-by: Jiri Benc <jbenc@redhat.com>
    RH-Acked-by: Hangbin Liu <haliu@redhat.com>
    RH-Acked-by: Ivan Vecera <ivecera@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1900944
    Upstream Status: RHEL Only
    Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=33255259
    Tested:
     # rpm -qlp kernel-selftests-internal-4.18.0-250.el8.bz1900944.x86_64.rpm | grep tc-testing
     verified that:
      - action.o is included
      - all other items are still there
     # rpm -ivh kernel-selftests-internal-4.18.0-250.el8.bz1900944.x86_64.rpm
     # pushd /usr/libexec/tc-testing
     # ./tdc.py -c bpf --nobuildebpf
     # popd
     (verified that all tests are passing)

    Shuang reports that clang/llvm are needed to build action.o, the eBPF
    program used by tdc.py, and the eBPF test program is not shipped
    in kernel-selftests-internal RPM. Now that tdc execution has been made
    compliant to kselftests, it's sufficient to add 'tc-testing' to
    TARGETS, as follows:

     $ make TARGETS="<list of targets>" <kselftests-target>

    Signed-off-by: Davide Caratti <dcaratti@redhat.com>
    Signed-off-by: Jan Stancek <jstancek@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc fd3ccc5f2e kernel.spec: avoid building bpftool repeatedly
Backport of RHEL8 commit.

commit 334cd6472196835d71a4eb0479822e73fa364498
Author: Jiri Benc <jbenc@redhat.com>
Date:   Tue Aug 18 13:38:55 2020 -0400

    [redhat] redhat: avoid building bpftool repeatedly

    Message-id: <5d080c5b61399ad635a271a7ff28a3c63f67d6ff.1597757857.git.jbenc@redhat.com>
    Patchwork-id: 324292
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 64/63] redhat: avoid building bpftool repeatedly
    Bugzilla: 1866908
    RH-Acked-by: Bruno Meneguele <bmeneg@redhat.com>
    RH-Acked-by: Frantisek Hrbata <fhrbata@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1866908
    Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=30777253

    Currently, tools/testing/selftests/bpf/Makefile builds bpftool twice, even
    though it has already been built.

    It is first built as tools/testing/selftests/bpf/tools/build/bpftool/bpftool
    and then a build of runqslower is invoked, which builds bpftool again as
    tools/testing/selftests/bpf/tools/bpftool. This is not only waste of time
    and resources, it's also prone to build errors: the two additional bpftool
    builds are run in parallel from the same base directory. As the result, they
    both try to create profiler.skel.h, which, depending on timing, may lead to
    gcc seeing a truncated include file and failing with weird errors.

    There's a mechanism in the makefile to use an already built bpftool. Let's
    just use it.

    Tested: built and run selftests, everything seems working as it should.
            According to brew logs, bpftool is not built anymore from selftests.

    Signed-off-by: Jiri Benc <jbenc@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc 403cff1c26 kernel.spec: selftests require python3
Backport of RHEL8 commit.

commit b3b5500d7ca7f63e3adcf3dc15aa8be26904180f
Author: Jiri Benc <jbenc@redhat.com>
Date:   Fri Aug 7 13:13:38 2020 -0400

    [redhat] redhat: kernel.spec: selftests require python3

    Message-id: <fd8760bb6ca5055890bbdc5170a36bc0c7164ae5.1596793349.git.jbenc@redhat.com>
    Patchwork-id: 323569
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 59/63] redhat: kernel.spec: selftests require python3
    Bugzilla: 1866908
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1866908

    Upstream: RHEL only

    Fix the following problem when running selftests:

    selftests: bpf: test_bpftool.sh
    ./test_bpftool.sh: line 5: python3: command not found
    not ok 43 selftests: bpf: test_bpftool.sh

    Signed-off-by: Jiri Benc <jbenc@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc d6195989a9 kernel.spec: skip selftests that failed to build
In ARK, the rpm build continues even if some of the selftests cannot be
built. It's not always possible to build selftests, as upstream sometimes
dependens on too new llvm version or has other issues. If something did not
get built, just skip it.

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc 2281aa01d9 kernel.spec: fix installation of bpf selftests
The mentioned commit that blindly copied everything is not included, it
would not make much sense, this patch is completely replacing it.

commit 27bee04408ff1f9dc9257148cdc1a178d847d815
Author: Jiri Benc <jbenc@redhat.com>
Date:   Fri Aug 7 13:13:37 2020 -0400

    [redhat] redhat: kernel.spec: fix installation of bpf selftests

    Message-id: <e86f03cfa84e50ee1cad57c0d102d85321fc1034.1596793349.git.jbenc@redhat.com>
    Patchwork-id: 323567
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 58/63] redhat: kernel.spec: fix installation of bpf selftests
    Bugzilla: 1866908
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1866908

    Upstream status: RHEL only

    RHEL 8 commit 7207d2907bd8 ("[redhat] redhat/kernel.spec: install
    selftests/bpf separately") attempted to fix installation of bpf selftests.
    However, it was blindly copying everything, including source files and build
    artifacts.

    Install only the files that are actually required, that is executable files,
    Python files and BPF object files. There will be also 'settings' file added
    later.

    Signed-off-by: Jiri Benc <jbenc@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc c1f9779acf redhat: fix samples and selftests make options
Backport of RHEL8 commit.
  - small conflict with already added _smp_mflags

commit a4c21259df563abcb973f969ba4d7ff1868475e1
Author: Jiri Benc <jbenc@redhat.com>
Date:   Fri Aug 7 13:13:36 2020 -0400

    [redhat] redhat: fix samples and selftests make options

    Message-id: <df632ec3de2f11a0fb12a2123eb180cb12e0fd64.1596793349.git.jbenc@redhat.com>
    Patchwork-id: 323566
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 57/63] redhat: fix samples and selftests make options
    Bugzilla: 1866908
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1866908

    The make should not be invoked with -s, it causes all information useful for
    build debugging to be missing from the build log. The V=1 is ignored by some
    selftests dirs but honored by others, let's keep it there, it does no harm
    for the dirs where it is not used.

    While touching those make invocations, let's also speed up the build by
    using parallel build.

    Signed-off-by: Jiri Benc <jbenc@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:23 -04:00
Jiri Benc 02eddb947a kernel.spec: enable mptcp selftests for kernel-selftests-internal
Backport of RHEL8 commit.

commit d8dff5bbd040e91ff011d4f03671cc1c91340d0f
Author: Hangbin Liu <haliu@redhat.com>
Date:   Tue Jun 23 07:25:33 2020 -0400

    [redhat] enable mptcp selftests for kernel-selftests-internal

    Message-id: <20200623072533.743131-1-haliu@redhat.com>
    Patchwork-id: 321375
    Patchwork-instance: patchwork
    O-Subject: [PATCH net RHEL8.3] enable mptcp selftests for kernel-selftests-internal
    Bugzilla: 1848230
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Florian Westphal <fwestpha@redhat.com>
    RH-Acked-by: Davide Caratti <dcaratti@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1848230
    Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=29605235
    Upstream status: RHEL only

    We have enabled MPTCP on RHEL8 via bug 1835796. Now enable the
    MPTCP selftest.

    Signed-off-by: Hangbin Liu <haliu@redhat.com>
    Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 73c200cb5b kernel.spec: Do not export shared objects from libexecdir to RPM Provides
Backport of RHEL8 commit.

commit de79ce798e1a04173f6d963379f8e48a92e14b67
Author: Michael Petlan <mpetlan@redhat.com>
Date:   Tue Jun 23 10:15:03 2020 -0400

    [redhat] spec: Do not export shared objects from libexecdir to RPM Provides

    Message-id: <20200623101503.11173-1-mpetlan@redhat.com>
    Patchwork-id: 321392
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 PATCH v2] spec: Do not export shared objects from libexecdir to RPM Provides
    Bugzilla: 1846014
    RH-Acked-by: Jiri Benc <jbenc@redhat.com>
    RH-Acked-by: Rafael Aquini <aquini@redhat.com>
    RH-Acked-by: Jiri Olsa <jolsa@redhat.com>

    Bugzilla: 1846014
    https://bugzilla.redhat.com/show_bug.cgi?id=1846014
    RHEL-only

    The package kernel-selftests-internal incorrectly exported libbpf.so
    as Provides, thus libbpf as perf dependency could have been satisfied
    by kernel-selftests-internal at the RPM level, although the libbpf.so
    file in /usr/libexec could not be used by perf. Don't export the library
    if it's invisible to linker.

    v1 --> v2
    =========
    Narrow the exclusion down to files under kselftests in order not to
    exclude perl modules in libexec.

    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 76f66f94bc kernel.spec: add missing dependency for the which package
Backport of RHEL8 commit.

commit 324e8df74b709bc19533a6ed0259378a290b4a22
Author: Brian Masney <bmasney@redhat.com>
Date:   Fri Apr 24 12:32:20 2020 -0400

    [redhat] kernel.spec: add missing dependency for the which package

    Message-id: <20200424123220.523325-1-bmasney@redhat.com>
    Patchwork-id: 304784
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 BZ 1825838 PATCH v2] [redhat] kernel.spec: add missing dependency for the which package
    Bugzilla: 1825838
    RH-Acked-by: Luis Goncalves <lgoncalv@redhat.com>
    RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
    RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1825838
    Upstream status: RHEL only
    Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28065951
    Tested: build tested on my workstation and on brew

    A RHEL 8.3 build inside a minimal container can fail with the following
    error:

        *** ERROR: Cannot find LLVM tool clang
        make[2]: *** [/usr/src/kernel-rhel/samples/bpf/Makefile:256: verify_cmds] Error 1
        make[1]: *** [Makefile:1718: /usr/src/kernel-rhel/samples/bpf/] Error 2
        make[1]: Leaving directory '/usr/src/kernel-rhel'
        make: *** [Makefile:231: all] Error 2

    clang was installed and the real issue is the missing 'which' binary.
    Let's go ahead and add that to the BuildRequires to avoid other people
    running into this same issue.

    Signed-off-by: Brian Masney <bmasney@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 29977b8b57 kernel.spec: add netfilter selftests to kernel-selftests-internal
Backport of RHEL8 commit.

commit 95d10f186dc4d70cf6e33d0150bfe358fddb6ba5
Author: Hangbin Liu <haliu@redhat.com>
Date:   Wed Apr 22 02:50:59 2020 -0400

    [redhat] add netfilter selftests to kernel-selftests-internal

    Message-id: <20200422025059.11686-5-haliu@redhat.com>
    Patchwork-id: 304491
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 PATCH net 4/4] redhat: add netfilter selftests to kernel-selftests-internal
    Bugzilla: 1826220
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
    RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
    RH-Acked-by: Florian Westphal <fwestpha@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1826220
    Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=28090611
    Upstream status: RHEL only

    This selftest will be used to verify netiflter functions for RHEL

    Signed-off-by: Hangbin Liu <haliu@redhat.com>
    Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 7c04b03d28 kernel.spec: move slabinfo and page_owner_sort debuginfo to tools-debuginfo
Backport of RHEL8 commit.

commit e3b2d7aef8ad82c55b6f526b1e1318aec3b94d8f
Author: Frantisek Hrbata <fhrbata@redhat.com>
Date:   Mon Apr 27 08:53:40 2020 -0400

    [redhat] redhat: move slabinfo and page_owner_sort debuginfo to tools-debuginfo

    Message-id: <20200427085340.GA5962@localhost.localdomain>
    Patchwork-id: 305261
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3] redhat: move slabinfo and page_owner_sort debuginfo to tools-debuginfo
    Bugzilla: 1828178
    RH-Acked-by: Rafael Aquini <aquini@redhat.com>
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1828178
    Upstream Status: RHEL only
    Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=28196548
    Tested: Verified that debuginfo files for slabinfo and page_owner_sort
            are included in tools-debuginfo instead of debuginfo-common

    Commit d06b1385849f3f5c1ff515888865ccb531ba90e9 ("redhat: spec: package and
    ship VM tools"), included in kernel-4.18.0-193.13.el8, added slabinfo and
    page_owner_sort tools. Unfortunatelly it missed to add the debuginfo for
    these tools to tools-debuginfo package. As a result of this there are two
    problems:

    1) The debug info, along with build-id links, is presented in debuginfo-common
       package, which is obviously wrong.

    2) Since debuginfo-common is installonlypkgs the osci installability test fails,
       because of conflicts on these files.
       Error: Transaction test error:
          file /usr/lib/debug/usr/bin/page_owner_sort.debug from install of
               kernel-debuginfo-common-x86_64-4.18.0-193.14.el8.x86_64 conflicts
               with file from package
               kernel-debuginfo-common-x86_64-4.18.0-193.13.el8.x86_64
          file /usr/lib/debug/usr/bin/slabinfo.debug from install of
               kernel-debuginfo-common-x86_64-4.18.0-193.14.el8.x86_64 conflicts
               with file from package
          kernel-debuginfo-common-x86_64-4.18.0-193.13.el8.x86_64

    Fixes: d06b1385849f ("redhat: spec: package and ship VM tools")
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc ba21784af6 kernel.spec: package and ship VM tools
Backport of RHEL8 commit.

commit d06b1385849f3f5c1ff515888865ccb531ba90e9
Author: Rafael Aquini <aquini@redhat.com>
Date:   Mon Apr 20 15:08:53 2020 -0400

    [redhat] redhat: spec: package and ship VM tools

    Message-id: <1621bdede1391140ca7d51c1afd68bd0d9d89e85.1587394443.git.aquini@redhat.com>
    Patchwork-id: 303890
    Patchwork-instance: patchwork
    O-Subject: [RHEL8 PATCH 2/2] redhat: spec: package and ship VM tools
    Bugzilla: 1825432
    RH-Acked-by: Don Dutile <ddutile@redhat.com>
    RH-Acked-by: Aristeu Rozanski <aris@redhat.com>
    RH-Acked-by: Waiman Long <longman@redhat.com>

    Upstream status: RHEL only
    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1825432

    We've been missing these troubleshooting tools in kernel-tools for
    too long already. This patch fixes that by building and packaging
    both page_owner_sort and slabinfo VM kernel tools.

    Signed-off-by: Rafael Aquini <aquini@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 83ac5d7c66 configs: enable CONFIG_PAGE_OWNER
This seems to be generally useful, enabling it also for Fedora. Note that
the feature is inactive and needs to be enabled by a kernel boot parameter.

Skipping the KABI hunk.

commit 9c1a6617fb272f09474a94a3257ee4458eab7c15
Author: Rafael Aquini <aquini@redhat.com>
Date:   Mon Apr 20 15:08:52 2020 -0400

    [redhat] redhat: configs: enable CONFIG_PAGE_OWNER

    Message-id: <a4b1babd75098b8e69cbb00426c27489d6c21915.1587394443.git.aquini@redhat.com>
    Patchwork-id: 303888
    Patchwork-instance: patchwork
    O-Subject: [RHEL8 PATCH 1/2] redhat: configs: enable CONFIG_PAGE_OWNER
    Bugzilla: 1825414
    RH-Acked-by: Don Dutile <ddutile@redhat.com>
    RH-Acked-by: Aristeu Rozanski <aris@redhat.com>
    RH-Acked-by: Waiman Long <longman@redhat.com>

    Upstream status: RHEL only
    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1825414

    Get CONFIG_PAGE_OWNER enabled on the RHEL kernel builds so we
    provide this debug feature to help on extending our ability to
    bug-chase kernel memory usage by 3rd party drivers.

    This will also enable CONFIG_PAGE_EXTENSION, which will cause
    struct mem_section to be extended, as well.

    [jbenc: stripped irrelevant kABI preserving discussion]

    Signed-off-by: Rafael Aquini <aquini@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 0f2c7dee68 kernel.spec: add coreutils
The sh-utils build dependency was removed from ARK. However, those tools are
still needed for the kernel build. Although coreutils are present in the
build environment by default, it still seems to be a good practice to
require them explicitly.

commit 8aa18d3c37c5d057ef2398210dd70915ed26915e
Author: Brian Masney <bmasney@redhat.com>
Date:   Mon Apr 6 15:41:26 2020 -0400

    [redhat] kernel.spec: replace sh-utils dependency with coreutils

    Message-id: <20200406154127.357506-2-bmasney@redhat.com>
    Patchwork-id: 299250
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 BZ 1821336 PATCH v4 1/2] kernel.spec: replace sh-utils dependency with coreutils
    Bugzilla: 1821336
    RH-Acked-by: Rafael Aquini <aquini@redhat.com>
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1821336
    Upstream Status: RHEL only
    Build Info: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=27632566
    Tested: via local RPM build and via brew build.

    As of RHEL 8.0, the sh-utils package is now provided by the coreutils
    package. Newer versions of Fedora don't include the sh-utils provides
    so let's go ahead and update the BuildRequires to depend on coreutils.

    Signed-off-by: Brian Masney <bmasney@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc ef5745dd03 kernel.spec: add netdevsim driver selftests to kernel-selftests-internal
Backport of RHEL8 commit.

commit 188976e5b7d5d5d23e5c640a8da412e0b1216864
Author: Petr Oros <poros@redhat.com>
Date:   Mon Mar 23 14:42:59 2020 -0400

    [redhat] add netdevsim driver selftests to kernel-selftests-internal

    Message-id: <9e902c0a0d2e96360088b691075baee0ac525fee.1584973596.git.poros@redhat.com>
    Patchwork-id: 297250
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 net PATCH 21/21] redhat: add netdevsim driver selftests to kernel-selftests-internal
    Bugzilla: 1805882
    RH-Acked-by: Hangbin Liu <haliu@redhat.com>
    RH-Acked-by: Ivan Vecera <ivecera@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1805882
    Upstream status: RHEL only

    These selftests will be used to verify various functionality implemented
    in netdevsim driver. This is useful for functional as well as regression
    testing. Netdevsim directory curently contain devlink and devlink_trap
    selftests

    Signed-off-by: Petr Oros <poros@redhat.com>
    Signed-off-by: Timothy Redaelli <tredaelli@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 4c767e5443 redhat/Makefile: Clean out the --without flags from the baseonly rule
Backport of RHEL8 commit.

commit 8ecd7aeaa1a53b0e22da4e97aef7d89df292a112
Author: Steve Dickson <SteveD@redhat.com>
Date:   Sun Feb 9 20:37:17 2020 -0500

    [redhat] Makefile: Clean out the --without flags from the baseonly rule

    Message-id: <20200209203717.299715-2-steved@redhat.com>
    Patchwork-id: 294575
    Patchwork-instance: patchwork
    O-Subject: [PATCH 2/2] [PATCH 8.2] [redhat] Makefile: Clean out the --without flags from the baseonly rule.
    Bugzilla: 1797242
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    With the previous patch, the baseonly define undefines unnecessary
    rpms that don't need to be build. So clean out the rh-kernel make
    rule of the not needed --without flags.

    Bugzilla: 1797242
    Upstream: RHEL-only

    Signed-off-by: Steve Dickson <steved@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:22 -04:00
Jiri Benc 5d2ef9e30c kernel.spec: Stop building unnecessary rpms for baseonly builds
Backport of RHEL8 commit.

commit 010b2e366255fc0f30c68f404679f85937d2549c
Author: Steve Dickson <SteveD@redhat.com>
Date:   Sun Feb 9 20:37:16 2020 -0500

    [redhat] kernel.spec.template: Stop building unnecessary rpms for baseonly builds

    Message-id: <20200209203717.299715-1-steved@redhat.com>
    Patchwork-id: 294574
    Patchwork-instance: patchwork
    O-Subject: [PATCH 1/2] [PATCH 8.2 V2] [redhat] kernel.spec.template: Stop building unnecessary rpms for baseonly builds
    Bugzilla: 1797242
    RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    With baseonly builds, undefined a number unnecessary build
    defines so the minimal number of rpms are built

    Bugzilla: 1797242
    Upstream: RHEL-only

    Signed-off-by: Steve Dickson <steved@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Jiri Benc 448c1d4a7a kernel.spec: disable more kabi switches for gcov build
Backport of RHEL8 commit.

commit 128ccd9b6c19f5cce20fac1479d9677623fbfc26
Author: Jan Stancek <jstancek@redhat.com>
Date:   Tue Dec 10 14:53:25 2019 -0500

    [redhat] disable more kabi switches for gcov build

    Message-id: <2e9b8ebc97c9eb430116a118dc8003f44870abf9.1575989369.git.jstancek@redhat.com>
    Patchwork-id: 291825
    O-Subject: [RHEL8.2 PATCH] redhat: disable more kabi switches for gcov build
    Bugzilla: 1781513
    RH-Acked-by: Bruno Eduardo de Oliveira Meneguele <bmeneg@redhat.com>
    RH-Acked-by: Čestmír Kalina <ckalina@redhat.com>
    RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>

    Bugzilla: 1781513
    Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=25255969
    Upstream: RHEL only
    Tested: make rh-srpm-gcov + compile only in brew

    gcov build disables with_kabichk, which makes Source300 undefined.
    But there are still couple kabi switches which use SOURCE300,
    which can cause brew build to fail:

      + tar xjvf '%{SOURCE300}' -C /builddir/build/BUILDROOT/kernel-4.18.0-161.el8.gcov.noarch/lib/modules/
      tar (child): %{SOURCE300}: Cannot open: No such file or directory
      tar (child): Error is not recoverable: exiting now
      tar: Child returned status 2
      tar: Error is not recoverable: exiting now
      RPM build errors:
      error: Bad exit status from /var/tmp/rpm-tmp.lcnD1l (%install)
          Bad exit status from /var/tmp/rpm-tmp.lcnD1l (%install)
      Child return code was: 1

    Signed-off-by: Jan Stancek <jstancek@redhat.com>
    Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Jiri Benc c7f40ccd4a kernel.spec: Rename kabi-dw base
Backport of RHEL8 commit.

commit 327393e3c3c7c5f47eded876edd89e9504f7af34
Author: Čestmír Kalina <ckalina@redhat.com>
Date:   Wed Nov 27 16:49:34 2019 -0500

    [redhat] kernel.spec.template: Rename kabi-dw base

    Message-id: <20191127164934.5427-1-ckalina@redhat.com>
    Patchwork-id: 290368
    O-Subject: [RHEL8.2 PATCH v2] [redhat] kernel.spec.template: Rename kabi-dw base
    Bugzilla: 1700349
    RH-Acked-by: Bruno Eduardo de Oliveira Meneguele <bmeneg@redhat.com>
    RH-Acked-by: Stepan Horacek <shoracek@redhat.com>
    RH-Acked-by: Jiri Benc <jbenc@redhat.com>

    RHBZ: 1700349
    Brew: 24962276

    Per https://projects.engineering.redhat.com/browse/RCM-54000, this patch
    renames: kabidw-base -> kernel-kabidw-base-internal.

    Cc: Jiri Benc <jbenc@redhat.com>
    Cc: tpn Horek <shoracek@redhat.com>
    Cc: Prarit Bhargava <prarit@redhat.com>
    Signed-off-by: estmr Kalina <ckalina@redhat.com>
    Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Jiri Benc e58ff25116 kernel.spec: Fix error messages during build of zfcpdump kernel
Backport of RHEL8 commit.
  - small conflict Flavour/Variant variable names.

commit 1b5714ef1f57ebc640fff6b6498a92f8e60a3699
Author: Philipp Rudo <prudo@redhat.com>
Date:   Tue Aug 27 10:51:21 2019 -0400

    [rpmspec] redhat: Fix error messages during build of zfcpdump kernel

    Message-id: <20190827105121.28041-1-prudo@redhat.com>
    Patchwork-id: 269801
    O-Subject: [RHEL8.2 PATCH] [rpmspec] redhat: Fix error messages during build of zfcpdump kernel
    Bugzilla: 1745652
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Steve Best <sbest@redhat.com>

    Bugzilla: 1745652
    Upstream Status: RHEL-only
    Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=23194083
    Tested: Ran brew build and checked build.log for s390x

    The zfcpdump kernel variant was renamed from 'kdump' to 'zfcpdump' to
    prevent misconception in the transition from RHEL7 to RHEL8. When
    forwardporting the kabi-dw tool it was missed to adjust to the rename
    causing error messages during build like

    + '[' zfcpdump '!=' kdump ']'
    + mkdir -p
    /builddir/build/BUILDROOT/kernel-4.18.0-137.el8.rhel.8.1.0.1743504.bz.s390x/kabi-dwarf
    + tar xjvf /builddir/build/SOURCES/kernel-kabi-dw-4.18.0-137.tar.bz2 -C
    /builddir/build/BUILDROOT/kernel-4.18.0-137.el8.rhel.8.1.0.1743504.bz.s390x/kabi-dwarf
    base/
    run_kabi-dw.sh
    **** Baseline dataset for kABI DWARF-BASED comparison report not found ****

    Fix them by adjusting to the rename. Other than the error messages no
    negative impact is expected. The zfcpdump kernel is not kABI protected.

    Fixes: cbcbf154b64a ("[redhat] kabi: integrate kabi-dw")
    Signed-off-by: Philipp Rudo <prudo@redhat.com>
    Signed-off-by: Phillip Lougher <plougher@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Jiri Benc 2c3bc0a613 kernel.spec: perf: remove bpf examples
Instead of specifying the files one by one, remove the whole
/usr/lib/perf/include directory the same way it is done in RHEL 8.

commit 9da4d617c730e81cf01e5685de5c5a23d6cd3003
Author: Michael Petlan <mpetlan@redhat.com>
Date:   Thu May 23 10:14:56 2019 -0400

    [rpmspec] perf: remove bpf examples

    Message-id: <f2e1d39854d7d06cf9937de75a127d0e9b4ded99.1558604935.git.mpetlan@redhat.com>
    Patchwork-id: 259900
    O-Subject: [RHEL8.1 BZ1709242 189/190] [rpmspec] perf: remove bpf examples
    Bugzilla: 1709242
    RH-Acked-by: Jiri Olsa <jolsa@redhat.com>
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    Bugzilla: 1709242
    https://bugzilla.redhat.com/show_bug.cgi?id=1709242
    Upstream Status: RHEL only

    description
    ===========
    The following files should not be packaged, since they are packaged
    in fedora neither:

       /usr/lib/perf/examples/bpf/5sec.c
       /usr/lib/perf/examples/bpf/augmented_syscalls.c
       /usr/lib/perf/examples/bpf/empty.c
       /usr/lib/perf/examples/bpf/hello.c
       /usr/lib/perf/examples/bpf/sys_enter_openat.c
       /usr/lib/perf/include/bpf/bpf.h
       /usr/lib/perf/include/bpf/stdio.h

    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Jiri Benc a6d374b3ec kernel.spec: selftests should not depend on modules-internal
This dependency doesn't make much sense. It says nothing about the running
kernel, it's possible to have mutliple kernel rpms of different versions
installed.

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Jiri Benc ae6da1eb12 kernel.spec: build samples
Bring back the code to install kernel headers that was removed by ARK commit
3a65b42715 ("Sync up the ARK build scripts") without any explanation. The
headers are needed. Add SMP flags to speed up the build.

Turn on building of samples, reverting ARK commit 9d270db9fd ("Skip
ksamples for bpf, they are broken"). The reason they were broken was the
incorrect drop of the kernel headers installation.

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Jiri Benc fbcbf743c3 kernel.spec: tools: sync missing options with RHEL 8
When the tools_make macro was ported to ARK, one change made in the
original RHEL 8 commit were forgotten: the cpupower tools should be
built without debug (the default is DEBUG=true, which builds without
optimizations).

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:21 -04:00
Phil Sutter 51f8dcf752 redhat/configs: nftables: Enable extra flowtable symbols
There is flowtable support for (the combined IPv4/IPv6) inet family
already, so having the IP-family specific ones disabled seems
artificial.

Signed-off-by: Phil Sutter <psutter@redhat.com>
2021-08-30 14:31:21 -04:00
Phil Sutter ea17bf6175 redhat/configs: Sync netfilter options with RHEL8
These three config symbols were missing although enabled in RHEL8. They
are enabled in Fedora, so move the respective files (and drop the
explicit IP_VS_MH disabler from ark).

Signed-off-by: Phil Sutter <psutter@redhat.com>
2021-08-30 14:31:20 -04:00
Justin M. Forbes 1a3f33df73 Fedora 5.13 config updates pt 2
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:20 -04:00
Fedora Kernel Team a70feb3aae [redhat] New configs in drivers/cxl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CXL_MEM:

 The CXL.mem protocol allows a device to act as a provider of
 "System RAM" and/or "Persistent Memory" that is fully coherent
 as if the memory was attached to the typical CPU memory
 controller.

 Say 'y/m' to enable a driver (named "cxl_mem.ko" when built as
 a module) that will attach to CXL.mem devices for
 configuration, provisioning, and health monitoring. This
 driver is required for dynamic provisioning of CXL.mem
 attached memory which is a prerequisite for persistent memory
 support. Typically volatile memory is mapped by platform
 firmware and included in the platform memory map, but in some
 cases the OS is responsible for mapping that memory. See
 Chapter 2.3 Type 3 CXL Device in the CXL 2.0 specification.

 If unsure say 'm'.

 Symbol: CXL_MEM [=n]
 Type  : tristate
 Defined at drivers/cxl/Kconfig:16
   Prompt: CXL.mem: Memory Devices
   Depends on: CXL_BUS [=y]
   Location:
     -> Device Drivers
       -> PCI support (PCI [=y])
         -> CXL (Compute Express Link) Devices Support (CXL_BUS [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_CXL_MEM set to module
v3:
 - CONFIG_CXL_MEM_RAW_COMMANDS disabled

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:20 -04:00
Justin M. Forbes a19bc84b9c Move CONFIG_ARCH_INTEL_SOCFPGA up a level for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:20 -04:00
Peter Robinson b05111f5e7 fedora: enable the Rockchip rk3399 pcie drivers
Now that we have upstream fixes for the issues with these
drivers when DEBUG_SHIRQ is enabled we can enable pcie for
the rk3399 devices that support this PCIE IP block.

Fixes: RHBZ #1704945
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:20 -04:00
Justin M. Forbes 996e95d958 Fedora 5.13 config updates pt 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:20 -04:00
Justin M. Forbes 75cba49f20 Fix version requirement from opencsd-devel buildreq
MR 1167 added a buildreq for 'opencsd-devel >= 1.0.0-2' on aarch64.
Unfortunately, this version does not exist. The latest build of
opencsd for eln is opencsd-1.0.0-1.eln110.  As of 5.12 kernels, perf
does require opencsd 1.0.0, so let's limit it there.

Cc: Michael Petlan mpetlan@redhat.com

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:20 -04:00
Philipp Rudo 5b5860f3a4 configs/ark/s390: set CONFIG_MARCH_Z14 and CONFIG_TUNE_Z15
Optimize ark for newer machines.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1876435
Signed-off-by: Philipp Rudo <prudo@redhat.com>
2021-08-30 14:31:19 -04:00
Philipp Rudo 734033902c configs/common/s390: Clean up CONFIG_{MARCH,TUNE}_Z*
Most of the configs are identical for fedora and ark so move them to
common/generic/s390x.

While at it move the remaining configs in fedora/generic to
fedora/generic/s390x.

Signed-off-by: Philipp Rudo <prudo@redhat.com>
2021-08-30 14:31:19 -04:00
Philipp Rudo 80f0abae66 configs/process_configs.sh: make use of dummy-tools
Using cc-option adds a dependency on the compiler in the configuration
environment. This usually breaks the config creation when the target
architecture is not the host architecture. As a remedy f88717cf44
("Temporarily switch TUNE_DEFAULT to y") unset failing configs to their
defaults. In the meantime upstream introduced the scripts/dummy-tools,
which are meant to disable cc-option checks by always returning 'y'.
Make use of the dummy-tools and revert the workaround.

Signed-off-by: Philipp Rudo <prudo@redhat.com>
2021-08-30 14:31:19 -04:00
Philipp Rudo 15066da64f configs/common: disable CONFIG_INIT_STACK_ALL_{PATTERN,ZERO}
These configs add option -ftrivial-auto-var-init={pattern,zero} to the
CFLAGS. This option are specific to CLANG and thus are not present on
typical developer systems using GCC. By using the dummy-tools the
cc-option check that tests if these options are present in the current
environment is disabled (i.e. always returns 'y') making the priviously
hidden configs visible. Thus explicitely disable these configs to satisfy
process_configs.sh.

Furthermore these configs are part of a 'choice' from which
CONFIG_INIT_STACK_NONE is selected.

Signed-off-by: Philipp Rudo <prudo@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 14:31:19 -04:00
Philipp Rudo 8e75475b01 configs/common/aarch64: disable CONFIG_RELR
This config adds option --pack-dyn-relocs=relr to the LDFLAGS.  This
option is specific to LLD and thus is not present on typical developer
systems using LD. By using the dummy-tools the cc-option check that
tests if the option is present in the current environment is disabled
(i.e. always returns 'y') making the priviously hidden config visible.
Thus explicitely disable the config to satisfy process_configs.sh.

Signed-off-by: Philipp Rudo <prudo@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
2021-08-30 14:31:19 -04:00
Mark Salter 0071e11087 redhat/config: enable STMICRO nic for RHEL
The STMICRO nic is enabled in RHEL8.4 (aarch64-only) and should be enabled
in ark as well.

Looking at PCS_XPCS, I noticed dead configs for MDIO_XPCS which is the
previous name for PCS_XPCS. So I removed those as well.

Signed-off-by: Mark Salter <msalter@redhat.com>
2021-08-30 14:31:19 -04:00
Mark Salter e66e6f8b8b redhat/configs: Enable ARCH_TEGRA on RHEL
ARCH_TEGRA and SERIAL_8250_TEGRA are enabled in RHEL8.4 and should
be enabled in ark as well.

Fedora currently enables these so I moved those into common/generic/arm.
Enabling ARCH_TEGRA uncovered a number of other Tegra options which needed
to be added for ark (none of which enabled at this point).

Signed-off-by: Mark Salter <msalter@redhat.com>
2021-08-30 14:31:18 -04:00
Fedora Kernel Team 3af08cfa43 [redhat] New configs in drivers/irqchip
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MST_IRQ:

 Support MStar Interrupt Controller.

 Symbol: MST_IRQ [=n]
 Type  : bool
 Defined at drivers/irqchip/Kconfig:584
   Prompt: MStar Interrupt Controller
   Location:
     -> Device Drivers
       -> IRQ chip support
 Selects: IRQ_DOMAIN [=y] && IRQ_DOMAIN_HIERARCHY [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:18 -04:00
Bruno Meneguele a845b0c4c9 redhat/configs: enable IMA_KEXEC for supported arches
In RHEL-8, powerpc has support for IMA_KEXEC, and today, only ppc and
aarch64 supports IMA_KEXEC, which are backed by the HAVE_IMA_KEXEC option.
With that, lets enable it in ARK and also, since the HAVE_* option it's safe
to enable the CONFIG_IMA_KEXEC option as a common/generic option too.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:31:18 -04:00
Bruno Meneguele ab8dc3e410 redhat/configs: enable INTEGRITY_SIGNATURE to all arches
CONFIG_INTEGRITY_SIGNATURE has been enabled for all supported arches in
RHEL-8 and also in Fedora, but I missed it in ARK and, consequently, s390x
missed the CONFIG_IMA_APPRAISE_MODSIG option, which should be set.

However, enabling as generic option also force we to generically disable
CONFIG_IMA_APPRAISE_BUILD_POLICY, which is fine for now.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:31:18 -04:00
Prarit Bhargava 6cb73672af RHMAINTAINERS: Update for June 11 2021
Update RHMAINTAINERS.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:31:18 -04:00
Benjamin Tissoires 8877015262 configs: enable CONFIG_LEDS_BRIGHTNESS_HW_CHANGED
This allows to control the LED brightness of the keyboard on
some Dell XPS laptops.

Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
2021-08-30 14:31:17 -04:00
Fedora Kernel Team c7e495c720 [redhat] New configs in drivers/net/pcs
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PCS_XPCS:

 This module provides helper functions for Synopsys DesignWare XPCS
 controllers.

 Symbol: PCS_XPCS [=n]
 Type  : tristate
 Defined at drivers/net/pcs/Kconfig:8
   Prompt: Synopsys DesignWare XPCS controller
   Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PCS device drivers
 Selects: MDIO_BUS [=y]
 Selected by [n]:
   - STMMAC_ETH [=n] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=n] && HAS_IOMEM [=y] && HAS_DMA [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:17 -04:00
Fedora Kernel Team 3a99fb9da0 [redhat] New configs in drivers/vdpa
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VP_VDPA:

 This kernel module bridges virtio PCI device to vDPA bus.

 Symbol: VP_VDPA [=n]
 Type  : tristate
 Defined at drivers/vdpa/Kconfig:63
   Prompt: Virtio PCI bridge vDPA driver
   Depends on: VDPA [=m] && PCI_MSI [=y]
   Location:
     -> Device Drivers
       -> vDPA drivers (VDPA [=m])
 Selects: VIRTIO_PCI_LIB [=y]

---

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_VP_VDPA enabled as a module.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:17 -04:00
Michael Petlan 8b763d637c [redhat] perf: enable CoreSight support
Bugzilla: https://bugzilla.redhat.com/1877192

Decoding CoreSight needs opencsd-devel package at build-time and
opencsd package as runtime dependency. This feature is aarch64-only.

Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 14:31:17 -04:00
Fedora Kernel Team cb4589993c [redhat] New configs in mm/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CMA_SYSFS:

 This option exposes some sysfs attributes to get information
 from CMA.

 Symbol: CMA_SYSFS [=n]
 Type  : bool
 Defined at mm/Kconfig:532
   Prompt: CMA information through sysfs interface
   Depends on: CMA [=y] && SYSFS [=y]
   Location:
     -> Memory Management options
       -> Contiguous Memory Allocator (CMA [=y])

---

Cc: Rafael Aquini <aquini@redhat.com>
Cc: Aristeu Rozanski <arozansk@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Cc: Nico Pache <npache@redhat.com>
Cc: Waiman Long <longman@redhat.com>
Cc: mm-maint@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_CMA_SYSFS enabled.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:17 -04:00
Fedora Kernel Team 135ded3cf5 [redhat] New configs in fs/cifs
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CIFS_SWN_UPCALL:

 The Service Witness Protocol (SWN) is used to get notifications
 from a highly available server of resource state changes. This
 feature enables an upcall mechanism for CIFS which contacts a
 userspace daemon to establish the DCE/RPC connection to retrieve
 the cluster available interfaces and resource change notifications.
 If unsure, say Y.

 Symbol: CIFS_SWN_UPCALL [=n]
 Type  : bool
 Defined at fs/cifs/Kconfig:193
   Prompt: SWN feature support
   Depends on: NETWORK_FILESYSTEMS [=y] && CIFS [=m]
   Location:
     -> File systems
       -> Network File Systems (NETWORK_FILESYSTEMS [=y])
         -> SMB3 and CIFS support (advanced network filesystem) (CIFS [=m])

---

Cc: kernel-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:17 -04:00
Jeff Moyer 60ea9a255a RHEL: disable io_uring support
Bugzilla: 1964537
Upstream Status: RHEL only

io_uring is still under very active development.  Disable support
for now.  We will reassess this decision each minor release.

Note: this is a temporary patch which can be reverted after RHEL 9
branches from ark.

Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
2021-08-30 14:31:16 -04:00
CKI Gitlab 8fca104a80 [redhat] New configs in drivers/hwtracing 2021-08-30 14:31:16 -04:00
CKI Gitlab 84f9e7e200 [redhat] New configs in drivers/hid 2021-08-30 14:31:16 -04:00
Frank Ramsay bae2f9383e all: Changing CONFIG_UV_SYSFS to build uv_sysfs.ko as a loadable
module.

There is no advantage to this being a built-in; and the vendor prefers
it being a loadable module.

signed-off-by: Frank Ramsay <framsay@redhat.com>
2021-08-30 14:31:16 -04:00
Fedora Kernel Team b097c796b8 [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AD5766:

 Say yes here to build support for Analog Devices AD5766, AD5767
 Digital to Analog Converter.

 To compile this driver as a module, choose M here: the
 module will be called ad5766.

 Symbol: AD5766 [=n]
 Type  : tristate
 Defined at drivers/iio/dac/Kconfig:192
   Prompt: Analog Devices AD5766/AD5767 DAC driver
   Depends on: IIO [=m] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Digital to analog converters

---

 CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE:

 This sensor present three angles, hinge angel, screen angles
 and keyboard angle respect to horizon (ground).
 Say yes here to build support for the HID custom
 intel hinge sensor.

 To compile this driver as a module, choose M here: the
 module will be called hid-sensor-custom-hinge.

 Symbol: HID_SENSOR_CUSTOM_INTEL_HINGE [=n]
 Type  : tristate
 Defined at drivers/iio/position/Kconfig:19
   Prompt: HID Hinge
   Depends on: IIO [=m] && HID_SENSOR_HUB [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Linear and angular position sensors
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && HID_SENSOR_IIO_COMMON [=m] && HID_SENSOR_IIO_TRIGGER [=m]

---

 CONFIG_YAMAHA_YAS530:

 Say Y here to add support for the Yamaha YAS530 series of
 3-Axis Magnetometers. Right now YAS530, YAS532 and YAS533 are
 fully supported.

 This driver can also be compiled as a module.
 To compile this driver as a module, choose M here: the module
 will be called yamaha-yas.

 Symbol: YAMAHA_YAS530 [=n]
 Type  : tristate
 Defined at drivers/iio/magnetometer/Kconfig:208
   Prompt: Yamaha YAS530 family of 3-Axis Magnetometers (I2C)
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Magnetometer sensors
 Selects: REGMAP_I2C [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:16 -04:00
Vitaly Kuznetsov aca2fec63a Enable NITRO_ENCLAVES on RHEL
Nitro Enclaves driver is enabled in RHEL8 and should remain enabled. Move
the config setting from fedora/ to common/.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
2021-08-30 14:31:16 -04:00
David Ward 235912c36d Update the Quick Start documentation
Explicitly use shell formatting for code blocks. Move instructions for pull
mirroring outside of a code block.

Provide a link that takes users to their own fork of the repository. Add a
link for users to register their SSH key in GitLab.

Remove a comment about creating a symlink at /usr/libexec/python-platform,
which is not necessary since commit a069f47f6141. Remove unneeded commands
for checking out the 'os-build' branch or pulling updates immediately after
cloning the repository.

Differentiate between building source and binary RPM packages, which happen
in separate steps. Since the examples use Koji or Mock, the kernel's build
dependencies do not need to be installed locally.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:16 -04:00
Eric Auger 8e8f5623b4 redhat/configs: Set PVPANIC_MMIO for x86 and PVPANIC_PCI for aarch64
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1961178
Upstream Status: RHEL only
Tested: on x86 with libvirt, on ARM with qemu as pvpanic-pci is not
        yet integrated in libvirt

With the introduction of pvpanic-pci new configs were introduced
for the MMIO and PCI flavour. On x86, currently none is set so
the ISA device is not available (this is a regression). The MMIO
flavour must be used on x86_64.

On ARM, the PCI one must be set.

Signed-off-by: Eric Auger <eric.auger@redhat.com>

---

v1 -> v2:
- s/y/m for PCI and MMIO configs
2021-08-30 14:31:15 -04:00
Jiri Olsa 786ca1cae5 bpf: Fix unprivileged_bpf_disabled setup
There's recent change [1] that adds new config option and sets
unprivileged_bpf_disabled to 2 if the option is enabled
(CONFIG_BPF_UNPRIV_DEFAULT_OFF).

The current RHEL specific behaviour is to set unprivileged_bpf_disabled
to 1 by default and add boot command line argument to enable
unpriv bpf.

The config option is enabled in previous patch, adding the taint
for proc/sysctl unprivileged_bpf_disabled setup.

  # sysctl kernel.unprivileged_bpf_disabled
  kernel.unprivileged_bpf_disabled = 2
  # cat /proc/sys/kernel/tainted
  0
  # sysctl kernel.unprivileged_bpf_disabled=0
  [   45.751085] Unprivileged BPF has been enabled, tainting the kernel
  kernel.unprivileged_bpf_disabled = 0
  # sysctl kernel.unprivileged_bpf_disabled=1
  kernel.unprivileged_bpf_disabled = 1
  # sysctl kernel.unprivileged_bpf_disabled=0
  sysctl: setting key "kernel.unprivileged_bpf_disabled": Operation not permitted
  # sysctl kernel.unprivileged_bpf_disabled=2
  sysctl: setting key "kernel.unprivileged_bpf_disabled": Operation not permitted
  # cat /proc/sys/kernel/tainted
  2147483648

[1] 08389d8882 ("bpf: Add kconfig knob for disabling unpriv bpf by default")
[2] 607f0e89af7e ("bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter")

Fixes: 607f0e89af7e ("bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter")
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:15 -04:00
Jiri Olsa 0015eb657f Enable CONFIG_BPF_UNPRIV_DEFAULT_OFF
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:31:15 -04:00
Fedora Kernel Team 6d510f1d92 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:15 -04:00
Fedora Kernel Team 6ee740fe2e [redhat] AUTOMATIC: New configs 2021-08-30 14:31:15 -04:00
Thomas Huth b9d1b661a4 [redhat] configs: Enable CONFIG_VIRTIO_FS on s390x, too
With the recent kernel versions, it is possible now to use virtio-fs
on s390x machines, too. Remove the s390x-specific CONFIG_VIRTIO_FS
file, so that this feature now also gets enabled via the generic
CONFIG_VIRTIO_FS=m setting on s390x, too.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1871130
Signed-off-by: Thomas Huth <thuth@redhat.com>
2021-08-30 14:31:15 -04:00
Philipp Rudo a10556e069 configs/common/s390: disable CONFIG_QETH_{OSN,OSX}
Shipment of the devices required for these options were ceased with z13.
With the ALS set to z14 for ark there is no need to keep the options
enabled.

v2: disable the configs for fedora as well

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1903201
Signed-off-by: Philipp Rudo <prudo@redhat.com>
2021-08-30 14:31:15 -04:00
Antoine Tenart ed0d36ab65 [redhat] Flip some diag modules from m to y
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1948340
Upstream Status: RHEL only
Tested: Instructions in the first comment in bz1948340.

Diag modules are required when investigating sockets with the `ss` tool,
and are loaded on-demand. This is also what happens when using the
`sosreport` tool. Recent discussions pointed out it was not always
possible to load extra modules on a production system, for various
reasons, and the `sosreport` tool was updated to avoid modules to be
loaded by default. Links to the discussions are available in the bz.

The issue is with this policy the `ss` command is now skipped, except if
the administrator explicitly allows it to do so or if diag modules are
already loaded. This results in a loss of valuable information when
generating an `sosreport`, impacting the following investigation.

This patch enables a set of selected DIAG modules to be built-in, so
that `ss` and `sosreport` can be used without loading additional
modules (only diag modules not depending on another loadable module were
considered):

- CONFIG_INET_DIAG
- CONFIG_INET_RAW_DIAG
- CONFIG_INET_TCP_DIAG
- CONFIG_INET_UDP_DIAG
- CONFIG_INET_MPTCP_DIAG
- CONFIG_NETLINK_DIAG
- CONFIG_PACKET_DIAG
- CONFIG_UNIX_DIAG

The generated configuration do not enable any additional non-listed
options with this change. The kernel image increase in size is very
minimal.

Signed-off-by: Antoine Tenart <atenart@redhat.com>
2021-08-30 14:31:15 -04:00
Vladis Dronov 74726adf8c [redhat] Add CONFIG_SYSTEM_REVOCATION_KEYS and _LIST
Add CONFIG_SYSTEM_REVOCATION_KEYS and CONFIG_SYSTEM_REVOCATION_LIST options.
Make them disabled since there are no revoked certificates embedded.

Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0e22b47f650
Link: https://gitlab.com/redhat/rhel/src/kernel/rhel-8/-/merge_requests/456
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1893793
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:31:15 -04:00
Mike Snitzer ba63ad6afc nvme: nvme_mpath_init remove multipath check
BZ: 1948690
Upstream Status: RHEL-only

Signed-off-by: Mike Snitzer <snitzer@redhat.com>

rhel-8.git commit f027c2e4045d02d103c7a545181b6df0b6162ee7
Author: David Milburn <dmilburn@redhat.com>
Date:   Wed Jan 29 15:29:37 2020 -0500

    [nvme] nvme: nvme_mpath_init remove multipath check

    Message-id: <1580311777-9193-1-git-send-email-dmilburn@redhat.com>
    Patchwork-id: 294254
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.2 PATCH] nvme: nvme_mpath_init remove multipath check
    Bugzilla: 1790958
    RH-Acked-by: Gopal Tiwari <gtiwari@redhat.com>
    RH-Acked-by: Ewan Milne <emilne@redhat.com>

    Marco Patalano found missing NVMe optimized/inaccessible paths when
    executing "nvme list-subsys" command with native multipathing disabled.
    He was able to git bisect this back to 6d0f426e ("nvme: fix multipath
    crash when ANA is deactivated"). The problem is the check for multipath,
    removing this is similar to RHEL commit 158eef2e ("nvme: allow ANA support
    to be independent of native multipathing"), I did leave the existing
    comment in place for future back ports and as a reminder to watch for
    these changes in the future.

    Bugzilla: 1790958
    Build info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=26061480
    Upstream: RHEL only
    Test: QE verified "nvme list-subsys" command and did sanity check with native
    multipathing disabled.

    Fixes: 6d0f426e ("nvme: fix multipath crash when ANA is deactivated")
    Signed-off-by: David Milburn <dmilburn@redhat.com>
    Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:31:14 -04:00
Fedora Kernel Team d8fad0407d [redhat] AUTOMATIC: New configs 2021-08-30 14:31:14 -04:00
Fedora Kernel Team dfd8156133 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:14 -04:00
Michael Petlan 7b504d56cd [redhat] perf: link libtraceevent dynamically
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1952426

Due to independent usage of libtraceevent by various users (perf, trace-cmd),
it now exists as a separate package, which provides the library+plugins. Now
perf has to link against it and not install its own libtraceevent, since that
would conflict.

v1 --> v2
=========
Rebased to latest os-build branch.

Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 14:31:14 -04:00
Hangbin Liu bf35094111 team: mark team driver as deprecated
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945477
Upstream: RHEL only

We are planning to deprecate Teaming in RHEL 9 and remove it in RHEL 10.
Teaming and Bonding offer similar functionalities and are causing confusion
for our customers. In the past, Bonding was not keeping up-to-date and
hence Teaming was an option being pursued. Bonding now is keeping current
and also widely adopted by our customers. Hence, it makes sense to keep
Bonding as our preferred option going forward and avoid causing un-necessary
confusion.

Signed-off-by: Hangbin Liu <haliu@redhat.com>
2021-08-30 14:31:14 -04:00
Simo Sorce bd21a6f4f1 Make CRYPTO_EC also builtin
Our current plan is to build crypto modules that we may want to certify
with FIPS-140-3 statically in the kernel.

So add ECDH and ECDSA as well. We currently already claim ECDSA in RHEL-8
kernels. Adding ECDH for completeness.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Simo Sorce <simo@redhat.com>
2021-08-30 14:31:14 -04:00
David Ward ef5811fb7b Do not hard-code a default value for DIST
DIST defaults to '.fc33' if it is not set (which no longer corresponds to
Fedora Rahwide). Obtain the default value from the RPM macros instead.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:14 -04:00
David Ward 8d44f92a78 Override %{debugbuildsenabled} if the --with-release option is used
This option had no effect. Test for it so that %{debugbuildsenabled}
can be overridden at build time without modifying the SPEC file.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:14 -04:00
David Ward c38acb17d2 Improve comments in SPEC file, and move some option tests and macros
Fix the descriptions of the %{released_kernel} and %{debugbuildsenabled}
macros to match their current usage. Also improve a comment that appears
above the build option tests.

Move the tests for --without-zfcpdump and --without-vdso-install so they
are located next to related build options. Also move the definitions of
%{debugbuildsenabled} and %{kversion} to be next to related definitions.

This commit does not make any functional changes to the SPEC file.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:14 -04:00
Pavel Reichl 64ae2e0143 configs: enable CONFIG_EXFAT_FS
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1943423

Upstream: RHEL only

Enable CONFIG_EXFAT_FS as requested in the bugzilla. Config
CONFIG_EXFAT_DEFAULT_IOCHARSET is needed by exFAT.

Remove the fedora specific configs and enable them in common folder.
Do not enable the option on s390x-zfcpdump kernel to avoid
configuration 'mismatch warning'.

Signed-off-by: Pavel Reichl <preichl@redhat.com>
2021-08-30 14:31:14 -04:00
Vladis Dronov 29fae260aa Revert s390x/zfcpdump part of a9d179c40281 and ecbfddd98621
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:31:13 -04:00
Vladis Dronov dce7d82649 Embed crypto algos, modes and templates needed in the FIPS mode
Currently a number of FIPS-allowed algorithms are built as modules or are
not enabled in Fedora and ARK. This can result in a panic while booting
in the FIPS mode. Fix this by embedding the FIPS-allowed algorithms, modes
and templates into a kernel, the same way as CTC, CBC and other algorithms
already do.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:31:13 -04:00
Mohammed Gamal 7da5247417 configs: Add and enable CONFIG_HYPERV_TESTING for debug kernels
CONFIG_HYPERV_TESTING=y is needed for some testing tools in the
hyperv-daemons package. Enable it for debug kernels

Signed-off-by: Mohammed Gamal <mgamal@redhat.com>
2021-08-30 14:31:13 -04:00
David Hildenbrand c56f9f652d mm/cma: mark CMA on x86_64 tech preview and print RHEL-specific infos
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945002
Upstream: RHEL only

CMA is Tech Preview in RHEL 9 for x86_64; to detect the use of CMA easily,
taint the kernel via mark_tech_preview(). Further print an info when
cma_alloc() is getting called for the first time.

Keep s390x (for vmcp) and ppc64 (for KVM) unmodified, as they have been
automatically creating CMA regions already in RHEL 8.

Signed-off-by: David Hildenbrand <david@redhat.com>
2021-08-30 14:31:13 -04:00
David Hildenbrand e89018a7e5 configs: enable CONFIG_CMA on x86_64 in ARK
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945002
Upstream: RHEL only

Enable CONFIG_CMA on x86_64 in ARK as we already have in fedora; move the
relevant configs from redhat/configs/fedora to redhat/configs/common.

As one example CMA will be required to eventually support RDMA<->GPU
p2pdma via dma-buf. As another example, CMA will be useful useful for more
reliable runtime allocation of gigantic pages.

Let's keep CONFIG_DMABUF_HEAPS_CMA disabled for now -- we'll enable it
separately, via a different BZ in the future.

Note that:
* CONFIG_DMA_CMA=Y has to be set due to FB_HYPERV, which force-enables it
  via "select DMA_CMA if HAVE_DMA_CONTIGUOUS && CMA"
* CONFIG_CMA_AREAS has to be configured due to CONFIG_CMA; use the fedora
  value (7). We can bump it up once we actually need more areas.
* CONFIG_CMA_DEBUG and CONFIG_CMA_DEBUGFS have to be configured due to
  CONFIG_CMA; use the fedora values, which disables both.
* CONFIG_DMA_PERNUMA_CMA has to be configured due to CONFIG_DMA_CMA; use
  the fedora value, which disables it. We can enable once we actually
  need it.
* CONFIG_CMA_ALIGNMENT, CONFIG_CMA_SIZE_MBYTES, CONFIG_CMA_SIZE_SEL_MAX,
  CONFIG_CMA_SIZE_SEL_MBYTES, CONFIG_CMA_SIZE_SEL_MIN,
  CONFIG_CMA_SIZE_SEL_PERCENTAGE have to be configured due to
  CONFIG_DMA_CMA; use the fedora values, which correspond to the defaults
  * 1MiB alignment of buffers
  * CMA being disabled, requiring explicit "cma=size[MG]" on the cmdline

Signed-off-by: David Hildenbrand <david@redhat.com>
2021-08-30 14:31:13 -04:00
Herton R. Krzesinski f49dda09a4 rpmspec: build debug-* meta-packages if debug builds are disabled
During upstream git snapshot builds, Fedora uses the debug configs to
build the main kernels, and drops the *-debug package variants. However
if someone installs a kernel-debug package for example it'll not update
until the next non-snapshot build. So add support to keep the debug
packages around even for snapshot builds, however in this case, they
will be just meta-packages requiring the main kernel-* packages built
with debug configs.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:31:13 -04:00
Aristeu Rozanski 8ec7aaa463 UIO: disable unused config options
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1957819
Tested: locally with dist-rhel-configs
Upstream Status: RHEL only

This patch disables unused UIO config options. See

	https://bugzilla.redhat.com/show_bug.cgi?id=1957819#c0

for more details

Signed-off-by: Aristeu Rozanski <arozansk@redhat.com>
2021-08-30 14:31:13 -04:00
Michael Petlan 3cfff18746 [redhat] perf: enable CTF support
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1957305

CTF support in perf needs libbabeltrace-devel to be present at buildtime.

Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 14:31:12 -04:00
Hans de Goede dc99e7e1c6 ARK-config: Make amd_pinctrl module builtin
The GPIOs provided by the AMD pinctrl module may be used by various
ACPI methods (e.g. _PS0, _PS3) and resources (GpioInt). These ACPI
uses may happen before the module has a chance to load when amd_pinctrl
is build as a module.

Change the CONFIG_PINCTRL_AMD option to y, so that the amd_pinctrl
code gets built into the kernel to fix this. This specifically fixes
I2C-HID touchpads on AMD based laptops sometimes not working at boot.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1634832
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1957203
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 14:31:12 -04:00
CKI Gitlab c2d336b35a [redhat] New configs in drivers/gpu 2021-08-30 14:31:12 -04:00
Mike Snitzer ee787de866 [redhat] enable CONFIG_DM_VERITY_FEC in ARK
Enabling CONFIG_DM_VERITY_FEC in terms of common/ because Fedora already
has it enabled.

Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2021-08-30 14:31:12 -04:00
Herton R. Krzesinski 381a9b58ec rpmspec: revert/drop content hash for kernel-headers
This was a change done in the RHEL 8 kernel package, with the purpose
of providing means to other tools to determine if the kernel-headers
changed between package updates. For example, linux containers that
only install kernel-headers would not be flagged for the need of CVE
updates if kernel-headers didn't change, in case of kernel CVEs that
didn't affect the headers.

But this content hash ended up never being used and AFAIK there
were no users. The need to avoid kernel CVEs flagging containers needing
updates only because of kernel-headers installed but not affected,
was handled through changes made in Red Hat's errata tool, and the
content hash here has no use anymore.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:31:12 -04:00
Herton R. Krzesinski 7de5d1bd72 rpmspec: fix check that calls InitBuildVars
InitBuildVars is only called in case BuildKernel is not called (because
it already calls InitBuildVars), and that is done eg. when all kernel
builds are disabled but still building of tools is wanted which needs
the definitions/variables it declares. However, the check is missing the
case when armv7hl with_pae is enabled which already called
BuildKernel->InitBuildVars, this just adds the missing check.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:31:12 -04:00
Damien Le Moal a8c54da107 fedora: enable zonefs
Fedora generic kernel config enables support for zoned block devices
with CONFIG_BLK_DEV_ZONED=y. The dm-zoned device mapper target is also
already enabled with CONFIG_DM_ZONED=m. When kernel 5.12 is introduced,
this default configuration will also enable btrfs native zoned block
device support.

Complete Fedora zoned block device ecosystem by enabling als zonefs as a
module. zonefs was introduced in kernel 5.6 and is already supported by
util-linux libblkid. A request for the zonefs-tools package will be sent
too for completes.

Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
2021-08-30 14:31:12 -04:00
CKI Gitlab 5f088fdf74 [redhat] New configs in fs/netfs 2021-08-30 14:31:12 -04:00
Bruno Meneguele c14ab9088a redhat: load specific ARCH keys to INTEGRITY_PLATFORM_KEYRING
In the current upstream kernel state all RHEL supported arches (aarch64,
x86_64, s390x and powerpc) supports loading platform keys (coming from the
boot process) to a trusted keyring in the system.

This patch enables CONFIG_INTEGRITY_PLATFORM_KEYRING to all ARK arches and
each CONFIG_LOAD_<arch>_KEYS to their respective architecture folder.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:31:11 -04:00
Bruno Meneguele 6887026c73 redhat: enable INTEGRITY_TRUSTED_KEYRING across all variants
This CONFIG option deprecates CONFIG_IMA_TRUSTED_KEYRING, however the old
one is still being required by some other options in upstream, that's why we
don't remove it yet.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:31:11 -04:00
Bruno Meneguele 0c5ca9e787 redhat: enable SYSTEM_BLACKLIST_KEYRING across all variants
It was already supported in Fedora/generic. Does the same for all ARK
arches.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:31:11 -04:00
Bruno Meneguele c10a51f5d0 redhat: enable INTEGRITY_ASYMMETRIC_KEYS across all variants
INTEGRITY_ASYMMETRIC_KEYS was already enabled in Fedora/generic/. This patch
adds it to common/generic because all supported ARK arches supports it.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:31:11 -04:00
Tom Stellard e0f415df54 [redhat] spec: Be more consistent about using %{make_opts} when invoking make
This change passes %{make_opts} to make when using the perf_make,
tools_make, and bpftool_make macros.  The main effect of this change
is that these macros will correctly set CC=clang when the --with
toolchain_clang option is passed to rpmbuild.

Additionally, this change also affects the verbosity of the make output
when these macros are used:

perf_make:
 * Before was always passing the -s (silent) flag.
 * Now will pass -s flag by default and V=1 (verbose) arg when
    --with verbose option is passed to rpmbuild.

tools_make and bfptool_make:
 * Before was always passing V=1 arg.
 * Now will pass -s flag by default and V=1 arg when
   --with verbose option is passed to rpmbuild.

Signed-off-by: Tom Stellard <tstellar@redhat.com>
2021-08-30 14:31:11 -04:00
Fedora Kernel Team 3e66f476ac [redhat] New configs in drivers/net/ethernet/microsoft
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MICROSOFT_MANA:

 This driver supports Microsoft Azure Network Adapter (MANA).
 So far, the driver is only supported on X86_64.

 To compile this driver as a module, choose M here.
 The module will be called mana.

 Symbol: MICROSOFT_MANA [=n]
 Type  : tristate
 Defined at drivers/net/ethernet/microsoft/Kconfig:18
   Prompt: Microsoft Azure Network Adapter (MANA) support
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MICROSOFT [=y] && PCI_MSI [=y] && X86_64 [=y] && PCI_HYPERV [=m]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
           -> Microsoft Network Devices (NET_VENDOR_MICROSOFT [=y])

---

 CONFIG_NET_VENDOR_MICROSOFT:

 If you have a network (Ethernet) device belonging to this class, say Y.

 Note that the answer to this question doesn't directly affect the
 kernel: saying N will just cause the configurator to skip the
 question about Microsoft network devices. If you say Y, you will be
 asked for your specific device in the following question.

 Symbol: NET_VENDOR_MICROSOFT [=y]
 Type  : bool
 Defined at drivers/net/ethernet/microsoft/Kconfig:5
   Prompt: Microsoft Network Devices
   Depends on: NETDEVICES [=y] && ETHERNET [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_MICROSOFT_MANA enabled as module

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:11 -04:00
Phil Sutter 0024f4e10a [redhat] Disable CONFIG_NETFILTER_XTABLES_COMPAT
This setting seems to have slipped through review process: Before this
symbol was introduced, the relevant feature was always enabled. Since it
is there now, we should use the opportunity to disable it and avoid any
further security holes it may contain in addition to the already fixed
ones.
2021-08-30 14:31:10 -04:00
David Ward e71ca26029 Remove unused boot loader specification files
The files generated by this package are not used. See comments in !1042.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:10 -04:00
Alaa Hleihel 584947e957 redhat/configs: Enable mlx5 IPsec and TLS offloads
Enable the needed configs for turning on the mlx5 IPsec and TLS offloads.

Bugzilla: http://bugzilla.redhat.com/1957636
Bugzilla: http://bugzilla.redhat.com/1869674
Upstream: RHEL-only

Signed-off-by: Alaa Hleihel <ahleihel@redhat.com>
2021-08-30 14:31:10 -04:00
Fedora Kernel Team 816e91e9bc [redhat] New configs in drivers/net/ethernet/broadcom
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NET_VENDOR_BROADCOM:

 If you have a network (Ethernet) chipset belonging to this class,
 say Y.

 Note that the answer to this question does not directly affect
 the kernel: saying N will just cause the configurator to skip all
 the questions regarding Broadcom chipsets. If you say Y, you will
 be asked for your specific chipset/driver in the following questions.

 Symbol: NET_VENDOR_BROADCOM [=y]
 Type  : bool
 Defined at drivers/net/ethernet/broadcom/Kconfig:6
   Prompt: Broadcom devices
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && (SSB_POSSIBLE [=y] && HAS_DMA [=y] || PCI [=y] || BCM63XX || SIBYTE_SB1xxx_SOC)
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
 Selected by [n]:
   - SCSI_BNX2_ISCSI [=n] && SCSI_LOWLEVEL [=y] && SCSI [=y] && NET [=y] && PCI [=y] && (IPV6 [=y] || IPV6 [=y]=n) && MMU [=y]
   - SCSI_BNX2X_FCOE [=n] && SCSI_LOWLEVEL [=y] && SCSI [=y] && PCI [=y] && (IPV6 [=y] || IPV6 [=y]=n) && LIBFC [=m] && LIBFCOE [=m] && MMU [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:10 -04:00
Justin M. Forbes 6a52ed4064 Force DWARF4 because crash does not support DWARF5 yet
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:10 -04:00
Fedora Kernel Team db23e154f5 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:10 -04:00
Fedora Kernel Team 7cefe76e59 [redhat] New configs in drivers/vdpa
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_IFCVF:

 This kernel module can drive Intel IFC VF NIC to offload
 virtio dataplane traffic to hardware.
 To compile this driver as a module, choose M here: the module will
 be called ifcvf.

 Symbol: IFCVF [=n]
 Type  : tristate
 Defined at drivers/vdpa/Kconfig:28
   Prompt: Intel IFC VF vDPA driver
   Depends on: VDPA [=m] && PCI_MSI [=y]
   Location:
     -> Device Drivers
       -> vDPA drivers (VDPA [=m])

---

 CONFIG_MLX5_VDPA_NET:

 VDPA network driver for ConnectX6 and newer. Provides offloading
 of virtio net datapath such that descriptors put on the ring will
 be executed by the hardware. It also supports a variety of stateless
 offloads depending on the actual device used and firmware version.

 Symbol: MLX5_VDPA_NET [=n]
 Type  : tristate
 Defined at drivers/vdpa/Kconfig:45
   Prompt: vDPA driver for ConnectX devices
   Depends on: VDPA [=m] && MLX5_CORE [=m]
   Location:
     -> Device Drivers
       -> vDPA drivers (VDPA [=m])
 Selects: MLX5_VDPA [=n]

---

 CONFIG_VDPA_SIM:

 Enable this module to support vDPA device simulators. These devices
 are used for testing, prototyping and development of vDPA.

 Symbol: VDPA_SIM [=n]
 Type  : tristate
 Defined at drivers/vdpa/Kconfig:12
   Prompt: vDPA device simulator core
   Depends on: VDPA [=m] && RUNTIME_TESTING_MENU [=y] && HAS_DMA [=y]
   Location:
     -> Device Drivers
       -> vDPA drivers (VDPA [=m])
 Selects: DMA_OPS [=y] && VHOST_RING [=n]

---

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_IFCVF enable as a module.
 - CONFIG_MLX5_VDPA_NET enable as a module.
 - CONFIG_VDPA_SIM enable as a module.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:10 -04:00
Fedora Kernel Team 3d1358ce0d [redhat] New configs in drivers/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INTEL_IDXD_PERFMON:

 Enable performance monitor (pmu) support for the Intel(R)
 data accelerators present in Intel Xeon CPU.  With this
 enabled, perf can be used to monitor the DSA (Intel Data
 Streaming Accelerator) events described in the Intel DSA
 spec.

 If unsure, say N.

 Symbol: INTEL_IDXD_PERFMON [=n]
 Type  : bool
 Defined at drivers/dma/Kconfig:303
   Prompt: Intel Data Accelerators performance monitor support
   Depends on: DMADEVICES [=y] && INTEL_IDXD [=m]
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
         -> Intel Data Accelerators support (INTEL_IDXD [=m])

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_INTEL_IDXD_PERFMON enabled for x86.

 Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:09 -04:00
Peter Robinson 554e90d487 common: disable Apple Silicon generally
ATM the Apple Silicon isn't useful for the average user, those that
want to experiment will be building their own kernel (and HW adapters).

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:09 -04:00
Fedora Kernel Team e65b17210c [redhat] New configs in drivers/net/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MARVELL_88X2222_PHY:

 Support for the Marvell 88X2222 Dual-port Multi-speed Ethernet
 Transceiver.

 Symbol: MARVELL_88X2222_PHY [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:204
   Prompt: Marvell 88X2222 PHY
   Depends on: NETDEVICES [=y] && PHYLIB [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])

---

 CONFIG_NXP_C45_TJA11XX_PHY:

 Enable support for NXP C45 TJA11XX PHYs.
 Currently supports only the TJA1103 PHY.

 Symbol: NXP_C45_TJA11XX_PHY [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:237
   Prompt: NXP C45 TJA11XX PHYs
   Depends on: NETDEVICES [=y] && PHYLIB [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])

---

Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:09 -04:00
Michael Petlan e484ba724e [redhat] perf: enable dynamic linking of libbpf
Bugzilla: https://bugzilla.redhat.com/1957210
Upstream: RHEL-only

description
===========
Enable dynamic linking of perf against libbpf. Also, libbpf-devel
becomes a build-dependency for kernel.src.rpm and libbpf becomes
a runtime dependency for perf.rpm.

Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 14:31:09 -04:00
Peter Robinson 305d1996e6 cleanup Intel's FPGA configs
Intel consolidated the architecture definitions around it's Arm based
FPGA SoCs into a single architecture definition, so clean this up (NFC).

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:09 -04:00
Peter Robinson 701e4437e5 common: move PTP KVM support from ark to common
The PTP_1588_CLOCK_KVM support is now avaialble to arm,
it was already built everywhere for ARK so let's move
it to common to do so for Fedora too.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:09 -04:00
Justin M. Forbes ffd43d68b6 Enable CONFIG_DRM_AMDGPU_USERPTR for everyone
In the 5.12 kernel cycle, CONFIG_HSA_AMD was changed to select
DRM_AMDGPU_USERPTR. This creates a config mismatch for ppc64le as
HSA_AMD was enabled there, but DRM_AMDGPU_USERPTR was not. This change
enables DRM_AMDGPU_USERPTR for everything, it is dependent on
DRM_AMDGPU, so this will not change the current s390X configs.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:09 -04:00
Herton R. Krzesinski 490cf97153 redhat: add initial rpminspect configuration
CI has been doing rpminspect runs against built rpm packages.

We have to add specific configuration for rpminspect, that can vary
depending on the kernel branch. For example, older releases didn't
have the kernel meta-package, but today kernel have it and requires
kernel-core/kernel-modules which are the ones which contains files.
This configuration is supposed as a tweak only for the cases where
it makes sense having it here, to ship with dist-git, instead of
changing rpminspect-data-* packages.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:31:08 -04:00
Fedora Kernel Team 82788a7bfc [redhat] New configs in net/netfilter
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NETFILTER_XTABLES_COMPAT:

 This option provides a translation layer to run 32bit arp,ip(6),ebtables
 binaries on 64bit kernels.

 If unsure, say N.

 Symbol: NETFILTER_XTABLES_COMPAT [=y]
 Type  : bool
 Defined at net/netfilter/Kconfig:731
   Prompt: Netfilter Xtables 32bit support
   Depends on: NET [=y] && INET [=y] && NETFILTER [=y] && NETFILTER_XTABLES [=y] && COMPAT [=y]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> Network packet filtering framework (Netfilter) (NETFILTER [=y])
           -> Core Netfilter Configuration
             -> Netfilter Xtables support (required for ip_tables) (NETFILTER_XTABLES [=y])

---

 CONFIG_NF_LOG_SYSLOG:

 This option enable support for packet logging via syslog.
 It supports IPv4, IPV6, ARP and common transport protocols such
 as TCP and UDP.
 This is a simpler but less flexible logging method compared to
 CONFIG_NETFILTER_NETLINK_LOG.
 If both are enabled the backend to use can be configured at run-time
 by means of per-address-family sysctl tunables.

 Symbol: NF_LOG_SYSLOG [=m]
 Type  : tristate
 Defined at net/netfilter/Kconfig:74
   Prompt: Syslog packet logging
   Depends on: NET [=y] && INET [=y] && NETFILTER [=y]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> Network packet filtering framework (Netfilter) (NETFILTER [=y])
           -> Core Netfilter Configuration
 Selected by [m]:
   - NETFILTER_XT_TARGET_LOG [=m] && NET [=y] && INET [=y] && NETFILTER [=y] && NETFILTER_XTABLES [=y]
   - NF_LOG_ARP [=m] && NET [=y] && INET [=y] && NETFILTER [=y]
   - NF_LOG_IPV4 [=m] && NET [=y] && INET [=y] && NETFILTER [=y]
   - NF_LOG_IPV6 [=m] && NET [=y] && INET [=y] && IPV6 [=y] && NETFILTER [=y]

---

Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:08 -04:00
Fedora Kernel Team ff085ec8ac [redhat] New configs in net/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PCPU_DEV_REFCNT:

 network device refcount are using per cpu variables if this option is set.
 This can be forced to N to detect underflows (with a performance drop).

 Symbol: PCPU_DEV_REFCNT [=y]
 Type  : bool
 Defined at net/Kconfig:248
   Prompt: Use percpu variables to maintain network device refcount
   Depends on: NET [=y] && SMP [=y]
   Location:
     -> Networking support (NET [=y])
       -> Networking options

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:08 -04:00
Fedora Kernel Team 9c22bcc474 [redhat] New configs in drivers/i2c
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_I2C_CP2615:

 If you say yes to this option, support will be included for Silicon
 Labs CP2615's I2C interface.

 This driver can also be built as a module.  If so, the module
 will be called i2c-cp2615.

 Symbol: I2C_CP2615 [=n]
 Type  : tristate
 Defined at drivers/i2c/busses/Kconfig:1212
   Prompt: Silicon Labs CP2615 USB sound card and I2C adapter
   Depends on: I2C [=y] && HAS_IOMEM [=y] && USB [=y]
   Location:
     -> Device Drivers
       -> I2C support
         -> I2C support (I2C [=y])
           -> I2C Hardware Bus support

---

 CONFIG_I2C_HISI:

 Say Y here if you want to have Hisilicon I2C controller support
 available on the Kunpeng Server.

 This driver can also be built as a module. If so, the module
 will be called i2c-hisi.

 Symbol: I2C_HISI [=n]
 Type  : tristate
 Defined at drivers/i2c/busses/Kconfig:648
   Prompt: HiSilicon I2C controller
   Depends on: I2C [=y] && HAS_IOMEM [=y] && (ARM64 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> I2C support
         -> I2C support (I2C [=y])
           -> I2C Hardware Bus support

---

Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:08 -04:00
Fedora Kernel Team 0762a7cee4 [redhat] New configs in drivers/thermal
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INTEL_TCC_COOLING:

 Enable this to support system cooling by adjusting the effective TCC
 activation temperature via the TCC Offset register, which is widely
 supported on modern Intel platforms.
 Note that, on different platforms, the behavior might be different
 on how fast the setting takes effect, and how much the CPU frequency
 is reduced.

 Symbol: INTEL_TCC_COOLING [=n]
 Type  : tristate
 Defined at drivers/thermal/intel/Kconfig:83
   Prompt: Intel TCC offset cooling Driver
   Depends on: THERMAL [=y] && (X86 [=y] || X86_INTEL_QUARK [=n] || COMPILE_TEST [=n]) && X86 [=y]
   Location:
     -> Device Drivers
       -> Thermal drivers (THERMAL [=y])
         -> Intel thermal drivers

---

Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:08 -04:00
Fedora Kernel Team 804d7683d7 [redhat] New configs in net/bluetooth
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BT_AOSPEXT:

 This options enables support for the Android Open Source
 Project defined HCI vendor extensions.

 Symbol: BT_AOSPEXT [=n]
 Type  : bool
 Defined at net/bluetooth/Kconfig:102
   Prompt: Enable Android Open Source Project extensions
   Depends on: NET [=y] && BT [=m]
   Location:
     -> Networking support (NET [=y])
       -> Bluetooth subsystem support (BT [=m])

---

Cc: Gopal Tiwari <gtiwari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:08 -04:00
Fedora Kernel Team 85cd9a5dd1 [redhat] New configs in drivers/bluetooth
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BT_VIRTIO:

 Virtio Bluetooth support driver.
 This driver supports Virtio Bluetooth devices.

 Say Y here to compile support for HCI over Virtio into the
 kernel or say M to compile as a module.

 Symbol: BT_VIRTIO [=n]
 Type  : tristate
 Defined at drivers/bluetooth/Kconfig:428
   Prompt: Virtio Bluetooth driver
   Depends on: NET [=y] && BT [=m] && VIRTIO [=y]
   Location:
     -> Networking support (NET [=y])
       -> Bluetooth subsystem support (BT [=m])
         -> Bluetooth device drivers

---

Cc: Gopal Tiwari <gtiwari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:07 -04:00
Peter Robinson 3fe2da5963 fedora: arm updates for 5.13
Initial updates for the 5.13 window

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:07 -04:00
Peter Robinson cb441e671a fedora: Enable WWAN and associated MHI bits
The Modem Host Interface (MHI) is used for most newer 4G/LTE and 5G
modems. It's basically virtual ethernet over a PCI <-> PCIE-endpoint
with a control over a TTY interface. These modems are already in the
latest Lenovo laptops and likely others.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:31:07 -04:00
Justin Forbes 3feb90ca54 Update CONFIG_MODPROBE_PATH to /usr/sbin
Technically both paths exist, but /sbin is a link to /usr/sbin
2021-08-30 14:31:07 -04:00
Fedora Kernel Team fcec24a5b3 [redhat] New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MODPROBE_PATH:

 When kernel code requests a module, it does so by calling
 the "modprobe" userspace utility. This option allows you to
 set the path where that binary is found. This can be changed
 at runtime via the sysctl file
 /proc/sys/kernel/modprobe. Setting this to the empty string
 removes the kernel's ability to request modules (but
 userspace can still load modules explicitly).

 Symbol: MODPROBE_PATH [=/sbin/modprobe]
 Type  : string
 Defined at init/Kconfig:2302
   Prompt: Path to modprobe binary
   Depends on: MODULES [=y]
   Location:
     -> Enable loadable module support (MODULES [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:07 -04:00
Justin M. Forbes dc19dc42b8 Fedora set modprobe path
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:07 -04:00
Fedora Kernel Team 99640bf481 [redhat] New configs in drivers/input
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INPUT_IQS626A:

 Say Y to enable support for the Azoteq IQS626A capacitive
 touch controller.

 To compile this driver as a module, choose M here: the
 module will be called iqs626a.

 Symbol: INPUT_IQS626A [=n]
 Type  : tristate
 Defined at drivers/input/misc/Kconfig:766
   Prompt: Azoteq IQS626A capacitive touch controller
   Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Miscellaneous devices (INPUT_MISC [=y])
 Selects: REGMAP_I2C [=m]

---

 CONFIG_TOUCHSCREEN_HYCON_HY46XX:

 Say Y here if you have a touchscreen using Hycon hy46xx

 If unsure, say N.

 To compile this driver as a module, choose M here: the
 module will be called hycon-hy46xx.

 Symbol: TOUCHSCREEN_HYCON_HY46XX [=n]
 Type  : tristate
 Defined at drivers/input/touchscreen/Kconfig:414
   Prompt: Hycon hy46xx touchscreen support
   Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Touchscreens (INPUT_TOUCHSCREEN [=y])

---

 CONFIG_TOUCHSCREEN_ILITEK:

 Say Y here if you have touchscreen with ILITEK touch IC,
 it supports 213X/23XX/25XX and other Lego series.

 If unsure, say N.

 To compile this driver as a module, choose M here: the
 module will be called ilitek_ts_i2c.

 Symbol: TOUCHSCREEN_ILITEK [=n]
 Type  : tristate
 Defined at drivers/input/touchscreen/Kconfig:440
   Prompt: Ilitek I2C 213X/23XX/25XX/Lego Series Touch ICs
   Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Touchscreens (INPUT_TOUCHSCREEN [=y])

---

 CONFIG_TOUCHSCREEN_MSG2638:

 Say Y here if you have an I2C touchscreen using MStar msg2638.

 If unsure, say N.

 To compile this driver as a module, choose M here: the
 module will be called msg2638.

 Symbol: TOUCHSCREEN_MSG2638 [=n]
 Type  : tristate
 Defined at drivers/input/touchscreen/Kconfig:616
   Prompt: MStar msg2638 touchscreen support
   Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Touchscreens (INPUT_TOUCHSCREEN [=y])

---

Cc: Tony Camuso <tcamuso@redhat.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:07 -04:00
Fedora Kernel Team 6acc0a1f78 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:06 -04:00
Fedora Kernel Team e90668af9f [redhat] AUTOMATIC: New configs 2021-08-30 14:31:06 -04:00
Don Zickus 37c899a0cf Keep sctp and l2tp modules in modules-extra
There are two modules: sctp_diag and l2tp_ip6 that are in kernel-modules
that accidentally dragged the rest of the sctp and l2tp mdoules in
there.  Instead all those modules should stay in modules-extra.

Move the offending modules into modules-extra.

Cc: mleitner@redhat.com
Cc: lxin@redhat.com
Cc: jbenc@redhat.com
Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:31:06 -04:00
Don Zickus 53019213c4 Fix ppc64le cross build packaging
CKI has been failing to cross build a ppc64le rpm for a while now. The
reason why is the ppc64le-gnu-strip command could not recognize the
scripts/dtc/libfdt/fdt_strerror.o file because it was an x86_64 file
type.  That is a result of the cross env.

What should have happened is, none of the *.o files in the script
directory should be there and thus the strip command would have nothing
to strip.

Having x86_64 files lying around to be packaged in kernel-devel is
another problem.  But for this build problem, just remove all the *.o
files in the script/ area.

The spec file tries to do this, but fails to remove *.o's at another
directory layer (libfdt).  Let's just replace the 'rm' commands with a
'find and rm' command instead.

Tested in a CKI container.  After this change, the rpm builds.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:31:06 -04:00
Hans de Goede 37e162b406 Fedora: Make amd_pinctrl module builtin
The GPIOs provided by the AMD pinctrl module may be used by various
ACPI methods (e.g. _PS0, _PS3) and resources (GpioInt). These ACPI
uses may happen before the module has a chance to load when amd_pinctrl
is build as a module.

Change the CONFIG_PINCTRL_AMD option to y, so that the amd_pinctrl
code gets built into the kernel to fix this. This specifically fixes
I2C-HID touchpads on AMD based laptops sometimes not working at boot.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1634832
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1957203
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 14:31:06 -04:00
Fedora Kernel Team f19c8e17fd [redhat] AUTOMATIC: New configs 2021-08-30 14:31:06 -04:00
Fedora Kernel Team b67813fa95 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:06 -04:00
CKI Gitlab cef4d7d636 [redhat] New configs in drivers/cxl 2021-08-30 14:31:06 -04:00
Fedora Kernel Team 9141bd5bbe [redhat] New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_ATC260X_I2C:

 Support for the Actions Semi ATC260x PMICs controlled via I2C.

 This driver provides common support for accessing the ATC2603C
 and ATC2609A chip variants, additional drivers must be enabled
 in order to use the functionality of the device.

 Symbol: MFD_ATC260X_I2C [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:2064
   Prompt: Actions Semi ATC260x PMICs with I2C
   Depends on: HAS_IOMEM [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_ATC260X [=n] && REGMAP_I2C [=m]

---

 CONFIG_MFD_NTXEC:

 Say yes here if you want to support the embedded controller found in
 certain e-book readers designed by the original design manufacturer
 Netronix.

 Symbol: MFD_NTXEC [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:970
   Prompt: Netronix embedded controller (EC)
   Depends on: HAS_IOMEM [=y] && (OF [=y] || COMPILE_TEST [=n]) && I2C [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: REGMAP_I2C [=m] && MFD_CORE [=m]

---

 CONFIG_MFD_ROHM_BD957XMUF:

 Select this option to get support for the ROHM BD9576MUF and
 BD9573MUF Power Management ICs. BD9576 and BD9573 are primarily
 designed to be used to power R-Car series processors.

 Symbol: MFD_ROHM_BD957XMUF [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:1981
   Prompt: ROHM BD9576MUF and BD9573MUF Power Management ICs
   Depends on: HAS_IOMEM [=y] && I2C [=y]=y && OF [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: REGMAP_I2C [=m] && MFD_CORE [=m]

---

Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:06 -04:00
Fedora Kernel Team e458ef8e8c [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_RT4505:

 This option enables support for the RT4505 flash LED controller.
 RT4505 includes torch and flash functions with programmable current.
 And it's commonly used to compensate the illuminance for the camera
 inside the mobile product like as phones or tablets.

 Symbol: LEDS_RT4505 [=n]
 Type  : tristate
 Defined at drivers/leds/flash/Kconfig:5
   Prompt: LED support for RT4505 flashlight controller
   Depends on: NEW_LEDS [=y] && LEDS_CLASS_FLASH [=m] && I2C [=y] && OF [=y] && (V4L2_FLASH_LED_CLASS [=n] || !V4L2_FLASH_LED_CLASS [=n])
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])
 Selects: REGMAP_I2C [=m]

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:05 -04:00
Justin M. Forbes 7380bff7b1 Keep CONFIG_KASAN_HW_TAGS off for aarch64 debug configs
Some time ago this config option came in, and the scripts missed it. I
added the file to pending turning it off, but that doesn't get it
reviewed.  This MR would move the config from pending to common, but it
does keep CONFIG_KASAN_HW_TAGS off.  Let me know if you would rather
turn it on.

Cc: Prarit Bhargava <prarit@redhat.com>

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:05 -04:00
Fedora Kernel Team 6639a60c99 New configs in drivers/bus
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VEXPRESS_CONFIG:

 Platform configuration infrastructure for the ARM Ltd.
 Versatile Express.

 Symbol: VEXPRESS_CONFIG [=y]
 Type  : tristate
 Defined at drivers/bus/Kconfig:224
   Prompt: Versatile Express configuration bus
   Depends on: (ARM || ARM64 [=y]) && OF [=y]
   Location:
     -> Device Drivers
       -> Bus devices
 Selects: REGMAP [=y]

Cc: Myron Stowe <myron.stowe@redhat.com>
2021-08-30 14:31:05 -04:00
David Gibson dcfd285453 RHEL: Don't build KVM PR module on ppc64
We're removing support for KVM on POWER in RHEL9.  However, we're leaving
the KVM module enabled to allow for certain internal test scenarious.  This
will also make life easier for possible IBM and/or community supported
efforts.

However, we only want to enable the KVM HV implementation, not the KVM PR
implementation.  The latter is very slow, quite buggy on POWER9 and later
CPUs and generally just causes confusion.  It's been disabled for a long
time in RHEL8 already (by 4e54d8b3cd8 "[redhat]powerpc64: disable kvm-pr").

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1930649
Upstream Status: RHEL only

Signed-off-by: David Gibson <dgibson@redhat.com>
2021-08-30 14:31:05 -04:00
Michael Petlan ceb20716e6 [redhat] spec: Add bzip2 dependency to perf package
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1957219
RHEL-only

description
===========
Adding explicit bzip2 dependency for perf tool. The bzip2
is used in perf archive script command, and without bzip2
command it fails, like:

  $ perf archive
  tar (child): bzip2: Cannot exec: No such file or directory
  tar (child): Error is not recoverable: exiting now

With explicit bzip2 dependency we're ok:
  $ rpm -qp --requires perf-...rpm  | grep bzip2
  bzip2

Signed-off-by: Michael Petlan <mpetlan@redhat.com>
2021-08-30 14:31:05 -04:00
Fedora Kernel Team a835ddbdf7 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:05 -04:00
Fedora Kernel Team 945722e59b [redhat] AUTOMATIC: New configs 2021-08-30 14:31:05 -04:00
Justin M. Forbes 9c0c4c6103 Flip CONFIG_USB_ROLE_SWITCH from m to y
As CONFIG_TYPEC_UCSI and CONFIG_UCSI_ACPI now depend on
CONFIG_USB_ROLE_SWITCH, we end up with a config mismatch.  We can either
change USB_ROLE_SWITCH to inline as I have done here, or change
TYPEC_UCSI and UCSI_ACPI to modules.  I chose flipping USB_ROLE_SWITCH
inline as it seems the safer solution.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:04 -04:00
Justin M. Forbes c31a3f6fac Set valid options for CONFIG_FW_LOADER_USER_HELPER
While FW_LOADER_USER_HELPER is largerly deprecated, there are 2 drivers
which still require it, CONFIG_LEDS_LP55XX_COMMON is turned off, but
CONFIG_DELL_RBU is enabled for x86_64.  This turns off
FW_LOADER_USER_HELPER for everything except for x86_64 to support the
DELL_RBU driver.  As the DELL_RBU driver does a select on
FW_LOADER_USER_HELPER, the options were turning it on, or turning off
the DELL_RBU driver.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:04 -04:00
Justin M. Forbes 9e6d3306dc Clean up CONFIG_FB_MODE_HELPERS
Some time ago, a config mismatch required turning on
CONFIG_FB_MODE_HELPERS for ppc. As I went through to create a proper MR
to get that reviewed, I found that our existing configs were a mess on
this one. This cleans everything up. As only a few drivers rely on this
feature, and they select it, this should be correct.  For RHEL configs,
it is only ppc64le that leaves it enabled.

Cc:      David Airlie <airlied@redhat.com>
Cc:      Adam Jackson <ajax@redhat.com>
Cc:      Lyude Paul <lyude@redhat.com>

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:04 -04:00
Fedora Kernel Team 7a9e1b147a [redhat] New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CGROUP_MISC:

 Provides a controller for miscellaneous resources on a host.

 Miscellaneous scalar resources are the resources on the host system
 which cannot be abstracted like the other cgroups. This controller
 tracks and limits the miscellaneous resources used by a process
 attached to a cgroup hierarchy.

 For more information, please check misc cgroup section in
 /Documentation/admin-guide/cgroup-v2.rst.

 Symbol: CGROUP_MISC [=n]
 Type  : bool
 Defined at init/Kconfig:1113
   Prompt: Misc resource controller
   Depends on: CGROUPS [=y]
   Location:
     -> General setup
       -> Control Group support (CGROUPS [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_CGROUP_MISC: enable it.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:04 -04:00
Justin M. Forbes bc03a94d07 Turn off CONFIG_VFIO for the s390x zfcpdump kernel
CONFIG_VFIO now selects IOMMU_API instead of depending on it, causing
several config mismatches for the zfcpdump kernel. Best to just turn it
off in this instance.

Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>
Cc: rhvirt-patches@redhat.com

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:04 -04:00
Justin M. Forbes f39536e709 Delete unused CONFIG_SND_SOC_MAX98390 pending-common
This file was added due to a config mismatch 9 months ago.  That
mismatch no longer exists with the current ARK configs, so I am deleting
the file.  If it becomes valid again, the scripts will create a new one
and send it through the regular config process.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:04 -04:00
Justin M. Forbes b3696c8141 Update pending-common configs, preparing to set correctly
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:03 -04:00
Justin M. Forbes a54477772b Update fedora filters for surface
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:03 -04:00
Justin M. Forbes 183c5459da Build CONFIG_CRYPTO_ECDSA inline for s390x zfcpdump
MR 1049 enabled CONFIG_CRYPTO_ECDSA and made it modular for everyone. As
the s390x zfcpdump kernels do not support modules, this needs to be
brought inline (or turned off all together) for that kernel.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:03 -04:00
Fedora Kernel Team 0c21a10c6b [redhat] New configs in drivers/net/dsa
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NET_DSA_MV88E6XXX_PTP:

 Say Y to enable PTP hardware timestamping on Marvell 88E6xxx switch
 chips that support it.

 Symbol: NET_DSA_MV88E6XXX_PTP [=n]
 Type  : bool
 Defined at drivers/net/dsa/mv88e6xxx/Kconfig:12
   Prompt: PTP support for Marvell 88E6xxx
   Depends on: NETDEVICES [=y] && HAVE_NET_DSA [=y] && PTP_1588_CLOCK [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Distributed Switch Architecture drivers

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:03 -04:00
Fedora Kernel Team 942583a492 [redhat] AUTOMATIC: New configs 2021-08-30 14:31:03 -04:00
Fedora Kernel Team fc54b65c9d [redhat] AUTOMATIC: New configs 2021-08-30 14:31:03 -04:00
David Ward 885d9ecc88 Replace "flavour" where "variant" is meant instead
In the SPEC file, "flavour" is used when referring to the kernel "variant"
instead (such as debug, lpae, or zfcpdump). In the Fedora/ARK documentation
and scripts, "flavor" refers to a configuration directory (fedora or ark)
underneath redhat/configs/ in the os-build branch.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:03 -04:00
David Ward 9d1506a5d3 Drop the %{variant} macro and fix --with-vanilla
The %{upstream_branch} macro and others were dropped from the SPEC file (in
Fedora kernel dist-git commit cff59d310104) seven years ago. It left behind
the %{variant} macro, which is only used for --with-vanilla.

The --with-vanilla option does not work with the current SPEC file, because
defining %{variant} causes errors: it results in dependencies with invalid
NVRs (where the package release contains a dash). Defining %{vanilla} would
also cause the source RPM to be built using a different name, although it
would have exactly the same contents as the "kernel" source RPM.

Even the name %{variant} is misleading. In Fedora/RHEL, kernel "variants"
are built with different options than the generic kernel configuration, and
are provided in subpackages. The %{variant} macro was meant to be used when
the kernel is built from different sources instead. (The sources in vanilla
builds do not have any downstream patches applied.)

Instead of using %{variant}, rely on package builders to define %{buildid}
when they change the package sources, whether it is by using --with-vanilla
or by introducing additional patches. This allows %{variant} to be dropped.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:03 -04:00
David Ward 1c371269d7 Fix syntax of %kernel_variant_files
The syntax used/shown here differs from what is implemented.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:03 -04:00
David Ward 2d983eed0e Change description of --without-vdso-install to fix typo
Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:31:02 -04:00
Fedora Kernel Team 0ad55fba0a [redhat] New configs in drivers/net/ethernet/mellanox
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MLX5_TC_SAMPLE:

 Say Y here if you want to support offloading sample rules via tc
 sample action.
 If set to N, will not be able to configure tc rules with sample
 action.

 If unsure, set to Y

 Symbol: MLX5_TC_SAMPLE [=y]
 Type  : bool
 Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:107
   Prompt: MLX5 TC sample offload support
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CLS_ACT [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
           -> Mellanox devices (NET_VENDOR_MELLANOX [=y])
             -> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y])
               -> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y])
                 -> MLX5 TC classifier action support (MLX5_CLS_ACT [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:02 -04:00
Justin M. Forbes 1eeeb52f39 Config updates to work around mismatches
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:02 -04:00
Justin M. Forbes 4655fa6dd7 CONFIG_SND_SOC_FSL_ASOC_CARD selects CONFIG_MFD_WM8994 now
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:02 -04:00
Hangbin Liu 840b99a9d9 wireguard: disable in FIPS mode
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1940794
Upstream: RHEL Only

The cryptos(BLAKE2S, Curve25519, CHACHA20POLY1305) in WireGuard are not
FIPS approved. Disable loading the cryptos is a better solution, but the
cryptos called by WireGuard are in lib/crypto/ instead of crypto/, which
is a little complex to disable. While disabling the WireGuard module is
more clear and easier.

So let's disable the WireGuard in FIPS mode first. When the issue that
loading the lib/crypto/ code in FIPS mode is fixed. We can revert this
internal patch.

Signed-off-by: Hangbin Liu <haliu@redhat.com>
2021-08-30 14:31:02 -04:00
Fedora Kernel Team b8ffdfa6cb [redhat] New configs in fs/nfs
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NFS_V4_2_READ_PLUS:

 This is intended for developers only. The READ_PLUS operation has
 been shown to have issues under specific conditions and should not
 be used in production.

 Symbol: NFS_V4_2_READ_PLUS [=n]
 Type  : bool
 Defined at fs/nfs/Kconfig:209
   Prompt: NFS: Enable support for the NFSv4.2 READ_PLUS operation
   Depends on: NETWORK_FILESYSTEMS [=y] && NFS_V4_2 [=y]
   Location:
     -> File systems
       -> Network File Systems (NETWORK_FILESYSTEMS [=y])

---

Cc: kernel-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:02 -04:00
Justin M. Forbes 0aa3e2f884 Enable mtdram for fedora (rhbz 1955916)
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:02 -04:00
Fedora Kernel Team 3a8b89d18b [redhat] New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MODULE_COMPRESS_GZIP:

 Compress modules with GZIP. The installed modules are suffixed
 with .ko.gz.

 Symbol: MODULE_COMPRESS_GZIP [=n]
 Type  : bool
 Defined at init/Kconfig:2264
   Prompt: GZIP
   Depends on: <choice>
   Location:
     -> Enable loadable module support (MODULES [=y])
       -> Module compression mode (<choice> [=y])

---

 CONFIG_MODULE_COMPRESS_NONE:

 Do not compress modules. The installed modules are suffixed
 with .ko.

 Symbol: MODULE_COMPRESS_NONE [=y]
 Type  : bool
 Defined at init/Kconfig:2258
   Prompt: None
   Depends on: <choice>
   Location:
     -> Enable loadable module support (MODULES [=y])
       -> Module compression mode (<choice> [=y])

---

 CONFIG_MODULE_COMPRESS_XZ:

 Compress modules with XZ. The installed modules are suffixed
 with .ko.xz.

 Symbol: MODULE_COMPRESS_XZ [=n]
 Type  : bool
 Defined at init/Kconfig:2270
   Prompt: XZ
   Depends on: <choice>
   Location:
     -> Enable loadable module support (MODULES [=y])
       -> Module compression mode (<choice> [=y])

---

 CONFIG_MODULE_COMPRESS_ZSTD:

 Compress modules with ZSTD. The installed modules are suffixed
 with .ko.zst.

 Symbol: MODULE_COMPRESS_ZSTD [=n]
 Type  : bool
 Defined at init/Kconfig:2276
   Prompt: ZSTD
   Depends on: <choice>
   Location:
     -> Enable loadable module support (MODULES [=y])
       -> Module compression mode (<choice> [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:02 -04:00
Fedora Kernel Team a8182991f6 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TEST_DIV64:

 Enable this to turn on 'do_div()' function test. This test is
 executed only once during system boot (so affects only boot time),
 or at module load time.

 If unsure, say N.

 Symbol: TEST_DIV64 [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:2078
   Prompt: 64bit/32bit division and modulo test
   Depends on: RUNTIME_TESTING_MENU [=y] && (DEBUG_KERNEL [=y] || m && MODULES [=y])
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Runtime Testing (RUNTIME_TESTING_MENU [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:01 -04:00
Vladis Dronov 9ea3d22a21 [redhat] Enable CONFIG_CRYPTO_CFB=y so cfb(aes) is available in FIPS mode
Currently the CFB algo is built as a module in Fedora and is not build in
ARK. This results in a panic while booting in a FIPS mode:

[    3.347092] alg: skcipher: failed to allocate transform for cfb(aes): -2
[    3.347918] Kernel panic - not syncing: alg: self-tests for cfb(aes) (cfb(aes)) failed in fips mode!

Fix this by embedding the CFB code into a kernel, the same way as CTS and
CBC algos already do. The reason why the CFB code is embedded and is not
built as a module is that dracut must add the module to an initramfs image.
This is not always the case.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1915290
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:31:01 -04:00
Fedora Kernel Team a70888981e [redhat] New configs in arch/s390
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CIO_INJECT:

 This option provides a debugging facility to inject certain artificial events
 and instruction responses to the CIO layer of Linux kernel. The newly created
 debugfs user-interfaces will be at /sys/kernel/debug/s390/cio/*

 Symbol: CIO_INJECT [=n]
 Type  : bool
 Defined at arch/s390/Kconfig.debug:19
   Prompt: CIO Inject interfaces
   Depends on: DEBUG_KERNEL [=y] && DEBUG_FS [=y]
   Location:
     -> Kernel hacking
       -> s390 Debugging

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_CIO_INJECT: s390 only

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:01 -04:00
Fedora Kernel Team 512635bea5 [redhat] New configs in security/landlock
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SECURITY_LANDLOCK:

 Landlock is a sandboxing mechanism that enables processes to restrict
 themselves (and their future children) by gradually enforcing
 tailored access control policies.  A Landlock security policy is a
 set of access rights (e.g. open a file in read-only, make a
 directory, etc.) tied to a file hierarchy.  Such policy can be
 configured and enforced by any processes for themselves using the
 dedicated system calls: landlock_create_ruleset(),
 landlock_add_rule(), and landlock_restrict_self().

 See Documentation/userspace-api/landlock.rst for further information.

 If you are unsure how to answer this question, answer N.  Otherwise,
 you should also prepend "landlock," to the content of CONFIG_LSM to
 enable Landlock at boot time.

 Symbol: SECURITY_LANDLOCK [=n]
 Type  : bool
 Defined at security/landlock/Kconfig:3
   Prompt: Landlock support
   Depends on: SECURITY [=y] && !ARCH_EPHEMERAL_INODES [=n]
   Location:
     -> Security options
 Selects: SECURITY_PATH [=n]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:01 -04:00
Fedora Kernel Team afcce0d387 [redhat] New configs in sound/virtio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_VIRTIO:

 This is the virtual sound driver for virtio. Say Y or M.

 Symbol: SND_VIRTIO [=n]
 Type  : tristate
 Defined at sound/virtio/Kconfig:4
   Prompt: Virtio sound driver
   Depends on: SOUND [=m] && !UML && SND [=m] && VIRTIO [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
 Selects: SND_PCM [=m] && SND_JACK [=y]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_SND_VIRTIO enable as a module.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:01 -04:00
Fedora Kernel Team 8f770f70b9 [redhat] New configs in crypto/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CRYPTO_ECDSA:

 Elliptic Curve Digital Signature Algorithm (NIST P192, P256 etc.)
 is A NIST cryptographic standard algorithm. Only signature verification
 is implemented.

 Symbol: CRYPTO_ECDSA [=n]
 Type  : tristate
 Defined at crypto/Kconfig:245
   Prompt: ECDSA (NIST P192, P256 etc.) algorithm
   Depends on: CRYPTO [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
 Selects: CRYPTO_ECC [=m] && CRYPTO_AKCIPHER [=y] && ASN1 [=y]

---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
 - CONFIG_CRYPTO_ECDSA enable as a module.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:31:01 -04:00
Justin M. Forbes fef5b59731 Remove reference to bpf-helpers man page
Upstream commit a01d935b2e removed the
bpf-helpers man page from bpftool docs. Trying to rm the built man page
will fail the kernel build because it isn't there.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:31:00 -04:00
Fedora Kernel Team d44f713ca6 [redhat] New configs in arch/x86
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KVM_XEN:

 Provides KVM support for the hosting Xen HVM guests and
 passing Xen hypercalls to userspace.

 If in doubt, say "N".

 Symbol: KVM_XEN [=n]
 Type  : bool
 Defined at arch/x86/kvm/Kconfig:106
   Prompt: Support for Xen hypercall interface
   Depends on: VIRTUALIZATION [=y] && KVM [=m]
   Location:
     -> Virtualization (VIRTUALIZATION [=y])
       -> Kernel-based Virtual Machine (KVM) support (KVM [=m])

---

Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:00 -04:00
Fedora Kernel Team 66373a1b62 [redhat] New configs in drivers/hid
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HID_FT260:

 Provides I2C host adapter functionality over USB-HID through FT260
 device. The customizable USB descriptor fields are exposed as sysfs
 attributes.

 To compile this driver as a module, choose M here: the module
 will be called hid-ft260.

 Symbol: HID_FT260 [=n]
 Type  : tristate
 Defined at drivers/hid/Kconfig:354
   Prompt: FTDI FT260 USB HID to I2C host support
   Depends on: INPUT [=y] && HID [=y] && USB_HID [=y] && HIDRAW [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> HID bus support (HID [=y])
           -> Special HID drivers

---

Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:00 -04:00
Fedora Kernel Team 9badc5adcf [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_BPA_RS600:

 If you say yes here you get hardware monitoring support for BluTek
 BPA-RS600 Power Supplies.

 This driver can also be built as a module. If so, the module will
 be called bpa-rs600.

 Symbol: SENSORS_BPA_RS600 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:59
   Prompt: BluTek BPA-RS600 Power Supplies
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_FSP_3Y:

 If you say yes here you get hardware monitoring support for
 FSP/3Y-Power hot-swap power supplies.
 Supported models: YH-5151E, YM-2151E

 This driver can also be built as a module. If so, the module will
 be called fsp-3y.

 Symbol: SENSORS_FSP_3Y [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:68
   Prompt: FSP/3Y-Power power supplies
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_IR36021:

 If you say yes here you get hardware monitoring support for Infineon
 IR36021.

 This driver can also be built as a module. If so, the module will
 be called ir36021.

 Symbol: SENSORS_IR36021 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:106
   Prompt: Infineon IR36021
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_MAX15301:

 If you say yes here you get hardware monitoring support for Maxim
 MAX15301, as well as for Flex BMR461.

 This driver can also be built as a module. If so, the module will
 be called max15301.

 Symbol: SENSORS_MAX15301 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:179
   Prompt: Maxim MAX15301
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_NZXT_KRAKEN2:

 If you say yes here you get support for hardware monitoring for the
 NZXT Kraken X42/X52/X62/X72 all-in-one CPU liquid coolers.

 This driver can also be built as a module. If so, the module
 will be called nzxt-kraken2.

 Symbol: SENSORS_NZXT_KRAKEN2 [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:1485
   Prompt: NZXT Kraken X42/X51/X62/X72 liquid coolers
   Depends on: HWMON [=y] && USB_HID [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

 CONFIG_SENSORS_STPDDC60:

 If you say yes here you get hardware monitoring support for ST
 STPDDC60 Universal Digital Multicell Controller, as well as for
 Flex BMR481.

 This driver can also be built as a module. If so, the module will
 be called stpddc60.

 Symbol: SENSORS_STPDDC60 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:287
   Prompt: ST STPDDC60
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:31:00 -04:00
CKI Gitlab 0dfbb00b15 [redhat] New configs in arch/x86 2021-08-30 14:31:00 -04:00
Prarit Bhargava 1246b803d5 RHMAINTAINERS: Update for Apr 30 2021
Update RHMAINTAINERS.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:31:00 -04:00
Dave Olsthoorn 7deb4c52d4 Fedora: enable more modules for surface devices
This enables new kernel modules for 5.13 which are for Microsofts Surface
line of devices.

Signed-off-by: Dave Olsthoorn <dave@bewaar.me>
2021-08-30 14:31:00 -04:00
Fedora Kernel Team 8f5a7508ce [redhat] AUTOMATIC: New configs 2021-08-30 14:30:59 -04:00
Fedora Kernel Team 4a97266e8e [redhat] AUTOMATIC: New configs 2021-08-30 14:30:59 -04:00
Fedora Kernel Team 07e0010b5f [redhat] AUTOMATIC: New configs 2021-08-30 14:30:59 -04:00
Fedora Kernel Team 4bb2df4d60 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:59 -04:00
Justin M. Forbes b5338c7a2a Fix Fedora config mismatch for CONFIG_FSL_ENETC_IERB
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:59 -04:00
Fedora Kernel Team 96d315fa80 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:59 -04:00
Fedora Kernel Team c32b0b8f53 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:59 -04:00
Justin M. Forbes 4de50332d2 hardlink is in /usr/bin/ now
In 2019, hardlink was brought into util-linux upstream with v2.34. As
part of the util-linux package, it is now in /usr/bin instead of
/usr/sbin.  No one noticed because we just skipped the hardlink and took
up a bit of extra space.  Let's point to the correct location now.

Fixes rhbz 1889043

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:59 -04:00
Justin M. Forbes 38123ad5e9 Ensure CONFIG_KVM_BOOK3S_64_PR stays on in Fedora, even if it is turned off in RHEL
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:59 -04:00
Fedora Kernel Team 4a7466e15c [redhat] New configs in drivers/spi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SPI_ALTERA_CORE:

 "The core code for the Altera SPI Controller"

 Symbol: SPI_ALTERA_CORE [=n]
 Type  : tristate
 Defined at drivers/spi/Kconfig:67
   Prompt: Altera SPI Controller core code
   Depends on: SPI [=y] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> SPI support (SPI [=y])
 Selects: REGMAP [=y]
 Selected by [n]:
   - SPI_ALTERA [=n] && SPI [=y] && SPI_MASTER [=y]
   - SPI_ALTERA_DFL [=n] && SPI [=y] && SPI_MASTER [=y] && FPGA_DFL [=n]

---

 CONFIG_SPI_HISI_KUNPENG:

 This enables support for HiSilicon SPI controller found on
 Kunpeng SoCs.

 This driver can also be built as a module. If so, the module
 will be called hisi-kunpeng-spi.

 Symbol: SPI_HISI_KUNPENG [=n]
 Type  : tristate
 Defined at drivers/spi/Kconfig:351
   Prompt: HiSilicon SPI Controller for Kunpeng SoCs
   Depends on: SPI [=y] && SPI_MASTER [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> SPI support (SPI [=y])

---

Cc: Al Stone <ahs3@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:58 -04:00
Fedora Kernel Team f967425c59 [redhat] New configs in arch/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT:

 The kernel stack offset can be randomized (after pt_regs) by
 roughly 5 bits of entropy, frustrating memory corruption
 attacks that depend on stack address determinism or
 cross-syscall address exposures. This feature is controlled
 by kernel boot param "randomize_kstack_offset=on/off", and this
 config chooses the default boot state.

 Symbol: RANDOMIZE_KSTACK_OFFSET_DEFAULT [=n]
 Type  : bool
 Defined at arch/Kconfig:1114
   Prompt: Randomize kernel stack offset on syscall entry
   Depends on: HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET [=y]
   Location:
     -> General architecture-dependent options

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:58 -04:00
Fedora Kernel Team 85d9324043 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LOCKDEP_BITS:

 Try increasing this value if you hit "BUG: MAX_LOCKDEP_ENTRIES too low!" message.

 Symbol: LOCKDEP_BITS [=15]
 Type  : integer
 Range : [10 30]
 Defined at lib/Kconfig.debug:1373
   Prompt: Bitsize for MAX_LOCKDEP_ENTRIES
   Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)

---

 CONFIG_LOCKDEP_CHAINS_BITS:

 Try increasing this value if you hit "BUG: MAX_LOCKDEP_CHAINS too low!" message.

 Symbol: LOCKDEP_CHAINS_BITS [=16]
 Type  : integer
 Range : [10 30]
 Defined at lib/Kconfig.debug:1381
   Prompt: Bitsize for MAX_LOCKDEP_CHAINS
   Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)

---

 CONFIG_LOCKDEP_CIRCULAR_QUEUE_BITS:

 Try increasing this value if you hit "lockdep bfs error:-1" warning due to __cq_enqueue() failure.

 Symbol: LOCKDEP_CIRCULAR_QUEUE_BITS [=12]
 Type  : integer
 Range : [10 30]
 Defined at lib/Kconfig.debug:1405
   Prompt: Bitsize for elements in circular_queue struct
   Depends on: LOCKDEP [=y]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)

---

 CONFIG_LOCKDEP_STACK_TRACE_BITS:

 Try increasing this value if you hit "BUG: MAX_STACK_TRACE_ENTRIES too low!" message.

 Symbol: LOCKDEP_STACK_TRACE_BITS [=19]
 Type  : integer
 Range : [10 30]
 Defined at lib/Kconfig.debug:1389
   Prompt: Bitsize for MAX_STACK_TRACE_ENTRIES
   Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)

---

 CONFIG_LOCKDEP_STACK_TRACE_HASH_BITS:

 Try increasing this value if you need large MAX_STACK_TRACE_ENTRIES.

 Symbol: LOCKDEP_STACK_TRACE_HASH_BITS [=14]
 Type  : integer
 Range : [10 30]
 Defined at lib/Kconfig.debug:1397
   Prompt: Bitsize for STACK_TRACE_HASH_SIZE
   Depends on: LOCKDEP [=y] && !LOCKDEP_SMALL [=n]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:58 -04:00
Fedora Kernel Team 6b99cf6386 [redhat] New configs in drivers/cpufreq
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ACPI_CPPC_CPUFREQ_FIE:

 This extends frequency invariance support in the CPPC cpufreq driver,
 by using CPPC delivered and reference performance counters.

 If in doubt, say N.

 Symbol: ACPI_CPPC_CPUFREQ_FIE [=y]
 Type  : bool
 Defined at drivers/cpufreq/Kconfig.arm:22
   Prompt: Frequency Invariance support for CPPC cpufreq driver
   Depends on: CPU_FREQ [=y] && (ARM || ARM64 [=y]) && ACPI_CPPC_CPUFREQ [=m] && GENERIC_ARCH_TOPOLOGY [=y]
   Location:
     -> CPU Power Management
       -> CPU Frequency scaling
         -> CPU Frequency scaling (CPU_FREQ [=y])
           -> CPUFreq driver based on the ACPI CPPC spec (ACPI_CPPC_CPUFREQ [=m])

---

Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:58 -04:00
David Ward 0e8e457848 Set date in package release from repository commit, not system clock
Packages can be rebuilt from tagged commits in the kernel-ark repository by
cloning it and running the packaging scripts. This should be reproducible:
packages built from identical sources should have the same NVR.

For builds based on upstream snapshots, the package release contains a date
that is meant to correspond to changes in the fedora-ark repository. (It is
not the date of the upstream snapshot.) Instead, the packaging scripts set
this date from the system clock. Change this so that the commit date in the
kernel-ark repository is used.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:30:58 -04:00
David Ward 86a53ba7b9 Use a better upstream tarball filename for snapshots
For snapshot builds, the upstream tarball filename includes the date that
"make dist-sources" was run. This date has no relationship to the upstream
sources and should not be part of the filename.

The only other information in the filename is the abbreviated commit hash.
The filename does not directly show which upstream release preceded it.

Change the filename for upstream snapshots so it is based on the output of
"git describe". An example filename is:

    linux-5.12-rc8-53-g2a1d7946f.tar.xz

This is a snapshot of commit 2a1d7946f, which is 53 commits ahead of the
tag v5.12-rc8. Note that the object name v5.12-rc8-53-g2a1d7946f can be
used in Git commands, just like the tags v5.12-rc8, v5.12, or v5.12.1.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:30:58 -04:00
Don Zickus ce9c13efdc Don't create empty pending-common files on pending-fedora commits
There is a bug in gen_config_patches.sh which will assumes all new
configs are in redhat/configs/pending-common.  This is not true
for pending-fedora configs.  As a result the script reads the
pending-feodra config and tries to copy a pending-common config
into the final location.

The pending-common file does not exist thus creating an empty final
config file.

Fix this by filtering out any pending-fedora configs from the list of
configs to process.

Tested manually.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:30:58 -04:00
Fedora Kernel Team 1850348678 [redhat] New configs in drivers/thunderbolt
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_USB4_DMA_TEST:

 This allows sending and receiving DMA traffic through loopback
 connection. Loopback connection can be done by either special
 dongle that has TX/RX lines crossed, or by simply connecting a
 cable back to the host. Only enable this if you know what you
 are doing. Normal users and distro kernels should say N here.

 To compile this driver a module, choose M here. The module will be
 called thunderbolt_dma_test.

 Symbol: USB4_DMA_TEST [=n]
 Type  : tristate
 Defined at drivers/thunderbolt/Kconfig:34
   Prompt: DMA traffic test driver
   Depends on: USB4 [=y] && DEBUG_FS [=y]
   Location:
     -> Device Drivers
       -> Unified support for USB4 and Thunderbolt (USB4 [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:58 -04:00
Fedora Kernel Team 729bd324bc [redhat] New configs in drivers/ntb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NTB_EPF:

 This driver supports EPF NTB on configurable endpoint.
 If unsure, say N.

 Symbol: NTB_EPF [=n]
 Type  : tristate
 Defined at drivers/ntb/hw/epf/Kconfig:1
   Prompt: Generic EPF Non-Transparent Bridge support
   Depends on: NTB [=m] && m && MODULES [=y]
   Location:
     -> Device Drivers
       -> Non-Transparent Bridge support (NTB [=m])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:57 -04:00
Fedora Kernel Team 47e7dd5942 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARCH_APPLE:

 This enables support for Apple's in-house ARM SoC family, starting
 with the Apple M1.

 Symbol: ARCH_APPLE [=n]
 Type  : bool
 Defined at arch/arm64/Kconfig.platforms:29
   Prompt: Apple Silicon SoC family
   Location:
     -> Platform selection
 Selects: APPLE_AIC [=n]

---

 CONFIG_ARCH_INTEL_SOCFPGA:

 This enables support for Intel's SoCFPGA ARMv8 families:
 Stratix 10 (ex. Altera), Agilex and eASIC N5X.

 Symbol: ARCH_INTEL_SOCFPGA [=n]
 Type  : bool
 Defined at arch/arm64/Kconfig.platforms:254
   Prompt: Intel's SoCFPGA ARMv8 Families
   Location:
     -> Platform selection

---

 CONFIG_ARM64_EPAN:

 Enhanced Privileged Access Never (EPAN) allows Privileged
 Access Never to be used with Execute-only mappings.

 The feature is detected at runtime, and will remain disabled
 if the cpu does not implement the feature.
 Symbol: ARM64_EPAN [=y]
 Type  : bool
 Defined at arch/arm64/Kconfig:1695
   Prompt: Enable support for Enhanced Privileged Access Never (EPAN)
   Depends on: ARM64_PAN [=y]
   Location:
     -> Kernel Features
       -> ARMv8.7 architectural features

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:57 -04:00
Fedora Kernel Team 42ad88efaf [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ADV_SWBUTTON:

 Say Y here to enable support for Advantech software defined
 button feature. More information can be found at
 <http://www.advantech.com.tw/products/>

 To compile this driver as a module, choose M here. The module will
 be called adv_swbutton.

 Symbol: ADV_SWBUTTON [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:207
   Prompt: Advantech ACPI Software Button Driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && INPUT [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---

 CONFIG_GIGABYTE_WMI:

 Say Y here if you want to support WMI-based temperature reporting on
 Gigabyte mainboards.

 To compile this driver as a module, choose M here: the module will
 be called gigabyte-wmi.

 Symbol: GIGABYTE_WMI [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:126
   Prompt: Gigabyte WMI temperature driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m] && HWMON [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---

Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:57 -04:00
Fedora Kernel Team 4784f2c0e8 [redhat] New configs in drivers/misc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DW_XDATA_PCIE:

 This driver allows controlling Synopsys DesignWare PCIe traffic
 generator IP also known as xData, present in Synopsys DesignWare
 PCIe Endpoint prototype.

 If unsure, say N.

 Symbol: DW_XDATA_PCIE [=n]
 Type  : tristate
 Defined at drivers/misc/Kconfig:405
   Prompt: Synopsys DesignWare xData PCIe driver
   Depends on: PCI [=y]
   Location:
     -> Device Drivers
       -> Misc devices

---

 CONFIG_PVPANIC_MMIO:

 This driver provides support for the MMIO pvpanic device.

 Symbol: PVPANIC_MMIO [=n]
 Type  : tristate
 Defined at drivers/misc/pvpanic/Kconfig:15
   Prompt: pvpanic MMIO device support
   Depends on: HAS_IOMEM [=y] && (ACPI [=y] || OF [=n]) && PVPANIC [=y]
   Location:
     -> Device Drivers
       -> Misc devices
         -> pvpanic device support (PVPANIC [=y])

---

 CONFIG_PVPANIC_PCI:

 This driver provides support for the PCI pvpanic device.
 pvpanic is a paravirtualized device provided by QEMU which
 forwards the panic events from the guest to the host.

 Symbol: PVPANIC_PCI [=n]
 Type  : tristate
 Defined at drivers/misc/pvpanic/Kconfig:21
   Prompt: pvpanic PCI device support
   Depends on: PCI [=y] && PVPANIC [=y]
   Location:
     -> Device Drivers
       -> Misc devices
         -> pvpanic device support (PVPANIC [=y])

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:57 -04:00
Mike Snitzer df97820111 nvme: decouple basic ANA log page re-read support from native multipathing
BZ: 1948690
Upstream Status: RHEL-only

This commit offers a more refined version of this rhel-8.git commit:
b904f4b8e0f90 [nvme] nvme: decouple basic ANA log page re-read support from native multipathing

Whether or not ANA is present is a choice of the target implementation;
the host (and whether it supports multipathing) has _zero_ influence on
this. If the target declares a path as 'inaccessible' the path _is_
inaccessible to the host. As such, ANA support should be functional
even if native multipathing is not.

Introduce ability to always re-read ANA log page as required due to ANA
error and make current ANA state available via sysfs -- even if native
multipathing is disabled on the host (e.g. nvme_core.multipath=N).
This is achieved by factoring out nvme_update_ana() and calling it in
nvme_complete_rq() for all FAILOVER requests.

This affords userspace access to the current ANA state independent of
which layer might be doing multipathing. This makes 'nvme list-subsys'
show ANA state for all NVMe subsystems with multiple controllers. It
also allows userspace multipath-tools to rely on the NVMe driver for
ANA support while dm-multipath takes care of multipathing.

And as always, if embedded NVMe users do not want any performance
overhead associated with ANA or native NVMe multipathing they can
disable CONFIG_NVME_MULTIPATH.

Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2021-08-30 14:30:57 -04:00
Mike Snitzer 15671d5b3a nvme: allow local retry and proper failover for REQ_FAILFAST_TRANSPORT
BZ: 1948690
Upstream Status: RHEL-only

This commit offers a more minimalist version of these 2 rhel-8.git commits:
f8fb6ea1226e2 [nvme] nvme: update failover handling to work with REQ_FAILFAST_TRANSPORT
7dadadb072515 [nvme] nvme: allow retry for requests with REQ_FAILFAST_TRANSPORT set

REQ_FAILFAST_TRANSPORT is set by upper layer software that handles
multipathing. Unlike SCSI, NVMe's error handling was specifically
designed to handle local retry for non-path errors. As such, allow
NVMe's local retry mechanism to be used for requests marked with
REQ_FAILFAST_TRANSPORT.

In this way, the mechanism of NVMe multipath or other multipath are
now equivalent. The mechanism is: non path related error will be
retried locally, path related error is handled by multipath.

Also, introduce FAILUP handling for REQ_FAILFAST_TRANSPORT. Update
NVMe to allow failover of requests marked with either REQ_NVME_MPATH
or REQ_FAILFAST_TRANSPORT. This allows such requests to be given a
disposition of either FAILOVER or FAILUP respectively.

nvme_complete_rq() is updated to call nvme_failup_req() if
nvme_decide_disposition() returns FAILUP. nvme_failup_req() ensures
the request is completed with a retryable path error.

Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2021-08-30 14:30:57 -04:00
Mike Snitzer 84ddc21ca6 nvme: Return BLK_STS_TARGET if the DNR bit is set
BZ: 1948690
Upstream Status: RHEL-only

Signed-off-by: Mike Snitzer <snitzer@redhat.com>

rhel-8.git commit ef4ab90c12db5e0e50800ec323736b95be7a6ff5
Author: Mike Snitzer <snitzer@redhat.com>
Date:   Tue Aug 25 21:52:45 2020 -0400

    [nvme] nvme: Return BLK_STS_TARGET if the DNR bit is set
    
    Message-id: <20200825215248.2291-8-snitzer@redhat.com>
    Patchwork-id: 325178
    Patchwork-instance: patchwork
    O-Subject: [RHEL8.3 PATCH 07/10] nvme: Return BLK_STS_TARGET if the DNR bit is set
    Bugzilla: 1843515
    RH-Acked-by: David Milburn <dmilburn@redhat.com>
    RH-Acked-by: Gopal Tiwari <gtiwari@redhat.com>
    RH-Acked-by: Ewan Milne <emilne@redhat.com>
    
    BZ: 1843515
    Upstream Status: RHEL-only
    
    If the DNR bit is set we should not retry the command, even if
    the standard status evaluation indicates so.
    
    SUSE is carrying this patch in their kernel:
    https://lwn.net/Articles/800370/
    
    Based on patch posted for upstream inclusion but rejected:
    v1: https://lore.kernel.org/linux-nvme/20190806111036.113233-1-hare@suse.de/
    v2: https://lore.kernel.org/linux-nvme/20190807071208.101882-1-hare@suse.de/
    v2-keith: https://lore.kernel.org/linux-nvme/20190807144725.GB25621@localhost.localdomain/
    v3: https://lore.kernel.org/linux-nvme/20190812075147.79598-1-hare@suse.de/
    v3-keith: https://lore.kernel.org/linux-nvme/20190813141510.GB32686@localhost.localdomain/
    
    This commit's change is basically "v3-keith".
    
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>
    Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
2021-08-30 14:30:56 -04:00
Justin M. Forbes e2cbe15c6b Add redhat/configs/pending-common/generic/s390x/zfcpdump/CONFIG_NETFS_SUPPORT
The default for CONFIG_NETFS_SUPPORT is m and creates a config mismatch
on s390x zfcpdump as modules are disabled there. This turns it off for
that config.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:56 -04:00
Fedora Kernel Team 0d9ea9076a [redhat] AUTOMATIC: New configs 2021-08-30 14:30:56 -04:00
Fedora Kernel Team d59da67193 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:56 -04:00
Don Zickus d9165befcd Create ark-latest branch last for CI scripts
It was noticed with the change to use ark-infra, the CI scripts were
failing at 'git push gitlab $(git describe).

That command was supposed to push a newly created tag from 'make
dist-release-tag' which is pointed to by ark-latest.

A 'git describe' of ark-latest translates to that tag and is easily
pushed.  With the addition of 'ark-infra', the last branch checked out
is ark-infra.  A 'git describe' of that branch translates into an
un-tagged reference forcing the 'git push' script to fail.

Fix this by forcing the ark-latest branch to be checked last so that
'git describe' works correctly.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:30:56 -04:00
David Ward 1afc9640f8 Replace /usr/libexec/platform-python with /usr/bin/python3
The platform-python package was abandoned:
https://fedoraproject.org/wiki/Changes/Platform_Python_Stack

It does not exist in any supported version of Fedora or RHEL. All of them
provide a native Python 3 package where the interpreter is installed at
/usr/bin/python3. In an unprivileged environment, it may not be possible
to create a /usr/libexec/platform-python symlink to build these sources.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:30:56 -04:00
Fedora Kernel Team d7e92f86c7 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK:

 This adds support for SoundWire with Sound Open Firmware
 for Intel(R) platforms.
 Say Y if you want to enable SoundWire links with SOF.
 If unsure select "N".

 Symbol: SND_SOC_SOF_INTEL_SOUNDWIRE_LINK [=n]
 Type  : bool
 Defined at sound/soc/sof/intel/Kconfig:356
   Prompt: SOF support for SoundWire
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m] && ACPI [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
               -> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y])

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
- CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK set to y for x86 only.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:56 -04:00
Dave Airlie 2cde878356 [redhat] turn off legacy drm interfaces
ARK and Fedora now have the same settings, so consolidate them in the
common config directory.

Cc: Lyude Paul <lyude@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2021-08-30 14:30:56 -04:00
Fedora Kernel Team a876525254 [redhat] New configs in arch/s390
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEBUG_ENTRY:

 This option enables sanity checks in s390 low-level entry code.
 Some of these sanity checks may slow down kernel entries and
 exits or otherwise impact performance.

 If unsure, say N.

 Symbol: DEBUG_ENTRY [=n]
 Type  : bool
 Defined at arch/s390/Kconfig.debug:9
   Prompt: Debug low-level entry code
   Depends on: DEBUG_KERNEL [=y]
   Location:
     -> Kernel hacking
       -> s390 Debugging

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
- Set CONFIG_DEBUG_ENTRY for s390x debug variant.
- Removed redundant ark/generic CONFIG_DEBUG_ENTRY file.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:55 -04:00
Justin M. Forbes d2c4fb5e50 Turn off ADI_AXI_ADC and AD9467 which now require CONFIG_OF
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:55 -04:00
Patrick Talbert 2d15f7620e [redhat] Disable CONFIG_VDPA for s390x/zfcpdump
This is enabled as a module now for the generic case so we either need
to bake it in to the zfcpdump kernel or disable it. I chose the latter.

Cc: Philipp Rudo <prudo@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:55 -04:00
Don Zickus 6a9e779be0 Export ark infrastructure files
Allow developers to use the ark infrastructure work on upstream
git trees.  This change saves the redhat/ plus supporting files
on top of the 'master' branch.

A developer can then 'git merge ark-infra' to apply this
infrastructure.

"NO_CONFIGCHECKS make dist-configs" to create the configs. And
away they go.

Utilize the daily rawhide_release builds to create this branch.  It
fits with the theme and is quick and easy to do in this job.  Note
I use the 'ark-latest' as the source of the export.  This should
include any environment fixes for the developer.

Tested by copy-n-pasting manual each step in the script to generate
the original ark-infra branch.  The gitlab-ci.yml change should be
intuitive enough to skip testing.

V2: Use git-archive and better sed regexp
V3: remove git reset and sed
V4: added comment about kabi-module (no new changes)
2021-08-30 14:30:55 -04:00
Jeremy Cline 4f0aef8908 [redhat] New configs in drivers/virtio 2021-08-30 14:30:55 -04:00
Jeremy Cline 1972880e21 [redhat] New configs in drivers/gpu 2021-08-30 14:30:55 -04:00
Don Zickus 08c6e180fd docs: Update docs to reflect newer workflow.
The workflow has recently changed such that all development is done
on the 'os-build' branch.  Update the docs to show how easy it is
to make a change, commit it, generate the srpm and upload it to koji.

Also add it a build dep for making a srpm: patchutils (for filterdiff).

V2: Fix checkout command and setup master branch
V3: Use default upstream/master and git pull mechanism
V4: Use default origin/master.  Add text to setup mirroring

Cc: Bastien Nocera <bnocera@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:30:55 -04:00
Don Zickus 4a9664f7a0 Use upstream/master for merge-base with fallback to master
In Makefile.common there is logic that determines what the
merge-base is and is used to generate changelogs correctly.

The logic assumes a 'master' branch exists and is up to date.
However, the documentation recommends using 'upstream/master' to
keep everything up to date.

Let's sync the documentation and code and use upstream/master if
it exists otherwise, use 'master' as the fallback.  If neither
exists error out.

Update redhat/genspec.sh to handle a different master too.

The 'error' out solves another problem when a master branch is not
defined not is 'upstream' used as recommended.

V2: change 'upstream' to 'origin' (Justin F.)

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:30:55 -04:00
Hans de Goede 1e1628f46d Fedora: Turn off the SND_INTEL_BYT_PREFER_SOF option
The plan was to enable this by default for F34+ :
https://fedoraproject.org/w/index.php?title=Changes/SofDefaultForIntelLpe

But there are still too many issues with the new SOF driver, see:
https://mailman.alsa-project.org/pipermail/sound-open-firmware/2021-March/004175.html

So disable this again to switch back to the old proven SST driver.

Note the same change was already made for the fedora-5.11 branch:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/980

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 14:30:54 -04:00
Paul Bolle a7486ef1e5 filter-modules.sh.fedora: clean up "netprots"
Fedora's kernel build doesn't include the dccp net protocol modules.
(CONFIG_IP_DCCP is not set.) So remove dccp from "netprots".

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:54 -04:00
Paul Bolle 6802f577ca filter-modules.sh.fedora: clean up "scsidrvs"
Fedora's kernel build doesn't include the aic94xx scsi module.
(CONFIG_SCSI_AIC94XX is not set.) So remove aic94xx from "scsidrvs".

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:54 -04:00
Paul Bolle 4202a36244 filter-*.sh.fedora: clean up "ethdrvs"
Fedora's kernel build doesn't include renesas ethernet modules. (Neither
CONFIG_ARCH_RENESAS nor CONFIG_COMPILE_TEST are set.) So remove renesas
from "ethdrvs".

The oki-semi ethernet module is only built as a builtin.
(CONFIG_NET_VENDOR_OKI=y.) So remove oki-semi from "ethdrvs" too.

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:54 -04:00
Paul Bolle 978ed5707f filter-*.sh.fedora: clean up "driverdirs"
Fedora's kernel build doesn't include isdn modules anymore. (CONFIG_ISDN
is not set.) So remove isdn from "driverdirs".

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:54 -04:00
Paul Bolle 1144435e15 filter-*.sh.fedora: remove incorrect entries
There are a number of incorrect entries in the various lists used to
filter modules into modules-extra:
	8 directories that have been removed upstream, because their
	drivers have been dropped:
		drivers/fmc
		drivers/net/ethernet/icplus
		drivers/net/irda
		drivers/scsi/mpt2sas
		drivers/usb/wusbcore
		drivers/uwb
		fs/ncpfs
		net/irda
	1 directory that has been renamed upstream (to .../tiny):
		drivers/gpu/drm/tinydrm
	3 directories that are actually modules:
		drivers/gpu/drm/sun4i-drm-hdmi
		drivers/scsi/advansys
		drivers/scsi/wd719x

Update the filter lists accordingly.

(Note that sun4i-drm-hdmi is already filtered through
"drivers/gpu/drm/sun4i/" and that advansys and wd719x could be added to
the singlemods list, if that is still desirable.)

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:54 -04:00
Paul Bolle 95cb8c8a68 filter-*.sh.fedora: clean up "singlemods"
There are some pointless modules in the singlemods lists:
	hwa-hc, iw_cxgb3, and cxgb3i_ddp have been removed from the kernel
	iw_cxgb4 is already filtered out (by drivers/infiniband)
	cxgb3i and cxgb4i are also filtered out (by drivers/scsi/cxgbi)
	chtls is also filtered out (by drivers/net/ethernet/chelsio)

Remove these modules from these lists.

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:54 -04:00
Paul Bolle 43a70753e9 filter-modules.sh.fedora: drop unused list "iiodrvs"
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:54 -04:00
Fedora Kernel Team 44489176dd [redhat] AUTOMATIC: New configs 2021-08-30 14:30:54 -04:00
Prarit Bhargava 72ab29adf1 RHMAINTAINERS: Update Apr 15 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:54 -04:00
Nico Pache 1ec60fa332 Update mod-internal to fix depmod issue
Currently rhel builds are failing due to a depmod on scftorture which
expects torture.o which is being filtered into the internals package.

Signed-off-by: Nico Pache <npache@redhat.com>
2021-08-30 14:30:54 -04:00
Tom Stellard eff1d044ba [redhat] spec: Disable ipaclones when building with clang
clang does not have a -fdump-ipa-clones option

Signed-off-by: Tom Stellard <tstellar@redhat.com>
2021-08-30 14:30:53 -04:00
Fedora Kernel Team e8524e2f35 [redhat] New configs in crypto/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CRYPTO_SM2:

 Generic implementation of the SM2 public key algorithm. It was
 published by State Encryption Management Bureau, China.
 as specified by OSCCA GM/T 0003.1-2012 -- 0003.5-2012.

 References:
 https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02
 http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtml
 http://www.gmbz.org.cn/main/bzlb.html

 Symbol: CRYPTO_SM2 [=n]
 Type  : tristate
 Defined at crypto/Kconfig:263
   Prompt: SM2 algorithm
   Depends on: CRYPTO [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
 Selects: CRYPTO_SM3 [=n] && CRYPTO_AKCIPHER [=y] && CRYPTO_MANAGER [=y] && MPILIB [=y] && ASN1 [=y]

---

 CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE:

 Allow obsolete cryptographic algorithms to be selected that have
 already been phased out from internal use by the kernel, and are
 only useful for userspace clients that still rely on them.

 Symbol: CRYPTO_USER_API_ENABLE_OBSOLETE [=y]
 Type  : bool
 Defined at crypto/Kconfig:1915
   Prompt: Enable obsolete cryptographic algorithms for userspace
   Depends on: CRYPTO [=y] && CRYPTO_USER_API [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])

---

 CONFIG_CRYPTO_USER_API_RNG_CAVP:

 This option enables extra API for CAVP testing via the user-space
 interface: resetting of DRBG entropy, and providing Additional Data.
 This should only be enabled for CAVP testing. You should say
 no unless you know what this is.

 Symbol: CRYPTO_USER_API_RNG_CAVP [=n]
 Type  : bool
 Defined at crypto/Kconfig:1895
   Prompt: Enable CAVP testing of DRBG
   Depends on: CRYPTO [=y] && CRYPTO_USER_API_RNG [=y] && CRYPTO_DRBG [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> User-space interface for random number generator algorithms (CRYPTO_USER_API_RNG [=y])

---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v4:
- CONFIG_CRYPTO_SM4_ARM64_CE removed from fedora configs.
v3:
- CONFIG_CRYPTO_SM4 is set m.
- CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE not defined for s390x/zfsdump.
- CONFIG_CRYPTO_SM2,3,4 set to y for s390x/zfsdump.
v2:
- CONFIG_CRYPTO_SM3=m is set.
- CONFIG_CRYPTO_SM4 and CONFIG_CRYPTO_SM4_ARM64_CE are NOT set; they are left
  enabled as modules in fedora.
- CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE and
  CONFIG_CRYPTO_{ANUBIS,ARC4,KHAZAD,SEED,TEA} are disabled everywhere EXCEPT
  they are all still enabled for s390x/zfcpdump.
- CONFIG_CRYPTO_USER_API_RNG_CAVP is disabled everywhere.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:53 -04:00
Jeremy Cline 32a7268377 [redhat] New configs in drivers/virtio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VIRTIO_VDPA:

 This driver provides support for virtio based paravirtual
 device driver over vDPA bus. For this to be useful, you need
 an appropriate vDPA device implementation that operates on a
 physical device to allow the datapath of virtio to be
 offloaded to hardware.

 If unsure, say M.

 Symbol: VIRTIO_VDPA [=n]
 Type  : tristate
 Defined at drivers/virtio/Kconfig:46
   Prompt: vDPA driver for virtio devices
   Depends on: VIRTIO_MENU [=y]
   Location:
     -> Device Drivers
       -> Virtio drivers (VIRTIO_MENU [=y])
 Selects: VDPA [=n] && VIRTIO [=y]

Enabled at the request of Michael S. Tsirkin. Disabled on zfcpdump as it
seems unnecessary and introduces a number of dependencies.

---

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
2021-08-30 14:30:53 -04:00
Jeremy Cline 15b324d78c [redhat] New configs in drivers/vhost
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VHOST_VDPA:

 This kernel module can be loaded in host kernel to accelerate
 guest virtio devices with the vDPA-based backends.

 To compile this driver as a module, choose M here: the module
 will be called vhost_vdpa.

 Symbol: VHOST_VDPA [=n]
 Type  : tristate
 Defined at drivers/vhost/Kconfig:62
   Prompt: Vhost driver for vDPA-based backend
   Depends on: VHOST_MENU [=y] && EVENTFD [=y]
   Location:
     -> Device Drivers
       -> VHOST drivers (VHOST_MENU [=y])
 Selects: VHOST [=m] && VDPA [=n]

Enabled at the request of Michael S. Tsirkin. Disabled on zfcpdump as it
seems unnecessary.

---

Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
2021-08-30 14:30:53 -04:00
Justin Forbes 14654f764f [redhat] New configs in drivers/vdpa 2021-08-30 14:30:53 -04:00
Vladis Dronov 59fb4b88f7 [redhat] Move ARM SMC configs to a proper location
ARM SMC configs in generic/aarch64/ are not in a proper location.
Move them to a proper one, namely, ark/generic/arm/aarch64/.

Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:30:53 -04:00
Justin M. Forbes 06e4012650 Turn on CONFIG_VDPA_SIM_NET (rhbz 1942343)
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:53 -04:00
Fedora Kernel Team a7ce6decbf [redhat] New configs in drivers/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CHARGER_BQ25980:

 Say Y to enable support for the TI BQ25980, BQ25975 and BQ25960
 series of fast battery chargers.

 Symbol: CHARGER_BQ25980 [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:639
   Prompt: TI BQ25980 battery charger driver
   Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])
 Selects: REGMAP_I2C [=m]

---

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:52 -04:00
Fedora Kernel Team ad27e1b7f0 [redhat] New configs in drivers/media
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VIDEO_IMX334:

 This is a Video4Linux2 sensor driver for the Sony
 IMX334 camera.

 To compile this driver as a module, choose M here: the
 module will be called imx334.

 Symbol: VIDEO_IMX334 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:816
   Prompt: Sony IMX334 sensor support
   Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n]

---

 CONFIG_VIDEO_OV5648:

 This is a Video4Linux2 sensor driver for the OmniVision
 OV5648 camera.

 To compile this driver as a module, choose M here: the
 module will be called ov5648.

 Symbol: VIDEO_OV5648 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:953
   Prompt: OmniVision OV5648 sensor support
   Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]

---

 CONFIG_VIDEO_OV8865:

 This is a Video4Linux2 sensor driver for OmniVision
 OV8865 camera sensor.

 To compile this driver as a module, choose M here: the
 module will be called ov8865.

 Symbol: VIDEO_OV8865 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:1078
   Prompt: OmniVision OV8865 sensor support
   Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]

---

 CONFIG_VIDEO_RDACM21:

 This driver supports the IMI RDACM21 GMSL camera, used in
 ADAS systems.

 This camera should be used in conjunction with a GMSL
 deserialiser such as the MAX9286.

 Symbol: VIDEO_RDACM21 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:1260
   Prompt: IMI RDACM21 camera support
   Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y]
   Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: V4L2_FWNODE [=n] && VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && VIDEO_MAX9271_LIB [=n]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:52 -04:00
Fedora Kernel Team 89a0f3d810 [redhat] New configs in drivers/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CHARGER_BQ256XX:

 Say Y to enable support for the TI BQ256XX battery chargers. The
 BQ256XX family of devices are highly-integrated, switch-mode battery
 charge management and system power path management devices for single
 cell Li-ion and Li-polymer batteries.

 Symbol: CHARGER_BQ256XX [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:658
   Prompt: TI BQ256XX battery charger driver
   Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])
 Selects: REGMAP_I2C [=m]

---

 CONFIG_CHARGER_LTC4162L:

 Say Y to include support for the Analog Devices (Linear Technology)
 LTC4162-L battery charger connected to I2C.

 Symbol: CHARGER_LTC4162L [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:517
   Prompt: LTC4162-L charger
   Depends on: POWER_SUPPLY [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])
 Selects: REGMAP_I2C [=m]

---

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:52 -04:00
Fedora Kernel Team 32f9ec1444 New configs in drivers/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_POWER_RESET_VEXPRESS:

 Power off and reset support for the ARM Ltd. Versatile
 Express boards.

 Symbol: POWER_RESET_VEXPRESS [=n]
 Type  : bool
 Defined at drivers/power/reset/Kconfig:184
   Prompt: ARM Versatile Express power-off and reset driver
   Depends on: POWER_RESET [=y] && (ARM || ARM64 [=y]) && VEXPRESS_CONFIG [=y]=y
   Location:
     -> Device Drivers
       -> Board level reset or power off (POWER_RESET [=y])

Cc: Lenny Szubowicz <lszubowi@redhat.com>
2021-08-30 14:30:52 -04:00
Fedora Kernel Team cc210725eb [redhat] New configs in drivers/nvmem
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NVMEM_RMEM:

 This driver maps reserved memory into an nvmem device. It might be
 useful to expose information left by firmware in memory.

 This driver can also be built as a module. If so, the module
 will be called nvmem-rmem.
 Symbol: NVMEM_RMEM [=n]
 Type  : tristate
 Defined at drivers/nvmem/Kconfig:273
   Prompt: Reserved Memory Based Driver Support
   Depends on: NVMEM [=y]
   Location:
     -> Device Drivers
       -> NVMEM Support (NVMEM [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:52 -04:00
Justin M. Forbes c70906696d Turn on CONFIG_NOUVEAU_DEBUG_PUSH for debug configs
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:52 -04:00
Fedora Kernel Team b7e7527e2e [redhat] New configs in fs/fuse
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FUSE_DAX:

 This allows bypassing guest page cache and allows mapping host page
 cache directly in guest address space.

 If you want to allow mounting a Virtio Filesystem with the "dax"
 option, answer Y.

 Symbol: FUSE_DAX [=y]
 Type  : bool
 Defined at fs/fuse/Kconfig:42
   Prompt: Virtio Filesystem Direct Host Memory Access support
   Depends on: VIRTIO_FS [=m] && FS_DAX [=y] && DAX_DRIVER [=y]
   Location:
     -> File systems
       -> FUSE (Filesystem in Userspace) support (FUSE_FS [=m])
         -> Virtio Filesystem (VIRTIO_FS [=m])
 Selects: INTERVAL_TREE [=y]

---

Cc: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:52 -04:00
Fedora Kernel Team 43e2e8c552 [redhat] New configs in drivers/thunderbolt
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_USB4_DEBUGFS_WRITE:

 Enables writing to device configuration registers through
 debugfs interface.

 Only enable this if you know what you are doing! Never enable
 this for production systems or distro kernels.

 Symbol: USB4_DEBUGFS_WRITE [=n]
 Type  : bool
 Defined at drivers/thunderbolt/Kconfig:21
   Prompt: Enable write by debugfs to configuration spaces (DANGEROUS)
   Depends on: USB4 [=y]
   Location:
     -> Device Drivers
       -> Unified support for USB4 and Thunderbolt (USB4 [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:51 -04:00
Fedora Kernel Team 4f9ce9fc95 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:51 -04:00
Justin M. Forbes 7c010832d8 Turn off KFENCE sampling by default for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:51 -04:00
Justin M. Forbes 8405d2edb0 Fedora config updates round 2
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:51 -04:00
Jeremy Cline fbe4eb9407 New configs in drivers/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_QCOM_OCMEM:

 The On Chip Memory (OCMEM) allocator allows various clients to
 allocate memory from OCMEM based on performance, latency and power
 requirements. This is typically used by the GPU, camera/video, and
 audio components on some Snapdragon SoCs.

 Symbol: QCOM_OCMEM [=n]
 Type  : tristate
 Prompt: Qualcomm On Chip Memory (OCMEM) driver
   Location:
     -> Device Drivers
       -> SOC (System On Chip) specific Drivers
         -> Qualcomm SoC drivers
   Defined at drivers/soc/qcom/Kconfig:69
   Depends on: ARCH_QCOM [=y]
   Selects: QCOM_SCM [=n]
2021-08-30 14:30:51 -04:00
Fedora Kernel Team 0017eaf0d1 [redhat] New configs in drivers/hid
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HID_PLAYSTATION:

 Provides support for Sony PS5 controllers including support for
 its special functionalities e.g. touchpad, lights and motion
 sensors.

 Symbol: HID_PLAYSTATION [=n]
 Type  : tristate
 Defined at drivers/hid/Kconfig:856
   Prompt: PlayStation HID Driver
   Depends on: INPUT [=y] && HID [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> HID bus support (HID [=y])
           -> Special HID drivers
 Selects: CRC32 [=y] && POWER_SUPPLY [=y]

---

 CONFIG_I2C_HID_ACPI:

 Say Y here if you use a keyboard, a touchpad, a touchscreen, or any
 other HID based devices which is connected to your computer via I2C.
 This driver supports ACPI-based systems.

 If unsure, say N.

 This support is also available as a module.  If so, the module
 will be called i2c-hid-acpi.  It will also build/depend on the
 module i2c-hid.

 Symbol: I2C_HID_ACPI [=n]
 Type  : tristate
 Defined at drivers/hid/i2c-hid/Kconfig:5
   Prompt: HID over I2C transport layer ACPI driver
   Depends on: I2C [=y] && INPUT [=y] && ACPI [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> I2C HID support

---

 CONFIG_I2C_HID_OF:

 Say Y here if you use a keyboard, a touchpad, a touchscreen, or any
 other HID based devices which is connected to your computer via I2C.
 This driver supports Open Firmware (Device Tree)-based systems.

 If unsure, say N.

 This support is also available as a module.  If so, the module
 will be called i2c-hid-of.  It will also build/depend on the
 module i2c-hid.

 Symbol: I2C_HID_OF [=n]
 Type  : tristate
 Defined at drivers/hid/i2c-hid/Kconfig:20
   Prompt: HID over I2C transport layer Open Firmware driver
   Depends on: I2C [=y] && INPUT [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> I2C HID support

---

 CONFIG_I2C_HID_OF_GOODIX:

 Say Y here if you want support for Goodix i2c devices that use
 the i2c-hid protocol on Open Firmware (Device Tree)-based
 systems.

 If unsure, say N.

 This support is also available as a module.  If so, the module
 will be called i2c-hid-of-goodix.  It will also build/depend on
 the module i2c-hid.

 Symbol: I2C_HID_OF_GOODIX [=n]
 Type  : tristate
 Defined at drivers/hid/i2c-hid/Kconfig:35
   Prompt: Driver for Goodix hid-i2c based devices on OF systems
   Depends on: I2C [=y] && INPUT [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> I2C HID support

---

Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>

v2:
- CONFIG_HID_PLAYSTATION changed to m.
- CONFIG_PLAYSTATION_FF set to y.
- CONFIG_I2C_HID_ACPI changed to m.
- CONFIG_I2C_HID_OF set to m for aarch64.
- CONFIG_I2C_HID_OF_GOODIX set to m for aarch64.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:51 -04:00
Fedora Kernel Team 53b5f95167 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CSD_LOCK_WAIT_DEBUG:

 This option enables debug prints when CPUs are slow to respond
 to the smp_call_function*() IPI wrappers.  These debug prints
 include the IPI handler function currently executing (if any)
 and relevant stack traces.

 Symbol: CSD_LOCK_WAIT_DEBUG [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:1380
   Prompt: Debugging for csd_lock_wait(), called from smp_call_function*()
   Depends on: DEBUG_KERNEL [=y] && 64BIT [=y]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)

---

 CONFIG_SCF_TORTURE_TEST:

 This option provides a kernel module that runs torture tests
 on the smp_call_function() family of primitives.  The kernel
 module may be built after the fact on the running kernel to
 be tested, if desired.

 Symbol: SCF_TORTURE_TEST [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:1370
   Prompt: torture tests for smp_call_function*()
   Depends on: DEBUG_KERNEL [=y]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)
 Selects: TORTURE_TEST [=n]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:51 -04:00
Paul Bolle 00efc586af filter-modules.sh: Fix copy/paste error 'input'
Fix a copy/paste error of 'input' and use the obviously intended 'char'.
The effect of this fix is that the cm4000_cs, cm4040_cs and mwave
modules will now be shipped in Fedora's kernel-modules package, as was
apparently intended. Nothing should change for RHEL, which actually
doesn't build these modules.

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-08-30 14:30:50 -04:00
Justin M. Forbes c93f5c6d84 Update module filtering for 5.12 kernels
Without these changes, the build fails due to depmod issues.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:50 -04:00
Fedora Kernel Team af35983c2b [redhat] New configs in drivers/watchdog
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_SMC_WATCHDOG:

 Say Y here to include support for a watchdog timer
 implemented by the EL3 Secure Monitor on ARM platforms.
 Requires firmware support.
 To compile this driver as a module, choose M here: the
 module will be called arm_smc_wdt.

 Symbol: ARM_SMC_WATCHDOG [=n]
 Type  : tristate
 Defined at drivers/watchdog/Kconfig:871
   Prompt: ARM Secure Monitor Call based watchdog support
   Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y]
   Location:
     -> Device Drivers
       -> Watchdog Timer Support (WATCHDOG [=y])
 Selects: WATCHDOG_CORE [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:50 -04:00
Fedora Kernel Team 952ed690c4 [redhat] New configs in drivers/media
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VIDEO_IMX214:

 This is a Video4Linux2 sensor driver for the Sony
 IMX214 camera.

 To compile this driver as a module, choose M here: the
 module will be called imx214.

 Symbol: VIDEO_IMX214 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:741
   Prompt: Sony IMX214 sensor support
   Depends on: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: V4L2_FWNODE [=n] && MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && REGMAP_I2C [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:50 -04:00
Fedora Kernel Team 6f19d1c817 [redhat] New configs in drivers/input
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INPUT_DA7280_HAPTICS:

 Say Y to enable support for the Dialog DA7280 haptics driver.
 The haptics can be controlled by PWM or GPIO
 with I2C communication.

 To compile this driver as a module, choose M here: the
 module will be called da7280.

 Symbol: INPUT_DA7280_HAPTICS [=n]
 Type  : tristate
 Defined at drivers/input/misc/Kconfig:623
   Prompt: Dialog Semiconductor DA7280 haptics support
   Depends on: !UML && INPUT_MISC [=y] && INPUT [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Miscellaneous devices (INPUT_MISC [=y])
 Selects: REGMAP_I2C [=m]

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:50 -04:00
Fedora Kernel Team b1a54683aa [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_TRIGGER_TTY:

 This allows LEDs to be controlled by activity on ttys which includes
 serial devices like /dev/ttyS0.

 When build as a module this driver will be called ledtrig-tty.

 Symbol: LEDS_TRIGGER_TTY [=n]
 Type  : tristate
 Defined at drivers/leds/trigger/Kconfig:147
   Prompt: LED Trigger for TTY devices
   Depends on: NEW_LEDS [=y] && LEDS_TRIGGERS [=y] && TTY [=y]
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])
         -> LED Trigger support (LEDS_TRIGGERS [=y])

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:50 -04:00
Fedora Kernel Team fc8efdf67d [redhat] New configs in drivers/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LITEX_SOC_CONTROLLER:

 This option enables the SoC Controller Driver which verifies
 LiteX CSR access and provides common litex_get_reg/litex_set_reg
 accessors.
 All drivers that use functions from litex.h must depend on
 LITEX.

 Symbol: LITEX_SOC_CONTROLLER [=n]
 Type  : tristate
 Defined at drivers/soc/litex/Kconfig:8
   Prompt: Enable LiteX SoC Controller driver
   Depends on: OF [=y] || COMPILE_TEST [=n]
   Location:
     -> Device Drivers
       -> SOC (System On Chip) specific Drivers
         -> Enable LiteX SoC Builder specific drivers
 Selects: LITEX [=n]

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:49 -04:00
Mark Mielke 7542480366 Fix genlog.py to ensure that comments retain "%" characters. 2021-08-30 14:30:49 -04:00
Patrick Talbert c91883d965 [redhat] New configs in drivers/clk
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CLK_GFM_LPASS_SM8250:

 Support for the Glitch Free Mux (GFM) Low power audio
 subsystem (LPASS) clocks found on SM8250 SoCs.

 Symbol: CLK_GFM_LPASS_SM8250 [=n]
 Type  : tristate
 Defined at drivers/clk/qcom/Kconfig:522
   Prompt: SM8250 GFM LPASS Clocks
   Depends on: COMMON_CLK [=y] && COMMON_CLK_QCOM [=y]
   Location:
     -> Device Drivers
       -> Common Clock Framework (COMMON_CLK [=y])
         -> Support for Qualcomm's clock controllers (COMMON_CLK_QCOM [=y])

---

 CONFIG_COMMON_CLK_FSL_FLEXSPI:

 On Layerscape SoCs there is a special clock for the FlexSPI
 interface.

 Symbol: COMMON_CLK_FSL_FLEXSPI [=n]
 Type  : tristate
 Defined at drivers/clk/Kconfig:191
   Prompt: Clock driver for FlexSPI on Layerscape SoCs
   Depends on: COMMON_CLK [=y] && (ARCH_LAYERSCAPE [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Common Clock Framework (COMMON_CLK [=y])

---

 CONFIG_SC_CAMCC_7180:

 Support for the camera clock controller on Qualcomm Technologies, Inc
 SC7180 devices.
 Say Y if you want to support camera devices and functionality such as
 capturing pictures.

 Symbol: SC_CAMCC_7180 [=n]
 Type  : tristate
 Defined at drivers/clk/qcom/Kconfig:293
   Prompt: SC7180 Camera Clock Controller
   Depends on: COMMON_CLK [=y] && COMMON_CLK_QCOM [=y]
   Location:
     -> Device Drivers
       -> Common Clock Framework (COMMON_CLK [=y])
         -> Support for Qualcomm's clock controllers (COMMON_CLK_QCOM [=y])
 Selects: SC_GCC_7180 [=m]

---

 CONFIG_SDX_GCC_55:

 Support for the global clock controller on SDX55 devices.
 Say Y if you want to use peripheral devices such as UART,
 SPI, I2C, USB, SD/UFS, PCIe etc.

 Symbol: SDX_GCC_55 [=n]
 Type  : tristate
 Defined at drivers/clk/qcom/Kconfig:425
   Prompt: SDX55 Global Clock Controller
   Depends on: COMMON_CLK [=y] && COMMON_CLK_QCOM [=y]
   Location:
     -> Device Drivers
       -> Common Clock Framework (COMMON_CLK [=y])
         -> Support for Qualcomm's clock controllers (COMMON_CLK_QCOM [=y])
 Selects: QCOM_GDSC [=y]

---

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:49 -04:00
Fedora Kernel Team 6f9a967bf1 [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_LP50XX:

 If you say yes here you get support for the Texas Instruments
 LP5036, LP5030, LP5024, LP5018, LP5012 and LP5009 LED driver.

 To compile this driver as a module, choose M here: the
 module will be called leds-lp50xx.

 Symbol: LEDS_LP50XX [=n]
 Type  : tristate
 Defined at drivers/leds/Kconfig:398
   Prompt: LED Support for TI LP5036/30/24/18/12/9 LED driver chip
   Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y] && REGMAP_I2C [=m] && (LEDS_CLASS_MULTICOLOR [=n] || !LEDS_CLASS_MULTICOLOR [=n])
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:49 -04:00
Fedora Kernel Team ea6a592fed [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:49 -04:00
Fedora Kernel Team c25fba8280 New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_AW2013:

 This option enables support for the AW2013 3-channel
 LED driver.

 To compile this driver as a module, choose M here: the module
 will be called leds-aw2013.

 Symbol: LEDS_AW2013 [=n]
 Type  : tristate
 Defined at drivers/leds/Kconfig:106
   Prompt: LED support for Awinic AW2013
   Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y] && I2C [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])

Cc: Tony Camuso <tcamuso@redhat.com>
2021-08-30 14:30:49 -04:00
David Ward 803856c3c8 Limit CONFIG_USB_CDNS_SUPPORT to x86_64 and arm in Fedora
This option was enabled in commit 1ec8c0f7827c, but it depends on
CONFIG_USB_XHCI_PLATFORM, which is only enabled on x86_64 and arm.

Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-08-30 14:30:49 -04:00
Fedora Kernel Team 6468b4e29c [redhat] New configs in drivers/input
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RMI4_F3A:

 Say Y here if you want to add support for RMI4 function 3A.

 Function 3A provides GPIO support for RMI4 devices. This includes
 support for buttons on TouchPads and ClickPads.

 Symbol: RMI4_F3A [=n]
 Type  : bool
 Defined at drivers/input/rmi4/Kconfig:103
   Prompt: RMI4 Function 3A (GPIO)
   Depends on: !UML && INPUT [=y] && RMI4_CORE [=m]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Synaptics RMI4 bus support (RMI4_CORE [=m])

---

 CONFIG_TOUCHSCREEN_ZINITIX:

 Say Y here if you have a touchscreen using Zinitix bt541,
 or something similar enough.

 If unsure, say N.

 To compile this driver as a module, choose M here: the
 module will be called zinitix.

 Symbol: TOUCHSCREEN_ZINITIX [=n]
 Type  : tristate
 Defined at drivers/input/touchscreen/Kconfig:1325
   Prompt: Zinitix touchscreen support
   Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Touchscreens (INPUT_TOUCHSCREEN [=y])

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:48 -04:00
Fedora Kernel Team 0cfbccd3af [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_RT8515:

 This option enables support for the Richtek RT8515 flash
 and torch LEDs found on some mobile phones.

 To compile this driver as a module, choose M here: the module
 will be called leds-rt8515.

 Symbol: LEDS_RT8515 [=n]
 Type  : tristate
 Defined at drivers/leds/flash/Kconfig:5
   Prompt: LED support for Richtek RT8515 flash/torch LED
   Depends on: NEW_LEDS [=y] && LEDS_CLASS_FLASH [=m] && GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:48 -04:00
Fedora Kernel Team 30f8e1bd73 [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_BLINK:

 This option enables blink support for the leds class.
 If unsure, say Y.

 Symbol: LEDS_BLINK [=n]
 Type  : bool
 Defined at drivers/leds/blink/Kconfig:1
   Prompt: LED Blink support
   Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y]
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:47 -04:00
Peter Robinson 0cc73eb09b Fedora: Enable CHARGER_GPIO on aarch64 too
The CHARGER_GPIO is needed for the Pinebook Pro for the battery
fuel guage, probably other devices too.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:47 -04:00
Fedora Kernel Team 1fd8d383cc [redhat] AUTOMATIC: New configs 2021-08-30 14:30:47 -04:00
Justin M. Forbes 74f6df802f Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:46 -04:00
Don Zickus 3abd35764f [redhat] Update configs for mod-internal.list
Several of the options for mod-internal.list are now out of sync
with RHEL8. Adjust accordingly.

Cc: Waiman Long <longman@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>

V2: rebase to latest
V3: Adjust CONFIG_NET_ACT_ options (Jiri B.)
V4: Update TORTURE_TEST configs (Waiman L.)
V5: Enable CONFIG_NET_ACT_{CTINFO|MPLS} to 'm' for Fedora (Jiri B.)
V6: Remove duplicate dmatest (Herton)
2021-08-30 14:30:46 -04:00
Hangbin Liu 63c0f64e7d wireguard: mark as Tech Preview
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1613522
Upstream: RHEL only

WireGuard is Tech Preview in RHEL 9.0.

Signed-off-by: Hangbin Liu <haliu@redhat.com>
2021-08-30 14:30:46 -04:00
Hangbin Liu 5b57d84cc7 configs: enable CONFIG_WIREGUARD in ARK
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1613522
Upstream: RHEL only

Enable CONFIG_WIREGUARD as requested in the bugzilla. Configs
CONFIG_CRYPTO_LIB_BLAKE2S, CONFIG_CRYPTO_LIB_CHACHA20POLY1305,
CONFIG_CRYPTO_LIB_CURVE25519 are needed by wireguard.

Remove the fedora specific configs and enable them in common folder.
Do not enable it on zfcpdump as it has "#CONFIG_INET is not set".

Disabling wireguard in FIPS mode will be fixed in another bug.

Signed-off-by: Hangbin Liu <haliu@redhat.com>
2021-08-30 14:30:46 -04:00
Don Zickus 46a70cd66d Remove duplicate configs acroos fedora, ark and common
Started with a bunch of scripts to filter out duplicates.  Then
ran into all the override quirks and quickly and to revert large
chunks of it.

What is left is duplicates and cleanups of a small set of configs.

The SPEAKUP stuff seemed easy to consolidate.
The DW_DMAC_* configs were tricky because I could not delete the Fedora
overrides.
The EXPOLINE_* configs are s390x specific and with a little manual
cleanup made it work.
The HOTPLUG_PCI_SHPC had some override quirks but a few tweaks I can
easily sync everything up.

One new exposure is TEST_MIN_HEAP is now enabled on fedora-debug.  I
think that was the original intent but the feodra override accidentally
disabled it from common.

Verified by comparing the original 'make dist-configs; make
dist-fedora-configs' with the new version.  Other than TEST_MIN_HEAP
everything else matches.

This whole exercise made me frown with how the common configs and the
overrides work.  Maybe evaluate_configs -j isn't so bad after all...

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:30:46 -04:00
Don Zickus 7f42c1d1c3 Combine duplicate configs across ark and fedora into common
Used redhat/configs/evaluate_configs -j and it made these changes.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:30:46 -04:00
Peter Robinson 0e9f56df7f common/ark: cleanup and unify the parport configs
Fedora already disables parport on non x86 platforms, ark disabled
it in aarch64/s390x by random explicit disabled. Cleanup and unify
this by disabling it in common/generic and just enabling it for x86
with a single common config as the outcome was the same everywhere.
This makes the config more explicit and easier to see what is
enabled/disabled where.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:45 -04:00
Jerry Snitselaar 6aab1a0481 iommu/vt-d: enable INTEL_IDXD_SVM for both fedora and rhel
It is already enabled for Fedora, so move to common/generic/x86.

Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
2021-08-30 14:30:45 -04:00
Jeremy Linton 22965a73f0 REDHAT: coresight: etm4x: Disable coresight on HPE Apollo 70
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1918888

The coresight tables on the latest Apollo 70, appear to be
damaged sufficiently to throw a few hundred lines of back-traces
during boot, lets disable it until we can get a firmware fix.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
cc: Peter Robinson <pbrobinson@redhat.com>
cc: Justin M. Forbes <jforbes@fedoraproject.org>
cc: Al Stone <ahs3@redhat.com>
2021-08-30 14:30:45 -04:00
CKI@GitLab 9bbea6d1cf [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM64_BTI:

 Branch Target Identification (part of the ARMv8.5 Extensions)
 provides a mechanism to limit the set of locations to which computed
 branch instructions such as BR or BLR can jump.

 To make use of BTI on CPUs that support it, say Y.

 BTI is intended to provide complementary protection to other control
 flow integrity protection mechanisms, such as the Pointer
 authentication mechanism provided as part of the ARMv8.3 Extensions.
 For this reason, it does not make sense to enable this option without
 also enabling support for pointer authentication.  Thus, when
 enabling this option you should also select ARM64_PTR_AUTH=y.

 Userspace binaries must also be specifically compiled to make use of
 this mechanism.  If you say N here or the hardware does not support
 BTI, such binaries can still run, but you get no additional
 enforcement of branch destinations.

 Symbol: ARM64_BTI [=y]
 Type  : bool
 Defined at arch/arm64/Kconfig:1594
   Prompt: Branch Target Identification support
   Location:
     -> Kernel Features
       -> ARMv8.5 architectural features

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 14:30:45 -04:00
Fedora Kernel Team 4ee2b2058b [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SURFACE_HOTPLUG:

 Driver for out-of-band hot-plug event signaling on Microsoft Surface
 devices with hot-pluggable PCIe cards.

 This driver is used on Surface Book (2 and 3) devices with a
 hot-pluggable discrete GPU (dGPU). When not in use, the dGPU on those
 devices can enter D3cold, which prevents in-band (standard) PCIe
 hot-plug signaling. Thus, without this driver, detaching the base
 containing the dGPU will not correctly update the state of the
 corresponding PCIe device if it is in D3cold. This driver adds support
 for out-of-band hot-plug notifications, ensuring that the device state
 is properly updated even when the device in question is in D3cold.

 Select M or Y here, if you want to (fully) support hot-plugging of
 dGPU devices on the Surface Book 2 and/or 3 during D3cold.

 Symbol: SURFACE_HOTPLUG [=n]
 Type  : tristate
 Defined at drivers/platform/surface/Kconfig:89
   Prompt: Surface Hot-Plug Driver
   Depends on: SURFACE_PLATFORMS [=y] && GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y])

---

 CONFIG_X86_PLATFORM_DRIVERS_DELL:

 Say Y here to get to see options for device drivers for various
 Dell x86 platforms, including vendor-specific laptop extension drivers.
 This option alone does not add any kernel code.

 If you say N, all options in this submenu will be skipped and disabled.

 Symbol: X86_PLATFORM_DRIVERS_DELL [=n]
 Type  : bool
 Defined at drivers/platform/x86/dell/Kconfig:6
   Prompt: Dell X86 Platform Specific Device Drivers
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---

Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:45 -04:00
Rafael Aquini 1f3981d825 configs/common/generic: disable CONFIG_SLAB_MERGE_DEFAULT
This is desired to reduce the risk of kernel heap overflows
being able to overwrite objects from merged caches, and it
changes the requirements for cache layout control, increasing
the difficulty of these attacks.

It also in increases the reliability and protection against
object data corruption due to use-after-free and double-free
class of bugs, as by keeping caches unmerged, these kinds of
issues can only damage objects in the same cache.

CONFIG_SLAB_MERGE_DEFAULT=n has been the default setting
since RHEL-8

Signed-off-by: Rafael Aquini <aquini@redhat.com>
2021-08-30 14:30:45 -04:00
Justin M. Forbes 6995d3ec7c Remove _legacy_common_support
An rpm define _legacy_common_support was added to as a short term
workaround for gcc10 issues with upstream projects. As upstream is now
fixed for gcc10, this is no longer required.  This has been tested with
scratch builds against gcc10 in F33 and gcc11 in rawhide.

Resolves kernel-ark issue 21.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:45 -04:00
Fedora Kernel Team 71d9236eea [redhat] New configs in arch/powerpc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PPC_RTAS_FILTER:

 The RTAS syscall API has security issues that could be used to
 compromise system integrity. This option enforces restrictions on the
 RTAS calls and arguments passed by userspace programs to mitigate
 these issues.

 Say Y unless you know what you are doing and the filter is causing
 problems for you.

 Symbol: PPC_RTAS_FILTER [=y]
 Type  : bool
 Defined at arch/powerpc/Kconfig:991
   Prompt: Enable filtering of RTAS syscalls
   Depends on: PPC_RTAS [=y]
   Location:
     -> Kernel options

---

Cc: kernel-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:44 -04:00
Fedora Kernel Team e4eb6849c7 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NVIDIA_CARMEL_CNP_ERRATUM:

 If CNP is enabled on Carmel cores, non-sharable TLBIs on a core will not
 invalidate shared TLB entries installed by a different core, as it would
 on standard ARM cores.

 If unsure, say Y.

 Symbol: NVIDIA_CARMEL_CNP_ERRATUM [=y]
 Type  : bool
 Defined at arch/arm64/Kconfig:813
   Prompt: NVIDIA Carmel CNP: CNP on Carmel semantically different than ARM cores
   Location:
     -> Kernel Features
       -> ARM errata workarounds via the alternatives framework

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:44 -04:00
Fedora Kernel Team 1016973344 [redhat] New configs in fs/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TMPFS_INODE64:

 tmpfs has historically used only inode numbers as wide as an unsigned
 int. In some cases this can cause wraparound, potentially resulting
 in multiple files with the same inode number on a single device. This
 option makes tmpfs use the full width of ino_t by default, without
 needing to specify the inode64 option when mounting.

 But if a long-lived tmpfs is to be accessed by 32-bit applications so
 ancient that opening a file larger than 2GiB fails with EINVAL, then
 the INODE64 config option and inode64 mount option risk operations
 failing with EOVERFLOW once 33-bit inode numbers are reached.

 To override this configured default, use the inode32 or inode64
 option when mounting.

 If unsure, say N.

 Symbol: TMPFS_INODE64 [=n]
 Type  : bool
 Defined at fs/Kconfig:204
   Prompt: Use 64-bit ino_t by default in tmpfs
   Depends on: TMPFS [=y] && 64BIT [=y]
   Location:
     -> File systems
       -> Pseudo filesystems
         -> Tmpfs virtual memory file system support (former shm fs) (TMPFS [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:44 -04:00
Hans de Goede f2bd10ea43 redhat/mod-blacklist.sh: Fix floppy blacklisting
The modules in the kernel-modules-extra sub-packages are no longer
added to a separate /lib/modules/$(uname -r)/extra dir, instead
they are now installed in the standard /lib/modules/$(uname -r)/kernel
dir.

Adjust the floppy module blacklisting in mod-blacklist.sh accordingly
fixing the floppy module no longer being blacklisted by default.

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1789155
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 14:30:44 -04:00
Fedora Kernel Team 69fa700ecc [redhat] New configs in lib/Kconfig.kgdb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KGDB_HONOUR_BLOCKLIST:

 If set to Y the debug core will use the kprobe blocklist to
 identify symbols where it is unsafe to set breakpoints.
 In particular this disallows instrumentation of functions
 called during debug trap handling and thus makes it very
 difficult to inadvertently provoke recursive trap handling.

 If unsure, say Y.

 Symbol: KGDB_HONOUR_BLOCKLIST [=y]
 Type  : bool
 Defined at lib/Kconfig.kgdb:27
   Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints
   Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y]
   Location:
     -> Kernel hacking
       -> Generic Kernel Debugging Instruments
         -> KGDB: kernel debugger (KGDB [=y])
 Selects: KPROBES [=y]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:44 -04:00
Fedora Kernel Team f5f750eec6 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FAULT_INJECTION_USERCOPY:

 Provides fault-injection capability to inject failures
 in usercopy functions (copy_from_user(), get_user(), ...).

 Symbol: FAULT_INJECTION_USERCOPY [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:1771
   Prompt: Fault injection capability for usercopy functions
   Depends on: FAULT_INJECTION [=y]
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Fault-injection framework (FAULT_INJECTION [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:44 -04:00
Patrick Talbert 388b46f27f [redhat] configs: Enable CONFIG_DEBUG_IRQFLAGS for debug builds.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:44 -04:00
Fedora Kernel Team c589775b48 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEBUG_IRQFLAGS:

 Enables checks for potentially unsafe enabling or disabling of
 interrupts, such as calling raw_local_irq_restore() when interrupts
 are enabled.

 Symbol: DEBUG_IRQFLAGS [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:1427
   Prompt: Debug IRQ flag manipulation
   Location:
     -> Kernel hacking
 Selected by [n]:
   - DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:43 -04:00
Fedora Kernel Team a76d28b52b [redhat] AUTOMATIC: New configs 2021-08-30 14:30:43 -04:00
Fedora Kernel Team 042978f305 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:43 -04:00
Fedora Kernel Team c20b2447c9 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:43 -04:00
CKI@GitLab 229a9cdf1f New configs in fs/pstore
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PSTORE_BLK:

 This enables panic and oops message to be logged to a block dev
 where it can be read back at some later point.

 For more information, see Documentation/admin-guide/pstore-blk.rst

 If unsure, say N.

 Symbol: PSTORE_BLK [=n]
 Type  : tristate
 Defined at fs/pstore/Kconfig:164
   Prompt: Log panic/oops to a block device
   Depends on: MISC_FILESYSTEMS [=y] && PSTORE [=y] && BLOCK [=y]
   Location:
     -> File systems
       -> Miscellaneous filesystems (MISC_FILESYSTEMS [=y])
         -> Persistent store support (PSTORE [=y])
 Selects: PSTORE_ZONE [=n]

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
2021-08-30 14:30:43 -04:00
Fedora Kernel Team b63a0bda75 New configs in arch/powerpc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PPC_PROT_SAO_LPAR:

 This option adds support for PROT_SAO mappings from userspace
 inside LPARs on supported CPUs.

 This may cause issues when performing guest migration from
 a CPU that supports SAO to one that does not.

 If unsure, say N here.

 Symbol: PPC_PROT_SAO_LPAR [=n]
 Type  : bool
 Defined at arch/powerpc/Kconfig:863
   Prompt: Support PROT_SAO mappings in LPARs
   Depends on: PPC_BOOK3S_64 [=y]
   Location:
     -> Kernel options

Cc: kernel-patches@redhat.com
2021-08-30 14:30:43 -04:00
Ondrej Mosnacek 50a0985856 configs: enable BPF LSM on Fedora and ARK
We are going to want to enable BPF LSM in RHEL, so start building it on
ARK and update the default LSM list so that it is enabled on boot by
default (to enable testing). It should have almost no performance impact
unless userspace attaches some BPF programs to the hooks. Users can
still completely turn it off by adding lsm="yama,integrity,selinux" to
the kernel command line.

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 14:30:43 -04:00
Ondrej Mosnacek a7fc6954d7 configs: clean up LSM configs
1. Set CONFIG_SECURITY_LOCKDOWN_LSM=y on both Fedora and ARK and move
   the associated configs from fedora/ to common/. On both this is
   required for proper UEFI secure boot support.
2. Remove ark/generic/CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE - this
   config has been removed upstream.
3. Deduplicate default value of CONFIG_LSM_MMAP_MIN_ADDR - set it to
   65536 under common/ and only override it in
   fedora/generic/arm/armv7/.
4. Trim LSMs that are not build-enabled from CONFIG_LSM on Fedora/ARK,
   which can now be unified under common/.

Note that this commit adds the Lockdown LSM to the default LSM list and
therefore effectively enables it on both Fedora (where it was enabled in
build, but disabled on boot) and ARK (where it wasn't even enabled at
build). According to Peter Robinson and Al Stone it should be enabled,
so hopefully this is the expected result.

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 14:30:42 -04:00
Vladis Dronov bcabdf3b18 [redhat] Unify crypto CHACHA20 and POLY1305 configs
Currently CRYPTO_CHACHA20* and CRYPTO_*POLY1305* configs are not in order.
Unify them by merging and moving to configs/common/. Also enable CRYPTO_
CHACHA20POLY1305 on PowerPC as it was done in rhbz#1734711.

Detailed actions taken:

Move:
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=y
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=y
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=y
to
configs/common/generic/s390x/zfcpdump/

Delete (per rhbz#1734711):
configs/ark/generic/powerpc/CONFIG_CRYPTO_CHACHA20POLY1305:# CONFIG_CRYPTO_CHACHA20POLY1305 is not set

Delete: configs/pending-common/generic/CONFIG_CRYPTO_POLY1305_NEON:# CONFIG_CRYPTO_POLY1305_NEON is not set
And move:
configs/fedora/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON:CONFIG_CRYPTO_POLY1305_NEON=m
to:
configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON

Merge:
       configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
configs/fedora/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
to:
configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON

Merge:
       configs/ark/generic/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
configs/fedora/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
to:
configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON

Merge:
       configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
to (depends on X86 && 64BIT):
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2

Merge:
       configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
to (depends on X86 && 64BIT):
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2

The result:

$ git grep -e CRYPTO_CHACHA20 -e CRYPTO_POLY1305 -e CRYPTO_NHPOLY1305
configs/common/generic/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=m
configs/common/generic/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=m
configs/common/generic/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=m
configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON:CONFIG_CRYPTO_POLY1305_NEON=m
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=y
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=y
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=y
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_CHACHA20_X86_64:CONFIG_CRYPTO_CHACHA20_X86_64=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_POLY1305_X86_64:CONFIG_CRYPTO_POLY1305_X86_64=m
configs/fedora/generic/arm/armv7/CONFIG_CRYPTO_POLY1305_ARM:CONFIG_CRYPTO_POLY1305_ARM=m

Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:30:42 -04:00
Fedora Kernel Team ef0b6eb830 [redhat] New configs in fs/xfs
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_XFS_SUPPORT_V4:

 The V4 filesystem format lacks certain features that are supported
 by the V5 format, such as metadata checksumming, strengthened
 metadata verification, and the ability to store timestamps past the
 year 2038.  Because of this, the V4 format is deprecated.  All users
 should upgrade by backing up their files, reformatting, and restoring
 from the backup.

 Administrators and users can detect a V4 filesystem by running
 xfs_info against a filesystem mountpoint and checking for a string
 beginning with "crc=".  If the string "crc=0" is found, the
 filesystem is a V4 filesystem.  If no such string is found, please
 upgrade xfsprogs to the latest version and try again.

 This option will become default N in September 2025.  Support for the
 V4 format will be removed entirely in September 2030.  Distributors
 can say N here to withdraw support earlier.

 To continue supporting the old V4 format (crc=0), say Y.
 To close off an attack surface, say N.

 Symbol: XFS_SUPPORT_V4 [=y]
 Type  : bool
 Defined at fs/xfs/Kconfig:25
   Prompt: Support deprecated V4 (crc=0) format
   Depends on: BLOCK [=y] && XFS_FS [=m]
   Location:
     -> File systems
       -> XFS filesystem support (XFS_FS [=m])

---

Cc: Brian Foster <bfoster@redhat.com>
Cc: Carlos Maiolino <cmaiolin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:42 -04:00
CKI@GitLab 4c54a5a58d New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INTEL_SCU_PCI:

 This driver is used to bridge the communications between kernel
 and SCU on some embedded Intel x86 platforms. It also creates
 devices that are connected to the SoC through the SCU.
 Platforms supported:
   Medfield
   Clovertrail
   Merrifield
   Broxton
   Apollo Lake

 Symbol: INTEL_SCU_PCI [=n]
 Type  : bool
 Defined at drivers/platform/x86/Kconfig:1354
   Prompt: Intel SCU PCI driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
 Selects: INTEL_SCU [=n]
 Selected by [n]:
   - X86_INTEL_MID [=n] && X86_EXTENDED_PLATFORM [=y] && X86_PLATFORM_DEVICES [=y] && PCI [=y] && (X86_64 [=y] || PCI_GOANY [=n] && X86_32 [=n]) && X86_IO_APIC [=y]

Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
2021-08-30 14:30:42 -04:00
CKI@GitLab 4191024a5a New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER:

 Select this config option to add support for the initrd= command
 line parameter, allowing an initrd that resides on the same volume
 as the kernel image to be loaded into memory.

 This method is deprecated.

 Symbol: EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER [=y]
 Type  : bool
 Defined at drivers/firmware/efi/Kconfig:127
   Prompt: Enable the command line initrd loader
   Depends on: EFI [=y] && EFI_STUB [=y] && (EFI_GENERIC_STUB [=y] || X86)
   Visible if: EFI [=y] && EFI_STUB [=y] && (EFI_GENERIC_STUB [=y] || X86) && !X86
   Location:
     -> Firmware Drivers
       -> EFI (Extensible Firmware Interface) Support

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
2021-08-30 14:30:42 -04:00
Jeremy Cline 282a3060a8 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_SOC_INTEL_CATPT:

 Enable support for Intel(R) Haswell and Broadwell platforms
 with I2S codec present. This is a recommended option.
 Say Y or m if you have such device.
 If unsure, say N.

 Symbol: SND_SOC_INTEL_CATPT [=n]
 Type  : tristate
 Defined at sound/soc/intel/Kconfig:37
   Prompt: Haswell and Broadwell
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && DMADEVICES [=y] && SND_DMA_SGBUF [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Intel ASoC SST drivers (SND_SOC_INTEL_SST_TOPLEVEL [=y])
 Selects: DW_DMAC_CORE [=y] && SND_SOC_ACPI_INTEL_MATCH [=m]
 Selected by [n]:
   - SND_SOC_INTEL_HASWELL [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:41 -04:00
Fedora Kernel Team 3da50c0c31 [redhat] New configs in drivers/scsi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE:

 Set Y to default enable DEBUGFS for SCSI_HISI_SAS

 Symbol: SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE [=n]
 Type  : bool
 Defined at drivers/scsi/hisi_sas/Kconfig:22
   Prompt: HiSilicon SAS debugging default enable
   Depends on: SCSI_LOWLEVEL [=y] && SCSI [=y] && SCSI_HISI_SAS [=m]
   Location:
     -> Device Drivers
       -> SCSI device support
         -> SCSI low-level drivers (SCSI_LOWLEVEL [=y])
           -> HiSilicon SAS (SCSI_HISI_SAS [=m])

---

Cc: "Ewan D. Milne" <emilne@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:41 -04:00
Fedora Kernel Team d2565aa036 [redhat] New configs in drivers/tty
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SERIAL_BCM63XX:

 This enables the driver for the onchip UART core found on
 the following chipsets:

   BCM33xx (cable modem)
   BCM63xx/BCM63xxx (DSL)
   BCM68xx (PON)
   BCM7xxx (STB) - DOCSIS console

 Symbol: SERIAL_BCM63XX [=n]
 Type  : tristate
 Defined at drivers/tty/serial/Kconfig:1117
   Prompt: Broadcom BCM63xx/BCM33xx UART support
   Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Enable TTY (TTY [=y])
           -> Serial drivers
 Selects: SERIAL_CORE [=y]

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:41 -04:00
Ben Crocker 7cb5549953 [redhat] Makefile: dist-dump-variables
Add Makefile, Makefile.rhelver to file(s) searched for
assignment patterns.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:41 -04:00
CKI Gitlab 86faf9e869 [redhat] New configs in drivers/perf
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_DMC620_PMU:

 Support for PMU events monitoring on the ARM DMC-620 memory
 controller.

 Symbol: ARM_DMC620_PMU [=n]
 Type  : tristate
 Defined at drivers/perf/Kconfig:133
   Prompt: Enable PMU support for the ARM DMC-620 memory controller
   Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Performance monitor support

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:41 -04:00
Fedora Kernel Team 884b9fa7a1 New configs in drivers/mailbox
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_QCOM_IPCC:

 Qualcomm Technologies, Inc. Inter-Processor Communication Controller
 (IPCC) driver for MSM devices. The driver provides mailbox support for
 sending interrupts to the clients. On the other hand, the driver also
 acts as an interrupt controller for receiving interrupts from clients.
 Say Y here if you want to build this driver.

 Symbol: QCOM_IPCC [=n]
 Type  : bool
 Defined at drivers/mailbox/Kconfig:247
   Prompt: Qualcomm Technologies, Inc. IPCC driver
   Depends on: MAILBOX [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Mailbox Hardware Support (MAILBOX [=y])

Cc: Al Stone <ahs3@redhat.com>
2021-08-30 14:30:41 -04:00
Justin M. Forbes 9e18f78bcc New configs in drivers/net/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BCM54140_PHY:

 Support the Broadcom BCM54140 Quad SGMII/QSGMII PHY.

 This driver also supports the hardware monitoring of this PHY and
 exposes voltage and temperature sensors.

 Symbol: BCM54140_PHY [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:357
   Prompt: Broadcom BCM54140 PHY
   Depends on: NETDEVICES [=y] && PHYLIB [=y] && (HWMON [=y] || HWMON [=y]=n)
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])
 Selects: BCM_NET_PHYLIB [=m]

Cc: Petr Oros <poros@redhat.com>
2021-08-30 14:30:41 -04:00
Fedora Kernel Team 046ed6c366 [redhat] New configs in mm/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_GUP_TEST:

 Provides /sys/kernel/debug/gup_test, which in turn provides a way
 to make ioctl calls that can launch kernel-based unit tests for
 the get_user_pages*() and pin_user_pages*() family of API calls.

 These tests include benchmark testing of the _fast variants of
 get_user_pages*() and pin_user_pages*(), as well as smoke tests of
 the non-_fast variants.

 There is also a sub-test that allows running dump_page() on any
 of up to eight pages (selected by command line args) within the
 range of user-space addresses. These pages are either pinned via
 pin_user_pages*(), or pinned via get_user_pages*(), as specified
 by other command line arguments.

 See tools/testing/selftests/vm/gup_test.c

 Symbol: GUP_TEST [=n]
 Type  : bool
 Defined at mm/Kconfig:824
   Prompt: Enable infrastructure for get_user_pages()-related unit tests
   Depends on: DEBUG_FS [=y]
   Location:
     -> Memory Management options

---

Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:40 -04:00
Vladis Dronov 46f5e30259 [redhat] Enable PERCPU_STATS and CRYPTO_DEV_CCP_DEBUGFS in the debug flavor
The same way in was done in the rhbz#1744633 and rhbz#bz1765717.

Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:30:40 -04:00
Augusto Caringi fd4b1579f2 Update CONFIG_DM_MULTIPATH_IOA 2021-08-30 14:30:40 -04:00
Fedora Kernel Team 70ec93889a [redhat] New configs in drivers/md
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DM_MULTIPATH_IOA:

 This path selector selects the path based on the CPU the IO is
 executed on and the CPU to path mapping setup at path addition time.

 If unsure, say N.

 Symbol: DM_MULTIPATH_IOA [=n]
 Type  : tristate
 Defined at drivers/md/Kconfig:466
   Prompt: I/O Path Selector based on CPU submission
   Depends on: MD [=y] && DM_MULTIPATH [=m]
   Location:
     -> Device Drivers
       -> Multiple devices driver support (RAID and LVM) (MD [=y])
         -> Device mapper support (BLK_DEV_DM [=m])
           -> Multipath target (DM_MULTIPATH [=m])

---

Cc: Nigel Croxon <ncroxon@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:40 -04:00
CKI@GitLab f8c5b02aaf New configs in mm/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ZSMALLOC_PGTABLE_MAPPING:

 By default, zsmalloc uses a copy-based object mapping method to
 access allocations that span two pages. However, if a particular
 architecture (ex, ARM) performs VM mapping faster than copying,
 then you should select this. This causes zsmalloc to use page table
 mapping rather than copying for object mapping.

 You can check speed with zsmalloc benchmark:
 https://github.com/spartacus06/zsmapbench

 Symbol: ZSMALLOC_PGTABLE_MAPPING [=n]
 Type  : bool
 Defined at mm/Kconfig:708
   Prompt: Use page table mapping to access object in zsmalloc
   Depends on: ZSMALLOC [=y]=y
   Location:
     -> Memory Management options
       -> Memory allocator for compressed pages (ZSMALLOC [=y])

Cc: Rafael Aquini <aquini@redhat.com>
2021-08-30 14:30:40 -04:00
Jeremy Cline 134196f19d New configs in arch/powerpc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PMU_SYSFS:

 This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*.

 Symbol: PMU_SYSFS [=n]
 Type  : bool
 Defined at arch/powerpc/platforms/Kconfig.cputype:428
   Prompt: Create PMU SPRs sysfs file
   Location:
     -> Processor support

Cc: kernel-patches@redhat.com
2021-08-30 14:30:40 -04:00
Jeremy Cline 27751ef8fc New configs in arch/powerpc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

CONFIG_COMPAT:

Enable support for 32bit binaries

Symbol: COMPAT [=n]
Type : bool
Defined at arch/powerpc/Kconfig:268
     Depends on: PPC64
  Default: y if !CPU_LITTLE_ENDIAN
  Selects: COMPAT_BINFMT_ELF
           ARCH_WANT_OLD_COMPAT_IPC
           COMPAT_OLD_SIGACTION

Cc: kernel-patches@redhat.com
2021-08-30 14:30:40 -04:00
Fedora Kernel Team 672f2723e7 New configs in drivers/input
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INPUT_IQS269A:

 Say Y to enable support for the Azoteq IQS269A capacitive
 touch controller.

 To compile this driver as a module, choose M here: the
 module will be called iqs269a.

 Symbol: INPUT_IQS269A [=n]
 Type  : tristate
 Defined at drivers/input/misc/Kconfig:721
   Prompt: Azoteq IQS269A capacitive touch controller
   Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Miscellaneous devices (INPUT_MISC [=y])
 Selects: REGMAP_I2C [=m]

Cc: Tony Camuso <tcamuso@redhat.com>
2021-08-30 14:30:39 -04:00
Justin M. Forbes e1873320df [redhat] New configs in drivers/net/ethernet/mellanox
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MLX5_CLS_ACT:

 mlx5 ConnectX offloads support for TC classifier action (NET_CLS_ACT),
 works in both native NIC mode and Switchdev SRIOV mode.
 Actions get attached to a Hardware offloaded classifiers and are
 invoked after a successful classification. Actions are used to
 overwrite the classification result, instantly drop or redirect and/or
 reformat packets in wire speeds without involving the host cpu.

 If set to N, TC offloads in both NIC and switchdev modes will be disabled.
 If unsure, set to Y

 Symbol: MLX5_CLS_ACT [=y]
 Type  : bool
 Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:81
   Prompt: MLX5 TC classifier action support
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_ESWITCH [=y] && NET_CLS_ACT [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
           -> Mellanox devices (NET_VENDOR_MELLANOX [=y])
             -> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y])
               -> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y])

---

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:39 -04:00
Justin M. Forbes 5cefa97ad9 New configs in net/bluetooth
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BT_MSFTEXT:

 This options enables support for the Microsoft defined HCI
 vendor extensions.

 Symbol: BT_MSFTEXT [=n]
 Type  : bool
 Defined at net/bluetooth/Kconfig:96
   Prompt: Enable Microsoft extensions
   Depends on: NET [=y] && BT [=m]
   Location:
     -> Networking support (NET [=y])
       -> Bluetooth subsystem support (BT [=m])

Cc: Gopal Tiwari <gtiwari@redhat.com>
2021-08-30 14:30:39 -04:00
Fedora Kernel Team 2346bbaa4f New configs in drivers/clk
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ICST:

 Supports clocking on ARM Reference designs:
 - Integrator/AP and Integrator/CP
 - RealView PB1176, EB, PB11MP and PBX

 Symbol: ICST [=n]
 Type  : bool
 Defined at drivers/clk/versatile/Kconfig:7
   Prompt: Clock driver for ARM Reference designs ICST
   Depends on: COMMON_CLK [=y] && (ARCH_INTEGRATOR || ARCH_REALVIEW || ARCH_VERSATILE || ARCH_VEXPRESS [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Common Clock Framework
         -> Clock driver for ARM Reference designs
 Selects: REGMAP_MMIO [=y]

Cc: Mark Salter <msalter@redhat.com>
2021-08-30 14:30:39 -04:00
Jeremy Cline a93a4a7621 New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_WATCH_QUEUE:

 This is a general notification queue for the kernel to pass events to
 userspace by splicing them into pipes.  It can be used in conjunction
 with watches for key/keyring change notifications and device
 notifications.

 See Documentation/watch_queue.rst

 Symbol: WATCH_QUEUE [=n]
 Type  : bool
 Defined at init/Kconfig:370
   Prompt: General notification queue
   Location:
     -> General setup

Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:39 -04:00
CKI Gitlab 1d5d5d5cee [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HARDLOCKUP_DETECTOR:

 Say Y here to enable the kernel to act as a watchdog to detect
 hard lockups.

 Hardlockups are bugs that cause the CPU to loop in kernel mode
 for more than 10 seconds, without letting other interrupts have a
 chance to run.  The current stack trace is displayed upon detection
 and the system will stay locked up.

 Symbol: HARDLOCKUP_DETECTOR [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:1000
   Prompt: Detect Hard Lockups
   Depends on: DEBUG_KERNEL [=y] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=y] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=n])
   Location:
     -> Kernel hacking
       -> Debug Oops, Lockups and Hangs
 Selects: LOCKUP_DETECTOR [=y] && HARDLOCKUP_DETECTOR_PERF [=n] && HARDLOCKUP_DETECTOR_ARCH

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:39 -04:00
Tom Stellard faf6b35d9a [redhat] spec: Add %bcond_with toolchain_clang option
This option can be enabled by passing --with toolchain_clang to rpmbuild
or mock.  Enabling this option will cause the kernel to be built with
clang instead of gcc.

Signed-off-by: Tom Stellard <tstellar@redhat.com>
2021-08-30 14:30:39 -04:00
Fedora Kernel Team b4d4e34b41 [redhat] New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_SC8180X:

 This is the pinctrl, pinmux, pinconf and gpiolib driver for the
 Qualcomm Technologies Inc TLMM block found on the Qualcomm
 Technologies Inc SC8180x platform.

 Symbol: PINCTRL_SC8180X [=n]
 Type  : tristate
 Defined at drivers/pinctrl/qcom/Kconfig:223
   Prompt: Qualcomm Technologies Inc SC8180x pin controller driver
   Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_MSM [=n]

---

 CONFIG_PINCTRL_SM8350:

 This is the pinctrl, pinmux, pinconf and gpiolib driver for the
 Qualcomm Technologies Inc TLMM block found on the Qualcomm
 Technologies Inc SM8350 platform.

 Symbol: PINCTRL_SM8350 [=n]
 Type  : tristate
 Defined at drivers/pinctrl/qcom/Kconfig:277
   Prompt: Qualcomm Technologies Inc SM8350 pin controller driver
   Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_MSM [=n]

---

Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:38 -04:00
Herton R. Krzesinski 8f87a0fc69 redhat: allow running fedora-configs and rh-configs targets outside of redhat/
Since the rename of all targets to dist-* targets, the specific config
target for RHEL configs do not work when called outside of the redhat directory:
the makefile filters only dist-% and distg-% targets, so it doesn't run against
redhat/Makefile and thus calling those targets do not work, unless you
cd into the redhat directory.

To allow running the specific config targets outside of redhat/
directory, we have two approaches: change makefile to accept those old
config targets, or create new ones starting with dist-*.

I chose the latter approach with this change: fedora-configs target
has a new dist-fedora-configs, while rh-configs target can now be
called as dist-rhel-configs. I also removed the old targets from the
help output replacing them in favour of the new ones.

v2: keep rh-configs and fedora-configs targets for compatibility, which
now calls the new dist-* ones.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:38 -04:00
Peter Robinson 6644b3084d all: unify the disable of goldfish (android emulation platform)
Disable Goldfish everywhere, it's an android emulation platform.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:38 -04:00
Peter Robinson dd77610786 common: minor cleanup/de-dupe of dma/dmabuf debug configs
Minor cleanup of dma/dmabuf settings.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:38 -04:00
Peter Robinson 9e331bcb6e common/ark: these drivers/arches were removed in 5.12
These were removed in the 5.12 merge window so are now dead options
so they can be cleaned up.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:38 -04:00
Paulo E. Castro 2fbd6593cc Correct kernel-devel make prepare build for 5.12.
Add requirements without which `prepare` won't work.
2021-08-30 14:30:38 -04:00
Herton R. Krzesinski 50fa44af1c redhat: add initial support for centos stream dist-git sync on Makefiles
This change introduces some initial centos stream support, mainly what's
needed for a dist-git sync. The dist-git sync is initially proposed to
be a fork + merge request model, and thus we need some changes for the
Makefiles. I also dropped IS_FEDORA variable, and replace it with
DISTRO, which can have either "fedora" or "centos" (and could be set
later to "rhel" or anything else if needed through the code).

While at it, I also fixed the default RHPKG_BIN to rhpkg instead of
rhpkg-sha512 in the default RHEL case, the former was a wrapper for
the sha512 transition on dist-git at RHEL 8 time and is not needed
anymore, it is now deprecated and will be removed from rhpkg.

Example of a dist-git sync with new centos dist-git:
make DIST=".el9" GL_DISTGIT_USER=<gitlab user> BUILDID="" RHDISTGIT_BRANCH=c9s dist-git

v2: use PACKAGE_NAME in Makefile.rhpkg as suggested by Jan Stancek
v3: make the default DISTRO rhel in case DIST is not fc*, to not break
    folks building kernel-ark on rhel which are used to not have to
    specify an extra variable, as reported by Don Zickus

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:38 -04:00
Josh Poimboeuf 733c7bb17b redhat/configs: Enable CONFIG_SCHED_STACK_END_CHECK for Fedora and ARK
CONFIG_SCHED_STACK_END_CHECK checks for stack overrun in calls to
schedule().  In internal testing, it had no measurable performance
impact.

Enable it for Fedora and ARK.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856174
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
2021-08-30 14:30:37 -04:00
Justin M. Forbes fca5f3d840 CONFIG_VFIO now selects IOMMU_API instead of depending on it, causing several config mismatches for the zfcpdump kernel
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:37 -04:00
Justin M. Forbes f445d41680 Turn off weak-modules for Fedora
This has been turned off for Fedora stable releases for quite some time
now, but still causes issues for rawhide and test release users.  Fedora
does not support CONFIG_MODVERSIONS or KABI, so the weak-modules script
offers no value, but does consume a large amount of CPU on major version
updates.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:37 -04:00
Prarit Bhargava fae4f69c53 RHMAINTAINERS: update for March 15 2021
Update RHMAINTAINERS.

v2: Update jforbes address

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:37 -04:00
Herton R. Krzesinski f8efdc5177 redhat: enable CONFIG_FW_LOADER_COMPRESS for ARK
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1939095

The CONFIG_FW_LOADER_COMPRESS have been kept enabled only for Fedora.
However in RHEL 9, we inherit the linux-firmware as is from Fedora, and
it installs firmware files compressed in .xz format for RHEL too.
However, the ARK/rhel config does not enable the needed support for
loading compressed firmware files, and thus firmware loading fails.

This fixes that by also enabling CONFIG_FW_LOADER_COMPRESS on ARK/rhel
config too (since ARK and Fedora have the same setting now, the config
file is moved to common/).

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:37 -04:00
Peter Robinson c776b79a46 Fedora: filters: update to move dfl-emif to modules
The dfl-emif module is part of the FPGA functionality which all resides
in the modules sub-package so filter this through to there too.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:37 -04:00
Peter Robinson 71a1270a1a drop duplicate DEVFREQ_GOV_SIMPLE_ONDEMAND config
We had to temporarily build in DEVFREQ_GOV_SIMPLE_ONDEMAND on ARMv7 but
we fixed that so this is now a dupe and can be dropped.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:37 -04:00
Fedora Kernel Team 66f12d910a [redhat] New configs in drivers/input
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MOUSE_SERIAL:

 Say Y here if you have a serial (RS-232, COM port) mouse connected
 to your system. This includes Sun, MouseSystems, Microsoft,
 Logitech and all other compatible serial mice.

 If unsure, say N.

 To compile this driver as a module, choose M here: the
 module will be called sermouse.

 Symbol: MOUSE_SERIAL [=n]
 Type  : tristate
 Defined at drivers/input/mouse/Kconfig:203
   Prompt: Serial mouse
   Depends on: !UML && INPUT [=y] && INPUT_MOUSE [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Mice (INPUT_MOUSE [=y])
 Selects: SERIO [=y]

---

Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:37 -04:00
Patrick Talbert aa64fbeceb [redhat] Set CONFIG_MOUSE_SERIAL=n by default
Since !777 CONFIG_MOUSE_SERIAL is only enabled for x86. That's fine, but
the config item does not declare a default so we must unset it for the
default case.

Cc: Peter Robinson <pbrobinson@gmail.com>
Cc: Dan Horák <dan@danny.cz>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:36 -04:00
Jeremy Linton 9e5f87b5d6 [redhat] arm: unify EFI vars
EFI is enabled on arm platforms, lets unify the config
options.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>

ptalbert@redhat.com: removed CONFIG_EFI_VARS due to !825.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:36 -04:00
Jeremy Linton 93f39e2827 [redhat] arm: Unify CPU_THERMAL
CPU_THERMAL is enabled on all builds, put
it in the right spot.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:36 -04:00
Jeremy Linton 9e52399557 [redhat] arm: move SPE to generic
Statistical profiling is a feature of recent arm cores
lets move the driver to the common directories.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:36 -04:00
Jeremy Linton cbbe09d749 [redhat] aarch64: sync and enable some arm interconnect PMUs
Lets assure that we are enabling PMUs for basic ARM
interconnects.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:36 -04:00
Jeremy Linton 46e1c90124 [redhat] arm: move psci checker disable to common
PSCI_CHECKER is disabled everywhere lets make it common.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:36 -04:00
Jeremy Linton 4a36a5c226 [redhat] aarch64: SW_TTBR_PAN globally on
The SW_TTBR_PAN is a security feature that should
be enabled on both fedora & ark.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:35 -04:00
Jeremy Linton 6d157f8a8c [redhat] aarch64: Move arm64_tlb_range to common
The tlb range options should be combined for all arm kernels.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:35 -04:00
Jeremy Linton fd335fa235 [redhat] aarch64: Enable hotplug memory
The hotplug mem option is used to enable a number of other
kernel features and should be enabled for ark.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:35 -04:00
Jeremy Linton 01234d8d85 [redhat] aarch64: ACPI/CPPC can be a module
ACPI/CPPC works just fine as a module, lets sync
the fedora/ark config.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:35 -04:00
Jeremy Linton 55cf5ce721 [redhat] aarch64: Support coresight as a generic option
The coresight debug and trace facitlity should be built
as modules on all ark/fedora/etc kernels.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:30:35 -04:00
Prarit Bhargava 36726cc3c8 RHMAINTAINERS: Update for March 1 2021
Update to latest version, reorganize sections, and remove
kernel-patches@redhat.com email list.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>

---
v2: Fix jforbes' email address
2021-08-30 14:30:34 -04:00
Peter Robinson 2cdacbf488 efi: The EFI_VARS is legacy and now x86 only
As of upstream commit 963fabf the EFI_VARS option is set to x86
only as it's long been deprecated pre !intel support and is due to
be removed so it now does nothing on arm platforms.

Fedora actually disabled this on x86 too, I do wonder if it's
worth considering disabling it in ark platforms too?

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
2021-08-30 14:30:34 -04:00
Peter Robinson 992011c40e common: enable RTC_SYSTOHC to supplement update_persistent_clock64
We already enable RTC_HCTOSYS in common config, this is the inverse
for syncing NTP to HW RTCs, and seems slightly better/preferred on
non x86-style CMOS RTCa than update_persistent_clock.

Set the device to rtc0, the same as we set RTC_HCTOSYS to.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:34 -04:00
Peter Robinson 735e3ce1d2 generic: arm: enable SCMI for all options
The Arm System Control and Management Interface (SCMI) specification is
a new standard firmware interface for Arm devices from Arm.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Cc: ahs3@redhat.com
Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
2021-08-30 14:30:34 -04:00
Peter Robinson 145548064c fedora: the PCH_CAN driver is x86-32 only
No functional change

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:34 -04:00
Peter Robinson e5ec68e83f common: disable legacy CAN device support
The Bosch C_CAN stopped shipping in 2006, it's successor D_CAN also
supported by the same driver it seems around 2010, the CC770 is also
based on the original C_CAN, and the SJA1000 is of similar vintage.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:34 -04:00
Peter Robinson 0e1d42d9d8 common: Enable Microchip MCP251x/MCP251xFD CAN controllers
The Microchip MCP251x/MCP251xFD CAN controllers are widely deployed
across IoT/Edge devices such as the Compulabs Fitlet2 (RHEL for Edge)
and are often attached in host systems via FTDI serial interfaces.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:33 -04:00
Peter Robinson e1624f9ed4 common: Bosch MCAN support for Intel Elkhart Lake
The Intel IoT/Edge Elkhart Lake SoC has onboard Bosch MCAN controller IP.
This is scheduled to be a supported RHEL for Edge platform so we want
MCAN support.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:33 -04:00
Peter Robinson 133ea9b1e9 common: enable CAN_PEAK_PCIEFD PCI-E driver
The CAN_PEAK_PCIEFD is a PEAK-System PCAN-PCIe FD cards driver
and the one that should have been eabled instead of CAN_PEAK_PCIEC.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:33 -04:00
Peter Robinson 04135854be common: disable CAN_PEAK_PCIEC PCAN-ExpressCard
The CAN_PEAK_PCIEC option is a PEAK PCAN-ExpressCard Card and not
something we support.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:33 -04:00
Peter Robinson c7ed620c53 common: enable common CAN layer 2 protocols
Enable vxcan (for virtual can tunneling), ISO 15765-2:2016 CAN transport protocol
(for londer datagram protocols needed for certain L3 protocols such as
IP-over-CAN traffic) and SAE J1939 (for j1939 socket type used by datalink &
transport protocol as well as management).

These are all common protocols needed for modern CAN deployments.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:33 -04:00
Peter Robinson 486a4545ab ark: disable CAN_LEDS option
The CONFIG_CAN_LEDS is marked as broken in the kernel, we don't
want to enable it for general CAN use cases anyway.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:33 -04:00
Hans de Goede 4d9f625f73 Fedora: Turn on SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC option
This is necessary to get sound working on some Skylake based laptops.

BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1933423
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 14:30:33 -04:00
Dave Olsthoorn 1df7fde685 Fedora: enable modules for surface devices
This enables new kernel modules for Microsofts Surface line of devices

Signed-off-by: Dave Olsthoorn <dave@bewaar.me>
2021-08-30 14:30:32 -04:00
Justin M. Forbes 2ab523dcf4 Turn on SND_SOC_INTEL_SOUNDWIRE_SOF_MACH for Fedora again
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:32 -04:00
Peter Robinson 1bb6ad8fd5 common: fix WM8804 codec dependencies
The WM8804 codec is required for Intel Apollo Lake support so enable it as it's a supported RHEL for Edge platform.

Some minor cleanups for the WM8804 codec configs while we're at it.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:32 -04:00
Fedora Kernel Team 5c7d8de540 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:32 -04:00
Fedora Kernel Team ccafff1654 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:32 -04:00
Peter Robinson 6a46202064 Build SERIO_SERPORT as a module
In all kernels it's only used by some USB CEC drivers so it no
longer needs to be built in.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:32 -04:00
Peter Robinson f12cea2aae input: touchscreen: move ELO and Wacom serial touchscreens to x86
The following EL0, Point of Sale and related, and Wacom touchscreens
are serial based touch screens and are only really used on x86 systems.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:32 -04:00
Peter Robinson bfeee2888a Sync serio touchscreens for non x86 architectures to the same as ARK
The serio touchscreens in Fedora aren't used out side of x86 so move the ark
configs to generic and the Fedora configs to fedora/x86. No change on ARK kernels.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:32 -04:00
Peter Robinson e98099614a Only enable SERIO_LIBPS2 on x86
The LIBPS2 is only used by the PS2 mice and AT keyboard drivers
which are now only enabled on x86

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:31 -04:00
Peter Robinson 9096e47e7d Only enable PC keyboard controller and associated keyboard on x86
THe i8042 PC Keyboard controller and AT keyboard are x86 only so
only enable them on that architecture.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:31 -04:00
Peter Robinson 20dce21dc6 Generic: Mouse: Tweak generic serial mouse options
Disable the ancient DEC VSXXXAA mouse, needs a special adapter to be
used over RS-232, only enable RS-232 mice on x86.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:31 -04:00
Peter Robinson 5f4d43fc23 Only enable PS2 Mouse options on x86
PS2 mice aren't supported on all current architectures other than x86
so move the generic option to x86 and the ark aarch64 options that
disabled them to generic so it applies to all non x86 architectures.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:31 -04:00
Peter Robinson 498199297d Disable bluetooth highspeed by default
Upstream has disabled BT_HS by disabled because it wasn't widely adopted.
It's also been referenced upstream by BleedingTooth vulnerability:
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00435.html

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:30:31 -04:00
Peter Robinson b5b6927794 Fedora: A few more general updates for 5.12 window
A number of general and arm updates from the pending-fedora

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:31 -04:00
Peter Robinson a4f9ca00da Fedora: Updates for 5.12 merge window
Mostly arm related updates but there's a few minor x86 and generic
bits, plus a few minor debug/prod dmabuf updates.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:30 -04:00
Peter Robinson 6a76c46d05 Fedora: remove dead options that were removed upstream
All these options are now non-existent upstream so just drop
them as they're ghost options.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:30 -04:00
Vladis Dronov 76d42e8ded [redhat] Make CONFIG_CRYPTO_DEV_QAT_* configs x86-only and unify them
Intel has confirmed that QAT hardware is x86 only. Unify all the related
configs under redhat/configs/common/generic/x86/.

Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:30:30 -04:00
Fedora Kernel Team b550630b6b [redhat] AUTOMATIC: New configs 2021-08-30 14:30:30 -04:00
Fedora Kernel Team 85b84571a0 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:30 -04:00
Vladis Dronov 62a310e1df [redhat] Provide CONFIG_X86_SGX for x86_64 only
SGX is officially x86_64-only and config X86_SGX depends on X86_64 in Kconfig.
Link: https://github.com/intel/linux-sgx/#prerequisites

Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:30:30 -04:00
Fedora Kernel Team 9189f7929a [redhat] New configs in drivers/clk
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_COMMON_CLK_AXI_CLKGEN:

 Support for the Analog Devices axi-clkgen pcore clock generator for Xilinx
 FPGAs. It is commonly used in Analog Devices' reference designs.

 Symbol: COMMON_CLK_AXI_CLKGEN [=n]
 Type  : tristate
 Defined at drivers/clk/Kconfig:248
   Prompt: AXI clkgen driver
   Depends on: COMMON_CLK [=y] && (HAS_IOMEM [=y] || COMPILE_TEST [=n]) && OF [=y]
   Location:
     -> Device Drivers
       -> Common Clock Framework (COMMON_CLK [=y])

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:30 -04:00
Fedora Kernel Team 458d15e382 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_AHT10:

 If you say yes here, you get support for the Aosong AHT10
 temperature and humidity sensors

 This driver can also be built as a module. If so, the module
 will be called aht10.

 Symbol: SENSORS_AHT10 [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:247
   Prompt: Aosong AHT10
   Depends on: HWMON [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

 CONFIG_SENSORS_TPS23861:

 If you say yes here you get support for Texas Instruments
 TPS23861 802.3at PoE PSE chips.

 This driver can also be built as a module. If so, the module
 will be called tps23861.

 Symbol: SENSORS_TPS23861 [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:1136
   Prompt: Texas Instruments TPS23861 PoE PSE
   Depends on: HWMON [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
 Selects: REGMAP_I2C [=m]

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:29 -04:00
Fedora Kernel Team 5837d2e666 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT:

 The implicit default version of DWARF debug info produced by a
 toolchain changes over time.

 This can break consumers of the debug info that haven't upgraded to
 support newer revisions, and prevent testing newer versions, but
 those should be less common scenarios.

 If unsure, say Y.

 Symbol: DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:264
   Prompt: Rely on the toolchain's implicit default DWARF version
   Depends on: <choice>
   Location:
     -> Kernel hacking
       -> Compile-time checks and compiler options
         -> Compile the kernel with debug info (DEBUG_INFO [=y])
           -> DWARF version (<choice> [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:29 -04:00
Fedora Kernel Team 8eb937bdb0 [redhat] New configs in drivers/pci
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PCIE_MICROCHIP_HOST:

 Say Y here if you want kernel to support the Microchip AXI PCIe
 Host Bridge driver.

 Symbol: PCIE_MICROCHIP_HOST [=n]
 Type  : bool
 Defined at drivers/pci/controller/Kconfig:278
   Prompt: Microchip AXI PCIe host bridge support
   Depends on: PCI [=y] && PCI_MSI [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> PCI support (PCI [=y])
         -> PCI controller drivers
 Selects: PCI_MSI_IRQ_DOMAIN [=y] && GENERIC_MSI_IRQ_DOMAIN [=y] && PCI_HOST_COMMON [=n]

---

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:29 -04:00
Fedora Kernel Team b9e491ccb8 [redhat] New configs in drivers/misc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BCM_VK:

 Select this option to enable support for Broadcom
 VK Accelerators.  VK is used for performing
 multiple specific offload processing tasks in parallel.
 Such offload tasks assist in such operations as video
 transcoding, compression, and crypto tasks.
 This driver enables userspace programs to access these
 accelerators via /dev/bcm-vk.N devices.

 If unsure, say N.

 Symbol: BCM_VK [=n]
 Type  : tristate
 Defined at drivers/misc/bcm-vk/Kconfig:5
   Prompt: Support for Broadcom VK Accelerators
   Depends on: PCI_MSI [=y]
   Location:
     -> Device Drivers
       -> Misc devices

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:29 -04:00
Fedora Kernel Team 9e74b57f55 [redhat] New configs in drivers/acpi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ACPI_FPDT:

 Enable support for the Firmware Performance Data Table (FPDT).
 This table provides information on the timing of the system
 boot, S3 suspend and S3 resume firmware code paths.

 Symbol: ACPI_FPDT [=n]
 Type  : bool
 Defined at drivers/acpi/Kconfig:90
   Prompt: ACPI Firmware Performance Data Table (FPDT) support
   Depends on: ACPI [=y] && X86_64 [=y]
   Location:
     -> Power management and ACPI options
       -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])

---

Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:29 -04:00
Fedora Kernel Team 73f6fc2fa0 [redhat] New configs in lib/Kconfig.kfence
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KFENCE:

 KFENCE is a low-overhead sampling-based detector of heap out-of-bounds
 access, use-after-free, and invalid-free errors. KFENCE is designed
 to have negligible cost to permit enabling it in production
 environments.

 See <file:Documentation/dev-tools/kfence.rst> for more details.

 Note that, KFENCE is not a substitute for explicit testing with tools
 such as KASAN. KFENCE can detect a subset of bugs that KASAN can
 detect, albeit at very different performance profiles. If you can
 afford to use KASAN, continue using KASAN, for example in test
 environments. If your kernel targets production use, and cannot
 enable KASAN due to its cost, consider using KFENCE.

 Symbol: KFENCE [=n]
 Type  : bool
 Defined at lib/Kconfig.kfence:6
   Prompt: KFENCE: low-overhead sampling-based memory safety error detector
   Depends on: HAVE_ARCH_KFENCE [=y] && (SLAB [=n] || SLUB [=y])
   Location:
     -> Kernel hacking
       -> Memory Debugging
 Selects: STACKTRACE [=y]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:29 -04:00
Fedora Kernel Team 6f3dfc9fef [redhat] New configs in lib/Kconfig.kasan
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KASAN_MODULE_TEST:

 This is a part of the KASAN test suite that is incompatible with
 KUnit. Currently includes tests that do bad copy_from/to_user
 accesses.

 Symbol: KASAN_MODULE_TEST [=n]
 Type  : tristate
 Defined at lib/Kconfig.kasan:195
   Prompt: KUnit-incompatible tests of KASAN bug detection capabilities
   Depends on: m && MODULES [=y] && KASAN [=y] && !KASAN_HW_TAGS [=n]
   Location:
     -> Kernel hacking
       -> Memory Debugging
         -> KASAN: runtime memory debugger (KASAN [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:28 -04:00
Fedora Kernel Team be84840f93 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CMDLINE_EXTEND:

 The command-line arguments provided by the boot loader will be
 appended to the default kernel command string.

 Symbol: CMDLINE_EXTEND [=n]
 Type  : bool
 Defined at arch/arm64/Kconfig:1859
   Prompt: Extend bootloader kernel arguments
   Depends on: <choice>
   Location:
     -> Boot options
       -> Default kernel command string (CMDLINE [=console=ttyAMA0])
         -> Kernel command line type (<choice> [=y])

---

 CONFIG_CMDLINE_FROM_BOOTLOADER:

 Uses the command-line options passed by the boot loader. If
 the boot loader doesn't provide any, the default kernel command
 string provided in CMDLINE will be used.

 Symbol: CMDLINE_FROM_BOOTLOADER [=y]
 Type  : bool
 Defined at arch/arm64/Kconfig:1852
   Prompt: Use bootloader kernel arguments if available
   Depends on: <choice>
   Location:
     -> Boot options
       -> Default kernel command string (CMDLINE [=console=ttyAMA0])
         -> Kernel command line type (<choice> [=y])

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:28 -04:00
Fedora Kernel Team 018dfbddfc [redhat] New configs in lib/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_STACK_HASH_ORDER:

 Select the hash size as a power of 2 for the stackdepot hash table.
 Choose a lower value to reduce the memory impact.

 Symbol: STACK_HASH_ORDER [=20]
 Type  : integer
 Range : [12 20]
 Defined at lib/Kconfig:654
   Prompt: stack depot hash size (12 => 4KB, 20 => 1024KB)
   Depends on: STACKDEPOT [=y]
   Location:
     -> Library routines

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:28 -04:00
Fedora Kernel Team 15e6650fd8 [redhat] New configs in drivers/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INTEL_LDMA:

 Enable support for Intel Lightning Mountain SOC DMA controllers.
 These controllers provide DMA capabilities for a variety of on-chip
 devices such as HSNAND and GSWIP (Gigabit Switch IP).

 Symbol: INTEL_LDMA [=n]
 Type  : bool
 Defined at drivers/dma/lgm/Kconfig:2
   Prompt: Lightning Mountain centralized DMA controllers
   Depends on: DMADEVICES [=y] && (X86 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
 Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:28 -04:00
Herton R. Krzesinski 366a84308a redhat: remove CONFIG_DRM_PANEL_XINGBANGDA_XBD599
We reverted the commit "drm: panel: add Xingbangda XBD599 panel", which
introduced this config option. Thus also remove the corresponding config
file.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:28 -04:00
Fedora Kernel Team f62531adb7 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:28 -04:00
Fedora Kernel Team f7a14aa76d New configs in arch/powerpc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CMDLINE:

 On some platforms, there is currently no way for the boot loader to
 pass arguments to the kernel. For these platforms, you can supply
 some command-line options at build time by entering them here.  In
 most cases you will need to specify the root device here.

 Symbol: CMDLINE [=]
 Type  : string
 Defined at arch/powerpc/Kconfig:882
   Prompt: Initial kernel command string
   Location:
     -> Kernel options

Cc: kernel-patches@redhat.com
2021-08-30 14:30:27 -04:00
Fedora Kernel Team 5094369950 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:27 -04:00
Fedora Kernel Team a697b011a2 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:27 -04:00
Justin M. Forbes 86a81a2466 Turn on CONFIG_PPC_QUEUED_SPINLOCKS as it is default upstream now
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:27 -04:00
Fedora Kernel Team 911c2d7594 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:27 -04:00
Fedora Kernel Team 41ce9d5de3 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:27 -04:00
Fedora Kernel Team dcf671715b [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARCH_N5X:

 This enables support for Intel's eASIC N5X SoCFPGA Family.

 Symbol: ARCH_N5X [=n]
 Type  : bool
 Defined at arch/arm64/Kconfig.platforms:16
   Prompt: Intel's eASIC N5X SoCFPGA Family
   Location:
     -> Platform selection

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:27 -04:00
Prarit Bhargava dca5a7bc7a RHMAINTAINERS: remove dmilburn
There are still some leftover dmilburn references.  I thought I had got
rid of these.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: gtiwari@redhat.com
Cc: darcari@redhat.com
2021-08-30 14:30:27 -04:00
Fedora Kernel Team 03045546c7 [redhat] New configs in drivers/net/ethernet/mellanox
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MLX5_SF:

 Build support for subfuction device in the NIC. A Mellanox subfunction
 device can support RDMA, netdevice and vdpa device.
 It is similar to a SRIOV VF but it doesn't require SRIOV support.

 Symbol: MLX5_SF [=n]
 Type  : bool
 Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205
   Prompt: Mellanox Technologies subfunction device support using auxiliary device
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
           -> Mellanox devices (NET_VENDOR_MELLANOX [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:27 -04:00
Fedora Kernel Team 0f3f0788f7 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:26 -04:00
Fedora Kernel Team 318d80b486 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:26 -04:00
Patrick Talbert 2bc14d12d4 [redhat] configs: Enable CONFIG_SND_JACK_INJECTION_DEBUG for the debug
variant

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:26 -04:00
Fedora Kernel Team 7e529e30e8 [redhat] New configs in sound/core
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_JACK_INJECTION_DEBUG:

 This option can be used to enable or disable sound jack
 software injection.
 Say Y if you are debugging via jack injection interface.
 If unsure select "N".

 Symbol: SND_JACK_INJECTION_DEBUG [=n]
 Type  : bool
 Defined at sound/core/Kconfig:190
   Prompt: Sound jack injection interface via debugfs
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_JACK [=y] && SND_DEBUG [=y] && DEBUG_FS [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> Debug (SND_DEBUG [=y])

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:26 -04:00
Fedora Kernel Team 8ac3f7907e [redhat] New configs in net/netfilter
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_IP_VS_TWOS:

 The weighted random twos choice least-connection scheduling
 algorithm picks two random real servers and directs network
 connections to the server with the least active connections
 normalized by the server weight.

 If you want to compile it in kernel, say Y. To compile it as a
 module, choose M here. If unsure, say N.

 Symbol: IP_VS_TWOS [=n]
 Type  : tristate
 Defined at net/netfilter/ipvs/Kconfig:274
   Prompt: weighted random twos choice least-connection scheduling
   Depends on: NET [=y] && NETFILTER [=y] && IP_VS [=m]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> Network packet filtering framework (Netfilter) (NETFILTER [=y])
           -> IP virtual server support (IP_VS [=m])

---

Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Antoine Tenart <atenart@redhat.com>
Cc: Balazs Nemeth <bnemeth@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:26 -04:00
Fedora Kernel Team fac3644fe4 [redhat] New configs in drivers/powercap
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DTPM:

 This enables support for the power capping for the dynamic
 thermal power management userspace engine.

 Symbol: DTPM [=n]
 Type  : bool
 Defined at drivers/powercap/Kconfig:47
   Prompt: Power capping for Dynamic Thermal Power Management
   Depends on: POWERCAP [=y]
   Location:
     -> Device Drivers
       -> Generic powercap sysfs driver (POWERCAP [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:26 -04:00
Fedora Kernel Team 288f74fa00 [redhat] New configs in drivers/net/wireless
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MT7921E:

 This adds support for MT7921E 802.11ax 2x2:2SS wireless devices.

 To compile this driver as a module, choose M here.

 Symbol: MT7921E [=n]
 Type  : tristate
 Defined at drivers/net/wireless/mediatek/mt76/mt7921/Kconfig:2
   Prompt: MediaTek MT7921E (PCIe) support
   Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless LAN (WLAN [=y])
           -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
 Selects: MT76_CONNAC_LIB [=n] && WANT_DEV_COREDUMP [=y]

---

Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:26 -04:00
Fedora Kernel Team e7070d0306 [redhat] New configs in drivers/char
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TCG_TIS_I2C_CR50:

 This is a driver for the Google cr50 I2C TPM interface which is a
 custom microcontroller and requires a custom i2c protocol interface
 to handle the limitations of the hardware.  To compile this driver
 as a module, choose M here; the module will be called tcg_tis_i2c_cr50.

 Symbol: TCG_TIS_I2C_CR50 [=n]
 Type  : tristate
 Defined at drivers/char/tpm/Kconfig:89
   Prompt: TPM Interface Specification 2.0 Interface (I2C - CR50)
   Depends on: TCG_TPM [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> TPM Hardware Support (TCG_TPM [=y])
 Selects: TCG_CR50

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:25 -04:00
Fedora Kernel Team cd76cf6328 [redhat] New configs in kernel/trace
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FTRACE_RECORD_RECURSION:

 All callbacks that attach to the function tracing have some sort
 of protection against recursion. Even though the protection exists,
 it adds overhead. This option will create a file in the tracefs
 file system called "recursed_functions" that will list the functions
 that triggered a recursion.

 This will add more overhead to cases that have recursion.

 If unsure, say N

 Symbol: FTRACE_RECORD_RECURSION [=n]
 Type  : bool
 Defined at kernel/trace/Kconfig:737
   Prompt: Record functions that recurse in function tracing
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && FUNCTION_TRACER [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])

---

 CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS:

 This will audit the time stamps on the ring buffer sub
 buffer to make sure that all the time deltas for the
 events on a sub buffer matches the current time stamp.
 This audit is performed for every event that is not
 interrupted, or interrupting another event. A check
 is also made when traversing sub buffers to make sure
 that all the deltas on the previous sub buffer do not
 add up to be greater than the current time stamp.

 NOTE: This adds significant overhead to recording of events,
 and should only be used to test the logic of the ring buffer.
 Do not use it on production systems.

 Only say Y if you understand what this does, and you
 still want it enabled. Otherwise say N

 Symbol: RING_BUFFER_VALIDATE_TIME_DELTAS [=n]
 Type  : bool
 Defined at kernel/trace/Kconfig:846
   Prompt: Verify ring buffer time stamp deltas
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && RING_BUFFER [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])

---

Cc: Jerome Marchand <jmarchan@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:25 -04:00
Fedora Kernel Team 26ed396683 [redhat] New configs in drivers/acpi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ACPI_PLATFORM_PROFILE:

 This driver adds support for platform-profiles on platforms that
 support it.

 Platform-profiles can be used to control the platform behaviour. For
 example whether to operate in a lower power mode, in a higher
 power performance mode or between the two.

 This driver provides the sysfs interface and is used as the registration
 point for platform specific drivers.

 Which profiles are supported is determined on a per-platform basis and
 should be obtained from the platform specific driver.

 Symbol: ACPI_PLATFORM_PROFILE [=m]
 Type  : tristate
 Defined at drivers/acpi/Kconfig:329
   Prompt: ACPI Platform Profile Driver
   Depends on: ACPI [=y]
   Location:
     -> Power management and ACPI options
       -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])

---

Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:25 -04:00
Justin M. Forbes 48b412b21e Update pending-common configs to address new upstream config deps
CONFIG_TYPEC_UCSI now depends on CONFIG_USB_ROLE_SWITCH, and must have
the same tristate.

CONFIG_HSA_AMD now will select CONFIG_DRM_AMDGPU_USERPTR, so it must be
turned on if CONFIG_HSA_AMD is on, or we will have a config mismatch

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:25 -04:00
Herton R. Krzesinski 332ec423f9 rpmspec: ship gpio-watch.debug in the proper debuginfo package
The gpio-watch tool is shipped within the kernel-tools package. However,
when it was added some time ago, the debuginfo pattern inside the spec
file was not updated, so the gpio-watch.debug file ends up in the
kernel-debuginfo-common package instead of the kernel-tools-debuginfo.

This change fixes the problem, and also it's likely will fix an
update/downgrade test done on CI for RHEL that reports:

Error: Transaction test error:
  file /usr/lib/debug/usr/bin/gpio-watch.debug from install of
kernel-debuginfo-common-x86_64-5.11.0-0.rc7.151.el9.x86_64 conflicts
with file from package kernel-debuginfo-common-x86_64-5.11.0-1.el9.x86_64

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:25 -04:00
Fedora Kernel Team 7f1541a288 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:25 -04:00
Fedora Kernel Team 4f34a9e7c2 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:25 -04:00
Fedora Kernel Team d8b229f2ae [redhat] New configs in kernel/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DMA_MAP_BENCHMARK:

 Provides /sys/kernel/debug/dma_map_benchmark that helps with testing
 performance of dma_(un)map_page.

 See tools/testing/selftests/dma/dma_map_benchmark.c

 Symbol: DMA_MAP_BENCHMARK [=n]
 Type  : bool
 Defined at kernel/dma/Kconfig:228
   Prompt: Enable benchmarking of streaming DMA mapping
   Depends on: DEBUG_FS [=y]
   Location:
     -> Library routines

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:25 -04:00
Jeremy Cline ccbde8d2d6 [redhat] New configs in drivers/iommu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_SMMU_V3_SVA:

 Support for sharing process address spaces with devices using the
 SMMUv3.

 Say Y here if your system supports SVA extensions such as PCIe PASID
 and PRI.

 Symbol: ARM_SMMU_V3_SVA [=n]
 Type  : bool
 Defined at drivers/iommu/Kconfig:311
   Prompt: Shared Virtual Addressing support for the ARM SMMUv3
   Depends on: IOMMU_SUPPORT [=y] && ARM_SMMU_V3 [=y]
   Location:
     -> Device Drivers
       -> IOMMU Hardware Support (IOMMU_SUPPORT [=y])
         -> ARM Ltd. System MMU Version 3 (SMMUv3) Support (ARM_SMMU_V3 [=y])

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:24 -04:00
Justin M. Forbes d47d34beca Removed description text as a comment confuses the config generation
Signed-off-by: Justin M. Forbes <jforbes@redhat.com>
2021-08-30 14:30:24 -04:00
Jeremy Cline d60c1f5862 [redhat] New configs in drivers/perf
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_CMN:

 Support for PMU events monitoring on the Arm CMN-600 Coherent Mesh
 Network interconnect.

 Symbol: ARM_CMN [=n]
 Type  : tristate
 Defined at drivers/perf/Kconfig:44
   Prompt: Arm CMN-600 PMU support
   Depends on: PERF_EVENTS [=y] && (ARM64 [=y] || COMPILE_TEST [=n] && 64BIT [=y])
   Location:
     -> Device Drivers
       -> Performance monitor support

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:24 -04:00
Fedora Kernel Team 4923eb4c9c [redhat] New configs in drivers/net/ethernet/chelsio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CHELSIO_INLINE_CRYPTO:

 Enable support for inline crypto.
 Allows enable/disable from list of inline crypto drivers.

 Symbol: CHELSIO_INLINE_CRYPTO [=y]
 Type  : bool
 Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6
   Prompt: Chelsio Inline Crypto support
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
           -> Chelsio devices (NET_VENDOR_CHELSIO [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:24 -04:00
Jeremy Cline 3eedda8d87 New configs in drivers/dma-buf
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DMABUF_HEAPS_SYSTEM:

 Choose this option to enable the system dmabuf heap. The system heap
 is backed by pages from the buddy allocator. If in doubt, say Y.

 Symbol: DMABUF_HEAPS_SYSTEM [=n]
 Type  : bool
 Defined at drivers/dma-buf/heaps/Kconfig:1
   Prompt: DMA-BUF System Heap
   Depends on: DMABUF_HEAPS [=y]
   Location:
     -> Device Drivers
       -> DMABUF options
         -> DMA-BUF Userland Memory Heaps (DMABUF_HEAPS [=y])

Cc: Lyude Paul <lyude@redhat.com>
2021-08-30 14:30:24 -04:00
CKI Gitlab 2b1125bbc5 [redhat] New configs in net/netfilter
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NFT_REJECT_NETDEV:

 This option enables the REJECT support from the netdev table.
 The return packet generation will be delegated to the IPv4
 or IPv6 ICMP or TCP RST implementation depending on the
 protocol of the packet.

 Symbol: NFT_REJECT_NETDEV [=n]
 Type  : tristate
 Defined at net/netfilter/Kconfig:685
   Prompt: Netfilter nf_tables netdev REJECT support
   Depends on: NET [=y] && INET [=y] && NETFILTER [=y] && NF_TABLES [=m] && NF_TABLES_NETDEV [=y] && NFT_REJECT_IPV4 [=m] && NFT_REJECT_IPV6 [=m]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> Network packet filtering framework (Netfilter) (NETFILTER [=y])
           -> Core Netfilter Configuration
             -> Netfilter nf_tables support (NF_TABLES [=m])

---

Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:24 -04:00
Peter Robinson 9e21c3d905 Fedora: ARMv7: build for 16 CPUs.
In reality we don't have a need for more than 16 CPUs and
it appears in certain circumstances it can cause us problems.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:24 -04:00
Peter Robinson a787cc2ccd Fedora: only enable DEBUG_HIGHMEM on debug kernels
We shouldn't have DEBUG_HIGHMEM for default kernels so disable it
and any of the bits that try to enable it on standard kernels but
leave it in place for debug kernels.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:23 -04:00
Ondrej Mosnacek ddd1ad0677 process_configs.sh: fix find/xargs data flow
`xargs -0` expects arguments delimited by \0 on stdin, but instead it
recieves a list of filenames delimited by \n from `find`. Fix that by
adding `-print0` to `find` so that it outputs the filenames delimited by
\0 as xargs expects.

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 14:30:23 -04:00
Kamal Heib 0b6e526272 RHMAINTAINERS: Add entry for the rdma_rxe driver
Add myself to be the maintainer for the rdma_rxe driver.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:23 -04:00
Kamal Heib 8726c4986c RHMAINTAINERS: Add entry for the siw driver
Add myself to be the maintainer for the siw driver.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:23 -04:00
Kamal Heib 3947b2a5b7 RHMAINTAINERS: Add entry for the vmw_pvrdma driver
Add myself to be the maintainer for the vmw_pvrdma driver.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:23 -04:00
Kamal Heib a15aa7525e RHMAINTAINERS: Add entry for the efa driver
Add myself to be the maintainer for the efa driver.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:23 -04:00
Kamal Heib f241dad9bf RHMAINTAINERS: Add entry for the bnxt_re driver
Add Selvin to be the maintainer for the bnxt_re driver.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Signed-off-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:23 -04:00
Justin M. Forbes 8be8321210 Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:23 -04:00
Peter Robinson f93e2b535e fedora: minor arm sound config updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:23 -04:00
Justin M. Forbes 56cc402160 Fix trailing white space in redhat/configs/fedora/generic/CONFIG_SND_INTEL_BYT_PREFER_SOF
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:22 -04:00
Hans de Goede 2b9ebcc1f3 Add a redhat/rebase-notes.txt file
As discussed on the Fedora kernel list add a redhat/rebase-notes.txt
file with notes about things to keep in mind when rebasing the
Fedora kernel packages to a new upstream release.

And populate this file with a note about disabling
SND_INTEL_BYT_PREFER_SOF for Fedora 33 and older.

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 14:30:22 -04:00
Hans de Goede 9d26f36e74 Turn on SND_INTEL_BYT_PREFER_SOF for Fedora
For Fedora 34 and newer we want to use the SOF driver as the
preferred driver for Intel LPE audio, see:
https://fedoraproject.org/w/index.php?title=Changes/SofDefaultForIntelLpe

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2021-08-30 14:30:22 -04:00
Hans de Goede 81d2e79af4 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:22 -04:00
Waiman Long 2397394c3e RHMAINTAINERS: Add futex subsystem
Bugzilla: INTERNAL
Upstream: RHEL only

As I am also tracking upstream changes in futex code, I may as well add
the futex subsystem entry.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:22 -04:00
Marcelo Ricardo Leitner 8b38a3aa6e RHMAINTAINERS: NETWORKING: Add entry for Balazs Nemeth
Balazs is now part of the networking team.

RH-Acked-by: Balazs Nemeth <bnemeth@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Xin Long <lxin@redhat.com>

Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:22 -04:00
Prarit Bhargava 71407da0b0 RHMAINTAINERS: Fix list entries for kernel-patches@redhat.com
kernel-patches@redhat.com is a list, not a maintainer.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:22 -04:00
Veronika Kabatova d50a75fec9 CI: Drop MR ID from the name variable
While this is not breaking ARK testing as the pipeline is not fully
building the kernel but only SRPM, we should fix this repo as well to
not run into any suprises in the future. The name is used to grab the
correct ccache file, and using the MR ID in there would render the whole
ccache setup useless.

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 14:30:22 -04:00
Philipp Rudo df616b05a2 [redhat] spec: package decompressor vmlinux for s390
On s390 more and more code from the early boot stage is moved to the
decompressor. With this the code complexity and thus the chances to
introduce bugs increases. In order to be able to debug these early boot
bugs package the decompressors vmlinux together with the other debuginfo
for s390.

This change requires kernel commit 7a84ffc047 ("s390/boot: add
build-id to decompressor") to work.

Upstream Status: RHEL only

Signed-off-by: Philipp Rudo <prudo@redhat.com>
2021-08-30 14:30:22 -04:00
Herton R. Krzesinski ed58fa2db7 redhat: add DUP and kpatch certificates to system trusted keys for RHEL build
We were not including yet the DUP and kpatch additional certificates in the
build process for RHEL. Do it by creating the required pem file and setting
the related kernel config option.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:22 -04:00
Justin M. Forbes c1fa2ff280 The comments in CONFIG_USB_RTL8153_ECM actually turn off CONFIG_USB_RTL8152
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:21 -04:00
Veronika Kabatova c3661ca13b Update CKI pipeline project
The paths have been changed and CI won't work without this update.

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 14:30:21 -04:00
Justin M. Forbes fd0d75b2ee Turn off additional KASAN options for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:21 -04:00
Justin M. Forbes db18fe1755 Rename the master branch to rawhide for Fedora
Yesterday, dist-git in Fedora was change, renaming the master branch to
either rawhide or main depending on the context.  In our case, rawhide
is the correct default branch going forward.  You can not run 'make
dist-git' successfully until this is merged.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:21 -04:00
Ben Crocker a3c26f92bd Makefile targets for packit integration
* dist-tarball
* dist-kernelrelease
* dist-kernelversion
* dist-specfile

dist-tarball echoes the path to the tarball, starting with redhat/.
dist-kernelrelease echoes the package name and full version;
dist-kernelversion echoes just the full version strin.
dist-specfile (possibly) invokes setup-source, then echoes a path to
the (possibly newly-generated) specfile.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:21 -04:00
Justin M. Forbes c914cbc299 Turn off KASAN for rawhide debug builds
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:21 -04:00
Fedora Kernel Team 4f67b44e14 [redhat] New configs in security/keys
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

CONFIG_KEY_NOTIFICATIONS

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:21 -04:00
Justin Forbes f3a584e8da New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KVM_ARM_PMU:

 Adds support for a virtual Performance Monitoring Unit (PMU) in
 virtual machines.

 Symbol: KVM_ARM_PMU [=y]
 Type  : bool
 Defined at arch/arm64/kvm/Kconfig:52
   Prompt: Virtual Performance Monitoring Unit (PMU) support
   Depends on: VIRTUALIZATION [=y] && KVM [=y] && HW_PERF_EVENTS [=y]
   Location:
     -> Virtualization (VIRTUALIZATION [=y])
       -> Kernel-based Virtual Machine (KVM) support (KVM [=y])

Cc: Mark Salter <msalter@redhat.com>
2021-08-30 14:30:21 -04:00
Peter Robinson 74d3a8d32d Remove deprecated Intel MIC config options
The Intel MIC drivers were removed in 5.10, in commit 80ade22,
so these driver configs are now irrelvent so remove them. This
primarilly affects Fedora as they were disabled in ARK anyway.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:21 -04:00
Herton R. Krzesinski 4bd173af89 redhat: replace inline awk script with genlog.py call
Upstream Status: RHEL only
Tested: verified changelog created after make rh-release

This wires in the genlog.py script call in genspec.sh, replacing the
previous inline awk script.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:20 -04:00
Herton R. Krzesinski 9b733086a1 redhat: add genlog.py script
Upstream Status: RHEL only
Tested: verified changelog created after make rh-release

This change adds a separate python script that will generate changelog
items for the kernel RPM package, based on git log contents. It aims to
be a straight replacement of the current awk logic in redhat/genspec.sh.

I received review feedback from Jan Stancek, Frantisek Hrbata, Don
Zickus on an earlier version of the script, and this version contains
suggestions made by them.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:20 -04:00
Ben Crocker 8553f1f6de kernel.spec.template - fix use_vdso usage
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:20 -04:00
Ben Crocker bdf3f3d79c [redhat] Makefile: new dist-buildreq-check target
Add a new dist-buildreq-check target that checks for missing
packages via rpmspec -q --buildrequires, and make dist-configs-prep
dependent on it.

This change is based on suggestions from Josh Poimboeuf, Don Zickus,
and Herton Krzesinski.  Ultimately this is Herton's version, which
generates the list of missing packages from an already-created
kernel.spec file.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:20 -04:00
Herton R. Krzesinski e0b7668ffe redhat: remove remaining references of CONFIG_RH_DISABLE_DEPRECATED
In the commit "Rename RH_DISABLE_DEPRECATED to RHEL_DIFFERENCES", the change
in kernel/Makefile was an addition instead of a rename. This change fixes
that by removing the old line still referencing CONFIG_RH_DISABLE_DEPRECATED.

Also, the redhat/configs tree still have the old config option files, remove
them too.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:20 -04:00
Justin M. Forbes 2c33a4479a Turn off vdso_install for ppc
With upstream commit 7fe2de246e
powerpc/vdso: Stripped VDSO is not needed, don't build it

the make targets for vdso_install are gone for ppc. If we call them, the
build fails. This just turns them off.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:20 -04:00
Fedora Kernel Team 1652d521fc [redhat] AUTOMATIC: New configs 2021-08-30 14:30:20 -04:00
Fedora Kernel Team 1a18a16c54 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:20 -04:00
Jiri Olsa d7ed120d0c Remove bpf-helpers.7 from bpftool package
It's packaged by man-pages. Removing bpf-helpers.7 from
bpftool package (rhbz #1686954, #1918707).

Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-08-30 14:30:19 -04:00
Ben Crocker 2d525ab424 [redhat] Makefile: consolidate rpmbuild cmds into one target
Consolidate rpmbuild commands into a new target, do-rpmbuild,
and invoke it from dist-all-rpms, dist-srpm, etc. via, e.g.,

dist-srpm: RPMBUILDOPTS=--nodeps -bs
dist-srpm: dist-sources do-rpmbuild

This works for all the targets that invoke rpmbuild EXCEPT
dist-kernel-%, which we rewrite:

dist-kernel-%: dist-sources
	RPMBUILDOPTS="--target $(MACH) --with $* --without vdso_install --without perf --without tools -bb" make do-rpmbuild

i.e., setting RPMBUILDOPTS and then invoking make again,
and dist-srpm-gcov, which already had an extra 'make' in its
recipe.

The cost of the dist-kernel-% rewrite is an extra trip through the Makefile,
and the extra prologue (4 lines) and epilogue (1 line) output that goes with it.

The newly rewritten dist-* targets require some ordering constraints,
which are not a bad idea even in the absence of these modifications,
and which can be accomplished by moving

    setup-source, dist-configs-check

FROM dist-sources TO sources-rh, thus making sure that
setup-source and dist-configs-check get made strictly before
sources-rh.

With these ordering constraints in place, commands like the following
work as expected:

% make -j 64 dist-rpms

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:19 -04:00
Fedora Kernel Team 63b288ac39 New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEBUG_FS_ALLOW_ALL:

 No restrictions apply. Both API and filesystem registration
 is on. This is the normal default operation.

 Symbol: DEBUG_FS_ALLOW_ALL [=y]
 Type  : bool
 Defined at lib/Kconfig.debug:500
   Prompt: Access normal
   Depends on: <choice>
   Location:
     -> Kernel hacking
       -> Generic Kernel Debugging Instruments
         -> Debug Filesystem (DEBUG_FS [=y])
           -> Debugfs default access (<choice> [=y])

Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:19 -04:00
Jeremy Cline 202d087a05 [redhat] New configs in drivers/spi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SPI_AMD:

 Enables SPI controller driver for AMD SoC.

 Symbol: SPI_AMD [=n]
 Type  : tristate
 Defined at drivers/spi/Kconfig:917
   Prompt: AMD SPI controller
   Depends on: SPI [=y] && SPI_MASTER [=y] && (SPI_MASTER [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> SPI support (SPI [=y])

---

Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 14:30:19 -04:00
Fedora Kernel Team dde0883ccf [redhat] AUTOMATIC: New configs 2021-08-30 14:30:19 -04:00
Justin M. Forbes d358c7d4de Turn off CONFIG_VIRTIO_CONSOLE for s390x zfcpdump
Upstream commit 9f30eb29c5 changed
VIRTIO_CONSOLE from depending on VIRTIO to selecting VIRTIO.  This made
it possible to build in the console with virtio drivers being modular.
Before this change, VIRTIO_CONSOLE status did not matter for the
zfcpdump kernel, because VIRTIO which it depends on was turned off.
After that change, having VIRTIO_CONSOLE on will select VIRTIO and turn
on those drivers as modules. This really sets things back to the way
they were.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:19 -04:00
Justin M. Forbes 74c221accf New configs in drivers/clk
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_COMMON_CLK:

 The common clock framework is a single definition of struct
 clk, useful across many platforms, as well as an
 implementation of the clock API in include/linux/clk.h.
 Architectures utilizing the common struct clk should select
 this option.

 Symbol: COMMON_CLK [=n]
 Type  : bool
 Defined at drivers/clk/Kconfig:25
   Prompt: Common Clock Framework
   Depends on: !HAVE_LEGACY_CLK [=n]
   Location:
     -> Device Drivers
 Selects: HAVE_CLK_PREPARE [=n] && CLKDEV_LOOKUP [=n] && SRCU [=y] && RATIONAL [=n]
 Selected by [n]:
   - MFD_INTEL_LPSS [=n] && HAS_IOMEM [=y]
   - INTEL_ATOMISP [=n] && STAGING [=n] && STAGING_MEDIA [=n] && MEDIA_SUPPORT [=n] && X86 && EFI && PCI [=y] && ACPI
   - PMC_ATOM [=n] && X86 && PCI [=y]

Cc: Mark Salter <msalter@redhat.com>
2021-08-30 14:30:19 -04:00
Jakub Čajka f6f966fb9e Keep VIRTIO_CONSOLE on s390x available.
This regression has been hit in the CoreOS pipeline as it utilizes
it to gather build logs from build VMs during build of the CoreOS.

Fixes RHBZ1917575
2021-08-30 14:30:18 -04:00
Jeremy Cline 4aa229843f New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEBUG_VM_PGTABLE:

 This option provides a debug method which can be used to test
 architecture page table helper functions on various platforms in
 verifying if they comply with expected generic MM semantics. This
 will help architecture code in making sure that any changes or
 new additions of these helpers still conform to expected
 semantics of the generic MM. Platforms will have to opt in for
 this through ARCH_HAS_DEBUG_VM_PGTABLE.

 If unsure, say N.

 Symbol: DEBUG_VM_PGTABLE [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:702
   Prompt: Debug arch page table for semantics compliance
   Depends on: MMU [=y] && ARCH_HAS_DEBUG_VM_PGTABLE [=y]
   Location:
     -> Kernel hacking
       -> Memory Debugging

Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:18 -04:00
Jeremy Cline e209986b71 [redhat] New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_EMMITSBURG:

 This pinctrl driver provides an interface that allows configuring
 of Intel Emmitsburg pins and using them as GPIOs.

 Symbol: PINCTRL_EMMITSBURG [=n]
 Type  : tristate
 Defined at drivers/pinctrl/intel/Kconfig:98
   Prompt: Intel Emmitsburg pinctrl and GPIO driver
   Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_INTEL [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:18 -04:00
Jeremy Cline b7c8a3f982 [redhat] New configs in drivers/crypto
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ZCRYPT_DEBUG:

 Say 'Y' here to enable some additional debug features on the
 s390 cryptographic adapters driver.

 There will be some more sysfs attributes displayed for ap cards
 and queues and some flags on crypto requests are interpreted as
 debugging messages to force error injection.

 Do not enable on production level kernel build.

 If unsure, say N.

 Symbol: ZCRYPT_DEBUG [=n]
 Type  : bool
 Defined at drivers/crypto/Kconfig:78
   Prompt: Enable debug features for s390 cryptographic adapters
   Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && DEBUG_KERNEL [=y] && ZCRYPT [=m]
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Hardware crypto devices (CRYPTO_HW [=y])
         -> Support for s390 cryptographic adapters (ZCRYPT [=m])

---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:18 -04:00
Fedora Kernel Team e69fc3ca55 [redhat] Move config option CONFIG_MLX5_EN_IPSEC to common area
Both ark and fedora have the same setting for this option so move it to
the common folder.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:18 -04:00
Fedora Kernel Team b7659d3634 [redhat] New configs in drivers/hid
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AMD_SFH_HID:

 If you say yes to this option, support will be included for the
 AMD Sensor Fusion Hub.
 This driver will enable sensors functionality on AMD platforms
 starting from 17h family of RYZEN parts.

 This driver can also be built as a module. If so, the module will
 be called amd-sfh.
 Say Y or M here if you want to support AMD SFH. If unsure, say N.
 Symbol: AMD_SFH_HID [=n]
 Type  : tristate
 Defined at drivers/hid/amd-sfh-hid/Kconfig:7
   Prompt: AMD Sensor Fusion Hub
   Depends on: INPUT [=y] && (X86_64 [=y] || COMPILE_TEST [=n]) && PCI [=y] && HID [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> AMD SFH HID Support

---

Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:18 -04:00
Jeremy Cline 116d16b8df [redhat] New configs in drivers/vfio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VFIO_PCI_ZDEV:

 Enabling this option exposes VFIO capabilities containing hardware
 configuration for zPCI devices. This enables userspace (e.g. QEMU)
 to supply proper configuration values instead of hard-coded defaults
 for zPCI devices passed through via VFIO on s390.

 Say Y here.

 Symbol: VFIO_PCI_ZDEV [=y]
 Type  : bool
 Defined at drivers/vfio/pci/Kconfig:49
   Prompt: VFIO PCI ZPCI device CLP support
   Depends on: VFIO_PCI [=m] && S390 [=y]
   Location:
     -> Device Drivers
       -> VFIO Non-Privileged userspace driver framework (VFIO [=m])
         -> VFIO support for PCI devices (VFIO_PCI [=m])

---

Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:17 -04:00
CKI Gitlab 748acd3f1c [redhat] New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_INTEL_PMT:

 The Intel Platform Monitoring Technology (PMT) is an interface that
 provides access to hardware monitor registers. This driver supports
 Telemetry, Watcher, and Crashlog PMT capabilities/devices for
 platforms starting from Tiger Lake.

 Symbol: MFD_INTEL_PMT [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:685
   Prompt: Intel Platform Monitoring Technology (PMT) support
   Depends on: HAS_IOMEM [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_CORE [=y]

---

Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:17 -04:00
CKI Gitlab 8c02b54664 [redhat] New configs in drivers/edac
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EDAC_IGEN6:

 Support for error detection and correction on the Intel
 client SoC Integrated Memory Controller using In-Band ECC IP.
 This In-Band ECC is first used on the Elkhart Lake SoC but
 may appear on others in the future.

 Symbol: EDAC_IGEN6 [=n]
 Type  : tristate
 Defined at drivers/edac/Kconfig:272
   Prompt: Intel client SoC Integrated MC
   Depends on: EDAC [=y] && PCI [=y] && X86_64 [=y] && PCI_MMCONFIG [=y] && ARCH_HAVE_NMI_SAFE_CMPXCHG [=y]
   Location:
     -> Device Drivers
       -> EDAC (Error Detection And Correction) reporting (EDAC [=y])

---

Cc: Aristeu Rozanski <aris@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:17 -04:00
Fedora Kernel Team f6f547e4ad [redhat] New configs in drivers/mailbox
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_MHU_V2:

 Say Y here if you want to build the ARM MHUv2 controller driver,
 which provides unidirectional mailboxes between processing elements.

 Symbol: ARM_MHU_V2 [=n]
 Type  : tristate
 Defined at drivers/mailbox/Kconfig:19
   Prompt: ARM MHUv2 Mailbox
   Depends on: MAILBOX [=y] && ARM_AMBA [=y]
   Location:
     -> Device Drivers
       -> Mailbox Hardware Support (MAILBOX [=y])

---

Cc: Al Stone <ahs3@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:17 -04:00
Fedora Kernel Team 1deee6a4ff [redhat] New configs in drivers/hid
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HID_VIVALDI:

 Say Y here if you want to enable support for Vivaldi keyboards.

 Vivaldi keyboards use a vendor-specific (Google) HID usage to report
 how the keys in the top row are physically ordered.

 Symbol: HID_VIVALDI [=n]
 Type  : tristate
 Defined at drivers/hid/Kconfig:400
   Prompt: Vivaldi Keyboard
   Depends on: INPUT [=y] && HID [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> HID bus support (HID [=y])
           -> Special HID drivers

---

Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:17 -04:00
Fedora Kernel Team dc60dd84d5 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARCH_BCM4908:

 This enables support for the Broadcom BCM4906, BCM4908 and
 BCM49408 SoCs. These SoCs use Brahma-B53 cores and can be
 found in home routers.

 Symbol: ARCH_BCM4908 [=n]
 Type  : bool
 Defined at arch/arm64/Kconfig.platforms:46
   Prompt: Broadcom BCM4908 family
   Location:
     -> Platform selection
 Selects: GPIOLIB [=y]

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:17 -04:00
Justin M. Forbes 0676cd2970 Fedora 5.11 config updates part 4
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:16 -04:00
Justin M. Forbes f64ea93a4d Fedora 5.11 config updates part 3
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:16 -04:00
Justin M. Forbes 2a18b684bf Fedora 5.11 config updates part 2
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:16 -04:00
Joe Lawrence 5beba3a6b0 Update internal (test) module list from RHEL-8
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1915073
Upstream Status: RHEL only

Forward port update from RHEL-8 to add the following modules to the
mod-internal.list file:

  dmatest
  test_klp_*

In RHEL builds, these modules are packaged into the
kernel-modules-internal rpm and not kernel-core.

Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
2021-08-30 14:30:16 -04:00
Fedora Kernel Team 11b8208a37 [redhat] New configs in drivers/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_QCOM_GPI_DMA:

 Enable support for the QCOM GPI DMA controller. This controller
 provides DMA capabilities for a variety of peripheral buses such
 as I2C, UART, and SPI. By using GPI dmaengine driver, bus drivers
 can use a standardize interface that is protocol independent to
 transfer data between DDR and peripheral.

 Symbol: QCOM_GPI_DMA [=n]
 Type  : tristate
 Defined at drivers/dma/qcom/Kconfig:22
   Prompt: Qualcomm Technologies GPI DMA support
   Depends on: DMADEVICES [=y] && ARCH_QCOM [=y]
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
 Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=n]

---

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:16 -04:00
CKI Gitlab f916313ce6 [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_UV_SYSFS:

 This driver supports a sysfs tree describing information about
 UV systems at /sys/firmware/sgi_uv/.

 To compile this driver as a module, choose M here: the module will
 be called uv_sysfs.

 Symbol: UV_SYSFS [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:81
   Prompt: Sysfs structure for UV systems
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_UV [=y] && SYSFS [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---

Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:16 -04:00
Fedora Kernel Team a2003420b6 [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DRM_ANALOGIX_ANX7625:

 ANX7625 is an ultra-low power 4K mobile HD transmitter
 designed for portable devices. It converts MIPI/DPI to
 DisplayPort1.3 4K.

 Symbol: DRM_ANALOGIX_ANX7625 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/analogix/Kconfig:29
   Prompt: Analogix Anx7625 MIPI to DP interface support
   Depends on: HAS_IOMEM [=y] && DRM_BRIDGE [=y] && DRM [=m] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges

---

 CONFIG_DRM_LONTIUM_LT9611UXC:

 Driver for Lontium LT9611UXC DSI to HDMI bridge
 chip driver that converts dual DSI and I2S to
 HDMI signals
 Please say Y if you have such hardware.

 Symbol: DRM_LONTIUM_LT9611UXC [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:64
   Prompt: Lontium LT9611UXC DSI/HDMI bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: SND_SOC_HDMI_CODEC [=n] && DRM_PANEL_BRIDGE [=y] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]

---

 CONFIG_DRM_PANEL_ABT_Y030XX067A:

 Say Y here to enable support for the Asia Better Technology Ltd.
 Y030XX067A 320x480 3.0" panel as found in the YLM RG-280M, RG-300
 and RG-99 handheld gaming consoles.

 Symbol: DRM_PANEL_ABT_Y030XX067A [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/panel/Kconfig:11
   Prompt: ABT Y030XX067A 320x480 LCD panel
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && SPI [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Panels
 Selects: REGMAP_SPI [=m]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:15 -04:00
Fedora Kernel Team 064011b672 [redhat] New configs in net/bridge
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BRIDGE_CFM:

 If you say Y here, then the Ethernet bridge will be able to run CFM
 protocol according to 802.1Q section 12.14

 Say N to exclude this support and reduce the binary size.

 If unsure, say N.

 Symbol: BRIDGE_CFM [=n]
 Type  : bool
 Defined at net/bridge/Kconfig:77
   Prompt: CFM protocol
   Depends on: NET [=y] && BRIDGE [=m]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> 802.1d Ethernet Bridging (BRIDGE [=m])

---

Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:15 -04:00
Justin M. Forbes e26dff1547 Fix USB_XHCI_PCI regression
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:15 -04:00
Peter Robinson f0c113f2cc fedora: fixes for ARMv7 build issue by disabling HIGHPTE
In RHBZ 1576593 we had issues with ARMv7 builders pausing, it turned out to be a
silicon bug and we could work around it by disabling HIGHPTE. For some reason
that workaround was lost in the 5.7-rc1 merge.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:15 -04:00
Justin M. Forbes 146ba399ed Change email address for Justin Forbes
As RHMAINTAINERS is used for mapping acks and such. I would rather
change it to use the jforbes@fedoraproject.org address that I use for
commits and such.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:15 -04:00
Fedora Kernel Team fcc04a4b42 [redhat] New configs in drivers/char
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HW_RANDOM_XIPHERA:

 This driver provides kernel-side support for Xiphera True Random
 Number Generator Intellectual Property Core.

 To compile this driver as a module, choose M here: the
 module will be called xiphera-trng.

 Symbol: HW_RANDOM_XIPHERA [=n]
 Type  : tristate
 Defined at drivers/char/hw_random/Kconfig:529
   Prompt: Xiphera FPGA based True Random Number Generator support
   Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Hardware Random Number Generator Core support (HW_RANDOM [=y])

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:15 -04:00
Fedora Kernel Team a73ee48d2f [redhat] New configs in drivers/net/wireless
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ATH11K:

 This module adds support for Qualcomm Technologies 802.11ax family of
 chipsets.

 If you choose to build a module, it'll be called ath11k.

 Symbol: ATH11K [=n]
 Type  : tristate
 Defined at drivers/net/wireless/ath/ath11k/Kconfig:2
   Prompt: Qualcomm Technologies 802.11ax chipset support
   Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ATH [=y] && MAC80211 [=m] && HAS_DMA [=y] && CRYPTO_MICHAEL_MIC [=m]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless LAN (WLAN [=y])
           -> Atheros/Qualcomm devices (WLAN_VENDOR_ATH [=y])
 Selects: ATH_COMMON [=m] && QCOM_QMI_HELPERS [=n]

---

Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:15 -04:00
Dan Horák 8ed8310537 all: s390x: Increase CONFIG_PCI_NR_FUNCTIONS to 512 (#1888735)
CONFIG_PCI_NR_FUNCTIONS limits the number of PCI functions the kernel
can handle on s390. In some situations (e.g. with the ROCE Express
adapter in z15) the number of available functions can easily exceed the
the current maximum. Thus increase the limit to 512, which is also the
default upstream.

Signed-off-by: Dan Horák <dan@danny.cz>
CC: Philipp Rudo <prudo@redhat.com>
CC: Steve Best <sbest@redhat.com>
2021-08-30 14:30:15 -04:00
Fedora Kernel Team f52ce80d56 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:14 -04:00
Justin M. Forbes 067f461976 Fedora 5.11 configs pt 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:14 -04:00
Herton R. Krzesinski 09fef59a72 redhat: avoid conflict with mod-blacklist.sh and released_kernel defined
The spec file has a potential issue: when released_kernel is defined, the
secureboot_ppc.cer source definition will clash with mod-blacklist.sh
definition, as both are using Source17 in the kernel spec file. To avoid
that, change the source numbers for x509 and certificate files so they
don't collide.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:14 -04:00
Herton R. Krzesinski 94f58b68a8 redhat: handle certificate files conditionally as done for src.rpm
When we create the src.rpm, we don't need to copy all certificate files,
only a set of them are needed depending on the RELEASED_KERNEL status.
This is necessary because when you do a make dist-git, the script
rh-dist-git.sh will create a diff to compare what was copied against what
is on dist-git clone, and this report will be bogus if we copy uneeded
files (it'll show in the diff that some files are not in the dist-git
copy, since the src.rpm created doesn't contain all certificate files,
because it's conditionally added based on released_kernel value).

Also while at it, delete old certificate files (secureboot.cer,
securebootca.cer) which are not used anymore since last grub related
security update.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:30:14 -04:00
Denys Vlasenko 36d8cae33e specfile: add %{?_smp_mflags} to "make headers_install" in tools/testing/selftests
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
2021-08-30 14:30:14 -04:00
Denys Vlasenko 3561cceaf1 specfile: add %{?_smp_mflags} to "make samples/bpf/"
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
2021-08-30 14:30:14 -04:00
CKI Gitlab 0bbdd77178 [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AMD_PMC:

 The driver provides support for AMD Power Management Controller
 primarily responsible for S2Idle transactions that are driven from
 a platform firmware running on SMU. This driver also provides a debug
 mechanism to investigate the S2Idle transactions and failures.

 Say Y or M here if you have a notebook powered by AMD RYZEN CPU/APU.

 If you choose to compile this driver as a module the module will be
 called amd-pmc.

 Symbol: AMD_PMC [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:194
   Prompt: AMD SoC PMC driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---

 CONFIG_DELL_WMI_SYSMAN:

 This driver allows changing BIOS settings on many Dell machines from
 2018 and newer without the use of any additional software.

 To compile this driver as a module, choose M here: the module will
 be called dell-wmi-sysman.

 Symbol: DELL_WMI_SYSMAN [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:458
   Prompt: Dell WMI-based Systems management driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m] && DMI [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
 Selects: NLS [=y]

---

 CONFIG_INTEL_PMT_CLASS:

 The Intel Platform Monitoring Technology (PMT) class driver provides
 the basic sysfs interface and file hierarchy uses by PMT devices.

 For more information, see:
 <file:Documentation/ABI/testing/sysfs-class-intel_pmt>

 To compile this driver as a module, choose M here: the module
 will be called intel_pmt_class.

 Symbol: INTEL_PMT_CLASS [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:1371
   Prompt: Intel Platform Monitoring Technology (PMT) Class driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
 Selected by [n]:
   - INTEL_PMT_TELEMETRY [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]
   - INTEL_PMT_CRASHLOG [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]

---

 CONFIG_INTEL_PMT_CRASHLOG:

 The Intel Platform Monitoring Technology (PMT) crashlog driver provides
 access to hardware crashlog capabilities on devices that support the
 feature.

 To compile this driver as a module, choose M here: the module
 will be called intel_pmt_crashlog.

 Symbol: INTEL_PMT_CRASHLOG [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:1394
   Prompt: Intel Platform Monitoring Technology (PMT) Crashlog driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
 Selects: INTEL_PMT_CLASS [=n]

---

 CONFIG_INTEL_PMT_TELEMETRY:

 The Intel Platform Monitory Technology (PMT) Telemetry driver provides
 access to hardware telemetry metrics on devices that support the
 feature.

 To compile this driver as a module, choose M here: the module
 will be called intel_pmt_telemetry.

 Symbol: INTEL_PMT_TELEMETRY [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:1383
   Prompt: Intel Platform Monitoring Technology (PMT) Telemetry driver
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
 Selects: INTEL_PMT_CLASS [=n]

---

 CONFIG_MLXBF_PMC:

 Say y here to enable PMC support. The PMC driver provides access
 to performance monitoring counters within various blocks in the
 Mellanox BlueField SoC via a sysfs interface.

 Symbol: MLXBF_PMC [=n]
 Type  : tristate
 Defined at drivers/platform/mellanox/Kconfig:59
   Prompt: Mellanox BlueField Performance Monitoring Counters driver
   Depends on: MELLANOX_PLATFORM [=y] && ARM64 [=y] && HWMON [=y] && ACPI [=y]
   Location:
     -> Device Drivers
       -> Platform support for Mellanox hardware (MELLANOX_PLATFORM [=y])

---

 CONFIG_SURFACE_GPE:

 This driver marks the GPEs related to the ACPI lid device found on
 Microsoft Surface devices as wakeup sources and prepares them
 accordingly. It is required on those devices to allow wake-ups from
 suspend by opening the lid.

 Symbol: SURFACE_GPE [=n]
 Type  : tristate
 Defined at drivers/platform/surface/Kconfig:43
   Prompt: Surface GPE/Lid Support Driver
   Depends on: SURFACE_PLATFORMS [=y] && ACPI [=y] && DMI [=y]
   Location:
     -> Device Drivers
       -> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y])

---

 CONFIG_SURFACE_PLATFORMS:

 Say Y here to get to see options for platform-specific device drivers
 for Microsoft Surface devices. This option alone does not add any
 kernel code.

 If you say N, all options in this submenu will be skipped and disabled.

 Symbol: SURFACE_PLATFORMS [=y]
 Type  : bool
 Defined at drivers/platform/surface/Kconfig:6
   Prompt: Microsoft Surface Platform-Specific Device Drivers
   Location:
     -> Device Drivers

---

Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:14 -04:00
CKI Gitlab 8e862a1d17 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_SOC_AMD_RENOIR_MACH:

 This option enables machine driver for DMIC

 Symbol: SND_SOC_AMD_RENOIR_MACH [=n]
 Type  : tristate
 Defined at sound/soc/amd/Kconfig:47
   Prompt: AMD Renoir support for DMIC
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_AMD_RENOIR [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> AMD Audio Coprocessor - Renoir support (SND_SOC_AMD_RENOIR [=m])
 Selects: SND_SOC_DMIC [=m]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:14 -04:00
Veronika Kabatova b34470546c Run MR testing in CKI pipeline
Updated to include schedule jobs and pages deployment (Don Zickus)

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-08-30 14:30:13 -04:00
Nicolas Chauvet b5c804c103 Reword comment 2021-08-30 14:30:13 -04:00
Nicolas Chauvet 6572bb3d80 Add with_cross_arm conditional
Copr only permits to use --with conditionals but no --target
This allows to cross compile the kernel and is specially relevant for arm

Signed-off-by: Nicolas Chauvet <kwizart@gmail.com>
2021-08-30 14:30:13 -04:00
Nicolas Chauvet 407b6b475d Redefines __strip if with_cross
Signed-off-by: Nicolas Chauvet <kwizart@gmail.com>
2021-08-30 14:30:13 -04:00
Patrick Talbert a6feae034c [redhat] Set CONFIG_SND_SOC_WM8804_I2C
!419 enabled CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH but missed also
setting CONFIG_SND_SOC_WM8804_I2C. Fix it.

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-08-30 14:30:13 -04:00
Fedora Kernel Team b819247b49 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_CORSAIR_PSU:

 If you say yes here you get support for Corsair PSUs with a HID
 interface.
 Currently this driver supports the (RM/HX)550i, (RM/HX)650i,
 (RM/HX)750i, (RM/HX)850i, (RM/HX)1000i and HX1200i power supplies
 by Corsair.

 This driver can also be built as a module. If so, the module
 will be called corsair-psu.

 Symbol: SENSORS_CORSAIR_PSU [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:452
   Prompt: Corsair PSU HID controller
   Depends on: HWMON [=y] && HID [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

 CONFIG_SENSORS_LTC2992:

 If you say yes here you get support for Linear Technology LTC2992
 I2C System Monitor. The LTC2992 measures current, voltage, and
 power of two supplies.

 This driver can also be built as a module. If so, the module will
 be called ltc2992.

 Symbol: SENSORS_LTC2992 [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:874
   Prompt: Linear Technology LTC2992
   Depends on: HWMON [=y] && I2C [=y] && GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

 CONFIG_SENSORS_MAX127:

 Say y here to support Maxim's MAX127 DAS chips.

 This driver can also be built as a module. If so, the module
 will be called max127.

 Symbol: SENSORS_MAX127 [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:965
   Prompt: Maxim MAX127 12-bit 8-channel Data Acquisition System
   Depends on: HWMON [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

 CONFIG_SENSORS_PM6764TR:

 If you say yes here you get hardware monitoring support for ST
 PM6764TR.

 This driver can also be built as a module. If so, the module will
 be called pm6764tr.

 Symbol: SENSORS_PM6764TR [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:223
   Prompt: ST PM6764TR
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_Q54SJ108A2:

 If you say yes here you get hardware monitoring support for Delta
 Q54SJ108A2 series Power Supplies.

 This driver can also be built as a module. If so, the module will
 be called q54sj108a2.

 Symbol: SENSORS_Q54SJ108A2 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:241
   Prompt: Delta Power Supplies Q54SJ108A2
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_SBTSI:

 If you say yes here you get support for emulated temperature
 sensors on AMD SoCs with SB-TSI interface connected to a BMC device.

 This driver can also be built as a module. If so, the module will
 be called sbtsi_temp.

 Symbol: SENSORS_SBTSI [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:1536
   Prompt: Emulated SB-TSI temperature sensor
   Depends on: HWMON [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:13 -04:00
Ben Crocker 85e676db9d [redhat] genspec.sh: fix lasttag/MARKER logic
Fix the lasttag/MARKER logic ca. lines 40ff.: if MARKER
is a SHA1 (i.e. pure hexadecimal number), then

lasttag=$(git describe --match="$MARKER" --abbrev=0)

results in

fatal: No names found, cannot describe anything.

Once the new if-block is executed, lasttag will always have
a non-null value, so the second 'if [ -z "$lasttag" ]' will
never be executed and can be dropped.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:13 -04:00
Ben Crocker a7a3baf0c9 [redhat] self-test/2001-dist-release.bats
New self test to check consistency of version amongst
commit log, Makefile.rhelver, and changelog.

* Test 1:

Performing

% make dist-release

more than once in succession results in only one commit remaining in
the log.

* Test 2:

Release # in commit message matches release # in Makefile.rhelver

* Test 3:

Release # in commit message matches release # in change log.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:13 -04:00
Peter Robinson 8bfdcbc839 fedora: only enable ACPI_CONFIGFS, ACPI_CUSTOM_METHOD in debug kernels
Like ARK does only enable these options in debug kernels, there's security
implications in particular for the later option, and they're not options
for day to day use.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Cc: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:12 -04:00
Peter Robinson 7ae4eaf024 fedora: User the same EFI_CUSTOM_SSDT_OVERLAYS as ARK
Fedora already enables ACPI_TABLE_UPGRADE so EFI_CUSTOM_SSDT_OVERLAYS doesn't
add much, it's also disabled when the kernels locked down such as for
secure boot.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:12 -04:00
Peter Robinson 3569c113ff all: all arches/kernels enable the same DMI options
No functional change, all EFI platforms enable the same DMI options
so move them to common.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:12 -04:00
Peter Robinson 33914c4ba2 all: move SENSORS_ACPI_POWER to common/generic
This is modular on Fedora x86/aarch64 and ARK x86, but it's built-in
on ARK aarch64 which doesn't really make sense as it's an ACPI rev4
spec and aarch64 was only supported in ACPI 5.1 (reduced hardware model)
so it's likely it's never been supported on shipping hardware so let's
make it modular there like everywhere else.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
2021-08-30 14:30:12 -04:00
Peter Robinson 6f7315344e fedora: PCIE_HISI_ERR is already in common
No chnage, just removes an option already set the same in common

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:12 -04:00
Peter Robinson f9651f442f all: all ACPI platforms enable ATA_ACPI so move it to common
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:12 -04:00
Peter Robinson 9fa59d55a2 all: x86: move shared x86 acpi config options to generic
No functional change, just move the x86 acpi configs that Fedora/ARK
share to the common location.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:11 -04:00
Peter Robinson 4fb59dccd5 All: x86: Move ACPI_VIDEO to common/x86
No chnage, just de-dupes the Fedora/ARK options

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:11 -04:00
Peter Robinson 08912eba5a All: x86: Enable ACPI_DPTF (Intel DPTF)
Enable the Intel Dynamic Platform and Thermal Framework on all
x86 kernels, and sync the sub components in common/generic/x86.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:11 -04:00
Peter Robinson d2f032836c All: enable ACPI_BGRT for all ACPI platforms.
This only actually changes ACPI_BGRT for ark:aarch64, all
others enabled it. We want this for ark:aarch64 too as we have
upcoming aarch64 edge devices that will support this and it's
useful for boot/firmware updates.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
2021-08-30 14:30:11 -04:00
Peter Robinson b30547462c All: Only build ACPI_EC_DEBUGFS for debug kernels
As per the Kconfig help ACPI_EC_DEBUGFS is for poking at the
system's Embedded Controller via a /sys/kernel/debug interface
and we really shouldn't encourage this for standard use as it's
explicitly designed for debugging drivers/hardware.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:11 -04:00
Peter Robinson e6de9f581c All: Disable Intel Classmate PC ACPI_CMPC option
The Intel Classmate PC's were x86-32 only with the last generation
being a first gen Atom. This option is hence unused across all
kernels.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:10 -04:00
Peter Robinson 9cb034d0dd cleanup: ACPI_PROCFS_POWER was removed upstream
No change as ACPI_PROCFS_POWER was removed in upstream
commit 8830280 in May 2020

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:10 -04:00
Peter Robinson 7bf250d1e2 All: ACPI: De-dupe the ACPI options that are the same across ark/fedora on x86/arm
There's a mass duplications of ACPI options across aarch64/x86 on both Fedora
and ARK kernels. Moving them into common doesn't affect non ACPI arches as
all the options are under the ACPI menu which only gets selected if the arch
presents ARCH_SUPPORTS_ACPI and some options were already in common/geneic.

There's no functional change here, this is purely de-dupe.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:10 -04:00
Jeremy Cline abc2f165c4 Enable the vkms module in Fedora
This is built as a module on RHEL and is useful for testing and for
running X (or similar) on headless machines.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:30:10 -04:00
Guillaume Nault bb90c1a455 RHMAINTAINERS: NETWORKING: Add entry for Antoine Tenart
Antoine is now part of the networking team.

RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Hangbin Liu <haliu@redhat.com>
RH-Acked-by: Antoine Tenart <atenart@redhat.com>

Acked-by: Antoine Tenart <atenart@redhat.com>
Signed-off-by: Guillaume Nault <gnault@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:10 -04:00
Brian Masney c3c4c1899c add ARK kernel maintainer and reviewer
Add Patrick Talbert as an ARK kernel maintainer and Don Zickus as a
reviewer.

[prarit: dzickus was added in a previous patch]

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>

Signed-off-by: Brian Masney <bmasney@redhat.com>
CC: Justin Forbes <jforbes@redhat.com>
CC: Patrick Talbert <ptalbert@redhat.com>
CC: Don Zickus <dzickus@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:10 -04:00
Brian Masney c9acd4735a add dzickus as a reviewer for ARK redhat/ directory
Let's make it official and add Don Zickus as a reviewer for ARK's
redhat/ directory.

RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

Signed-off-by: Brian Masney <bmasney@redhat.com>
CC: Donald Zickus <dzickus@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:10 -04:00
Prarit Bhargava bb97c3596b RHMAINTAINERS: Remove dead email addresses
viskulka and zyan are no longer at Red Hat.

RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Ilya Dryomov <idryomov@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Ilya Dryomov <idryomov@redhat.com>
Cc: John W. Linville <linville@redhat.com>
2021-08-30 14:30:09 -04:00
Prarit Bhargava 0a88f6b303 RHMAINTAINERS: Add coverage for arch/Kconfig
Configs listed in arch/Kconfig are not covered in RHMAINTAINERS.  Add the
arch maintainers to cover this file.

RH-Acked-by: Mark Salter <msalter@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Steve Best <sbest@redhat.com>
2021-08-30 14:30:09 -04:00
Vitaly Kuznetsov 3bda23e1d6 RHMAINTAINERS: Add AWS Nitro Enclaves
Adding AWS Nitro Enclaves driver to the 'RHEL on third party hypervisors
and public clouds' team's responsibilities.

RH-Acked-by: Mohammed Gamal <mgamal@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:09 -04:00
CKI Gitlab 51192141c7 [redhat] New configs in arch/x86
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_X86_SGX:

 Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
 that can be used by applications to set aside private regions of code
 and data, referred to as enclaves. An enclave's private memory can
 only be accessed by code running within the enclave. Accesses from
 outside the enclave, including other enclaves, are disallowed by
 hardware.

 If unsure, say N.

 Symbol: X86_SGX [=n]
 Type  : bool
 Defined at arch/x86/Kconfig:1937
   Prompt: Software Guard eXtensions (SGX)
   Depends on: X86_64 [=y] && CPU_SUP_INTEL [=y] && CRYPTO [=y]=y && CRYPTO_SHA256 [=y]=y
   Location:
     -> Processor type and features
 Selects: SRCU [=y] && MMU_NOTIFIER [=y]

---

Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:09 -04:00
Fedora Kernel Team 42f7e586ee [redhat] AUTOMATIC: New configs 2021-08-30 14:30:09 -04:00
Fedora Kernel Team e6ea4272de [redhat] New configs in drivers/xen
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_XEN_UNPOPULATED_ALLOC:

 Use unpopulated memory ranges in order to create mappings for guest
 memory regions, including grant maps and foreign pages. This avoids
 having to balloon out RAM regions in order to obtain physical memory
 space to create such mappings.

 Symbol: XEN_UNPOPULATED_ALLOC [=n]
 Type  : bool
 Defined at drivers/xen/Kconfig:328
   Prompt: Use unpopulated memory ranges for guest mappings
   Depends on: XEN [=y] && X86 [=y] && ZONE_DEVICE [=y]
   Location:
     -> Device Drivers
       -> Xen driver support

---

Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:09 -04:00
CKI Gitlab 9e267a6ab5 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_SOC_ADI:

 Audio support for various reference designs by Analog Devices.

 Symbol: SND_SOC_ADI [=n]
 Type  : tristate
 Defined at sound/soc/adi/Kconfig:2
   Prompt: Audio support for Analog Devices reference designs
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])

---

 CONFIG_SND_SOC_FSL_XCVR:

 Say Y if you want to add Audio Transceiver (XCVR) support for NXP
 iMX CPUs. XCVR is a digital module that supports HDMI2.1 eARC,
 HDMI1.4 ARC and SPDIF.

 Symbol: SND_SOC_FSL_XCVR [=n]
 Type  : tristate
 Defined at sound/soc/fsl/Kconfig:98
   Prompt: NXP Audio Transceiver (XCVR) module support
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> SoC Audio for Freescale CPUs
 Selects: REGMAP_MMIO [=n] && SND_SOC_IMX_PCM_DMA [=n] && SND_SOC_GENERIC_DMAENGINE_PCM [=n]

---

 CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT:

 This adds support for Sound Open Firmware for Intel(R) platforms
 using the Alderlake processors.
 Say Y if you have such a device.
 If unsure select "N".

 Symbol: SND_SOC_SOF_ALDERLAKE_SUPPORT [=n]
 Type  : bool
 Defined at sound/soc/sof/intel/Kconfig:274
   Prompt: SOF support for Alderlake
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
               -> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y])

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:09 -04:00
Jeremy Cline 59a9ffdcd8 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_SOC_AMD_RENOIR:

 This option enables ACP support for Renoir platform

 Symbol: SND_SOC_AMD_RENOIR [=n]
 Type  : tristate
 Defined at sound/soc/amd/Kconfig:40
   Prompt: AMD Audio Coprocessor - Renoir support
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && X86 [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])

---

 CONFIG_SND_SOC_INTEL_EHL_RT5660_MACH:

 This adds support for ASoC machine driver for Elkhart Lake
 platform with RT5660 I2S audio codec.

 Symbol: SND_SOC_INTEL_EHL_RT5660_MACH [=n]
 Type  : tristate
 Defined at sound/soc/intel/boards/Kconfig:545
   Prompt: EHL with RT5660 in I2S mode
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && SND_SOC_SOF_ELKHARTLAKE [=m] && I2C [=y] && ACPI [=y] && GPIOLIB [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n]) && SND_HDA_CODEC_HDMI [=m] && SND_SOC_SOF_HDA_AUDIO_CODEC [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
 Selects: SND_SOC_RT5660 [=m] && SND_SOC_DMIC [=m]

---

 CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH:

 This adds support for ASoC machine driver for Intel platforms
 with the Wolfson/Cirrus WM8804 I2S audio codec.
 Say Y or m if you have such a device. This is a recommended option.
 If unsure select "N".

 Symbol: SND_SOC_INTEL_SOF_WM8804_MACH [=n]
 Type  : tristate
 Defined at sound/soc/intel/boards/Kconfig:329
   Prompt: SOF with Wolfson/Cirrus WM8804 codec
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && SND_SOC_SOF_APOLLOLAKE [=m] && I2C [=y] && ACPI [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
 Selects: SND_SOC_WM8804_I2C [=n]

---

 CONFIG_SND_SOC_ZL38060:

 Support for ZL38060 Connected Home Audio Processor from Microsemi,
 which consists of a Digital Signal Processor (DSP), several Digital
 Audio Interfaces (DAIs), analog outputs, and a block of 14 GPIOs.

 Symbol: SND_SOC_ZL38060 [=n]
 Type  : tristate
 Defined at sound/soc/codecs/Kconfig:1660
   Prompt: Microsemi ZL38060 Connected Home Audio Processor
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> CODEC drivers
 Selects: GPIOLIB [=y] && REGMAP [=y]
 Implied by [n]:
   - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:08 -04:00
Peter Robinson 8ae258511c Fedora: arm updates for 5.11 and general cross Fedora cleanups
Updates for the arm architectures for 5.11, some cleanups of general
Fedora arch configs.

Deletion of some old/obsolete configs. No functional changes to non
Fedora specific configs.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:08 -04:00
Justin M. Forbes b930c3cf8e Add gcc-c++ to BuildRequires
This is required for some of the gcc plugins.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:08 -04:00
Justin M. Forbes 4992742ebb Update CONFIG_KASAN_HW_TAGS
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:08 -04:00
Peter Robinson 52dc2619ea fedora: arm: move generic power off/reset to all arm
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:08 -04:00
Peter Robinson 4e0b1f90ee fedora: ARMv7: build in DEVFREQ_GOV_SIMPLE_ONDEMAND until I work out why it's changed
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:08 -04:00
Peter Robinson 12f0b756c3 fedora: cleanup joystick_adc
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:08 -04:00
Peter Robinson f0352f6338 fedora: update some display options
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:08 -04:00
Peter Robinson 2dedf338f0 fedora: arm: enable TI PRU options
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:07 -04:00
Peter Robinson a1254e59d6 fedora: arm: minor exynos plaform updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:07 -04:00
Peter Robinson 5e5396c1f7 arm: SoC: disable Toshiba Visconti SoC 2021-08-30 14:30:07 -04:00
Peter Robinson 277c70323a common: disable ARCH_BCM4908 (NFC)
The ARCH_BCM4908 option is in pending and fedora and disabled in both.
These SOCs are used in home WiFi routers and we won't currently support
them anywhere.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:07 -04:00
Peter Robinson d92739136b fedora: minor arm config updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:07 -04:00
Peter Robinson 48aeeeeca6 fedora: enable Tegra 234 SoC
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:07 -04:00
Peter Robinson 3ccd1e04d0 fedora: arm: enable new Hikey 3xx options
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:06 -04:00
Peter Robinson 4e5312702f Fedora: USB updates
Build the Cadence USB3 controller for Arm, the Renasas PCI XHCI
controller as a module, minor other cleanups

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:06 -04:00
Peter Robinson 6bd4631940 fedora: enable the GNSS receiver subsystem
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:06 -04:00
Peter Robinson 436960c4c4 Remove POWER_AVS as no longer upstream
Only affects Fedora but all the AVS drivers have been moved
to SoC specific drivers so there's no functional change.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:06 -04:00
Peter Robinson 0c2fffd0aa Cleanup RESET_RASPBERRYPI
We want this for Fedora so clean up this config

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:06 -04:00
Peter Robinson d7d10408dc Cleanup GPIO_CDEV_V1 options.
Don't set it in generic as enterprise never enabled v1 like
Fedora has has. Leave it on in Fedora for the time being
even though the libgpiod tools support v2.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:06 -04:00
Peter Robinson f2c23ed94e fedora: arm crypto updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:06 -04:00
Justin M. Forbes 8903f7e506 CONFIG_KASAN_HW_TAGS for aarch64
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:06 -04:00
Peter Robinson a89609ae6a Fedora: cleanup PCMCIA configs, move to x86
None of the Fedora architectures other than x86 support PCMCIA cards
and arm/s390 arches had already disabled the support, as had ARK in
general so move all the configs to reside in fedora/x86 as it's
config would actually be the only consumers of the drivers now.

No functional change to non Fedora configs.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-08-30 14:30:05 -04:00
Fedora Kernel Team 8207e2c2da [redhat] AUTOMATIC: New configs 2021-08-30 14:30:05 -04:00
Fedora Kernel Team f91695ee73 [redhat] New configs in drivers/ptp
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PTP_1588_CLOCK_OCP:

 This driver adds support for an OpenCompute time card.

 The OpenCompute time card is an atomic clock along with
 a GPS receiver that provides a Grandmaster clock source
 for a PTP enabled network.

 More information is available at http://www.timingcard.com/

 Symbol: PTP_1588_CLOCK_OCP [=n]
 Type  : tristate
 Defined at drivers/ptp/Kconfig:154
   Prompt: OpenCompute TimeCard as PTP clock
   Depends on: PTP_1588_CLOCK [=y] && HAS_IOMEM [=y] && PCI [=y]
   Location:
     -> Device Drivers
       -> PTP clock support

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:05 -04:00
Fedora Kernel Team 7867b034ed [redhat] New configs in drivers/crypto
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CRYPTO_DEV_HISI_TRNG:

 Support for HiSilicon TRNG Driver.

 Symbol: CRYPTO_DEV_HISI_TRNG [=n]
 Type  : tristate
 Defined at drivers/crypto/hisilicon/Kconfig:75
   Prompt: Support for HISI TRNG Driver
   Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && ARM64 [=y] && ACPI [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Hardware crypto devices (CRYPTO_HW [=y])
 Selects: HW_RANDOM [=y] && CRYPTO_RNG [=y]

---

 CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4:

 Support for Intel Keem Bay Offload and Crypto Subsystem (OCS) AES and
 SM4 cihper hardware acceleration for use with Crypto API.

 Provides HW acceleration for the following transformations:
 cbc(aes), ctr(aes), ccm(aes), gcm(aes), cbc(sm4), ctr(sm4), ccm(sm4)
 and gcm(sm4).

 Optionally, support for the following transformations can also be
 enabled: ecb(aes), cts(cbc(aes)), ecb(sm4) and cts(cbc(sm4)).

 Symbol: CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 [=n]
 Type  : tristate
 Defined at drivers/crypto/keembay/Kconfig:1
   Prompt: Support for Intel Keem Bay OCS AES/SM4 HW acceleration
   Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && (OF [=y] || COMPILE_TEST [=n])
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Hardware crypto devices (CRYPTO_HW [=y])
 Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_AEAD [=y] && CRYPTO_ENGINE [=n]

---

 CONFIG_CRYPTO_DEV_QAT_4XXX:

 Support for Intel(R) QuickAssist Technology QAT_4xxx
 for accelerating crypto and compression workloads.

 To compile this as a module, choose M here: the module
 will be called qat_4xxx.

 Symbol: CRYPTO_DEV_QAT_4XXX [=n]
 Type  : tristate
 Defined at drivers/crypto/qat/Kconfig:49
   Prompt: Support for Intel(R) QAT_4XXX
   Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && X86 [=y] && PCI [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Hardware crypto devices (CRYPTO_HW [=y])
 Selects: CRYPTO_DEV_QAT [=m]

---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:05 -04:00
Fedora Kernel Team a6aacf728f [redhat] New configs in arch/x86
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_XEN_PVHVM_GUEST:

 Support running as a Xen PVHVM guest.

 Symbol: XEN_PVHVM_GUEST [=y]
 Type  : bool
 Defined at arch/x86/xen/Kconfig:62
   Prompt: Xen PVHVM guest support
   Depends on: HYPERVISOR_GUEST [=y] && XEN_PVHVM [=y] && PCI [=y]
   Location:
     -> Processor type and features
       -> Linux guest support (HYPERVISOR_GUEST [=y])
         -> Xen guest support (XEN [=y])

---

Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:05 -04:00
Fedora Kernel Team 5cf63e8b2b [redhat] New configs in arch/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_STATIC_CALL_SELFTEST:

 Boot time self-test of the call patching code.

 Symbol: STATIC_CALL_SELFTEST [=n]
 Type  : bool
 Defined at arch/Kconfig:109
   Prompt: Static call selftest
   Depends on: HAVE_STATIC_CALL [=y]
   Location:
     -> General architecture-dependent options

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:05 -04:00
Fedora Kernel Team af7880e85f [redhat] AUTOMATIC: New configs 2021-08-30 14:30:04 -04:00
Fedora Kernel Team f25ec222b3 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:04 -04:00
Fedora Kernel Team e64923a42c New configs in drivers/rtc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RTC_DRV_RV3032:

 If you say yes here you get support for the Micro Crystal
 RV3032.

 This driver can also be built as a module. If so, the module
 will be called rtc-rv3032.

 Symbol: RTC_DRV_RV3032 [=n]
 Type  : tristate
 Defined at drivers/rtc/Kconfig:672
   Prompt: Micro Crystal RV3032
   Depends on: RTC_CLASS [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Real Time Clock (RTC_CLASS [=y])
 Selects: REGMAP_I2C [=m]

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
2021-08-30 14:30:04 -04:00
Jeremy Cline e719e77098 [redhat] New configs in drivers/i2c
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_I2C_MLXBF:

 Enabling this option will add I2C SMBus support for Mellanox BlueField
 system.

 This driver can also be built as a module. If so, the module will be
 called i2c-mlxbf.

 This driver implements an I2C SMBus host controller and enables both
 master and slave functions.

 Symbol: I2C_MLXBF [=n]
 Type  : tristate
 Defined at drivers/i2c/busses/Kconfig:734
   Prompt: Mellanox BlueField I2C controller
   Depends on: I2C [=y] && HAS_IOMEM [=y] && ARM64 [=y]
   Location:
     -> Device Drivers
       -> I2C support
         -> I2C support (I2C [=y])
           -> I2C Hardware Bus support

---

 CONFIG_I2C_SLAVE_TESTUNIT:

 This backend can be used to trigger test cases for I2C bus masters
 which require a remote device with certain capabilities, e.g.
 multi-master, SMBus Host Notify, etc. Please read
 Documentation/i2c/slave-testunit-backend.rst for further details.

 Symbol: I2C_SLAVE_TESTUNIT [=n]
 Type  : tristate
 Defined at drivers/i2c/Kconfig:128
   Prompt: I2C eeprom testunit driver
   Depends on: I2C [=y] && I2C_SLAVE [=y]
   Location:
     -> Device Drivers
       -> I2C support
         -> I2C support (I2C [=y])
           -> I2C slave support (I2C_SLAVE [=y])

---

Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:04 -04:00
Josh Poimboeuf 45fe7667bd redhat/configs: Enable CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL
Enable CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL for both fedora and ARK.
This prevents a lot of uninitialized stack variable exploits, with a
minimal impact on performance.

This feature is incompatible with CONFIG_KASAN, so it can't be enabled
on debug kernels.

Also, it's mutually exclusive with CONFIG_INIT_STACK_NONE=y.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856176
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
2021-08-30 14:30:04 -04:00
Josh Poimboeuf c4fd93c565 redhat/configs: Enable CONFIG_GCC_PLUGIN_STRUCTLEAK
This will be needed for CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856176
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
2021-08-30 14:30:04 -04:00
Josh Poimboeuf 4f367b1214 redhat/configs: Enable CONFIG_GCC_PLUGINS on ARK
Enable CONFIG_GCC_PLUGINS on ARK so CONFIG_GCC_PLUGIN_STRUCTLEAK can be
enabled.

Fedora already has CONFIG_GCC_PLUGINS, so move it to the common
directory so it can be shared with ARK.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856176
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
2021-08-30 14:30:04 -04:00
Josh Poimboeuf a923cc443d redhat/configs: Enable CONFIG_KASAN on Fedora
KASAN is useful for finding bugs.  Enable it in the Fedora debug kernel
for x86 and arm64, for consistency with ARK.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1856176
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
2021-08-30 14:30:03 -04:00
Fedora Kernel Team fb291e0cb7 [redhat] New configs in arch/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SECCOMP_CACHE_DEBUG:

 This enables the /proc/pid/seccomp_cache interface to monitor
 seccomp cache data. The file format is subject to change. Reading
 the file requires CAP_SYS_ADMIN.

 This option is for debugging only. Enabling presents the risk that
 an adversary may be able to infer the seccomp filter logic.

 If unsure, say N.

 Symbol: SECCOMP_CACHE_DEBUG [=n]
 Type  : bool
 Defined at arch/Kconfig:520
   Prompt: Show seccomp filter cache status in /proc/pid/seccomp_cache
   Depends on: SECCOMP_FILTER [=y] && !HAVE_SPARSE_SYSCALL_NR [=n] && PROC_FS [=y]
   Location:
     -> General architecture-dependent options
       -> Enable seccomp to safely execute untrusted bytecode (SECCOMP [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:03 -04:00
Fedora Kernel Team bc1977b52d New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KERNEL_ZSTD:

 ZSTD is a compression algorithm targeting intermediate compression
 with fast decompression speed. It will compress better than GZIP and
 decompress around the same speed as LZO, but slower than LZ4. You
 will need at least 192 KB RAM or more for booting. The zstd command
 line tool is required for compression.

 Symbol: KERNEL_ZSTD [=n]
 Type  : bool
 Defined at init/Kconfig:282
   Prompt: ZSTD
   Depends on: <choice> && HAVE_KERNEL_ZSTD [=y]
   Location:
     -> General setup
       -> Kernel compression mode (<choice> [=y])

Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:03 -04:00
Ben Crocker 9ab5e4c477 build_configs.sh: Fix syntax flagged by shellcheck
SC2001: See if you can use ${variable//search/replace} instead.
SC2046: Quote this to prevent word splitting.
SC2086: Double quote to prevent globbing and word splitting.
SC2162: read without -r will mangle backslashes.
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.

Disable:
SC2010: Don't use ls | grep. Use a glob or a for loop with a condition to allow non-alphanumeric filenames.
as any alternative is worse, i.e. harder to understand.  Filenames are known
to be well-formed (i.e. no blanks or special characters) in our situation.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:03 -04:00
Ben Crocker e469e8640d genspec.sh: Fix syntax flagged by shellcheck
SC2002: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead.
SC2086: Double quote to prevent globbing and word splitting.
SC2196: egrep is non-standard and deprecated. Use grep -E instead.
SC2034: <variable; in this case, STAMP> appears unused.

Change to #!/bin/bash explicitly to allow
SC2039: bash-isms

Eliminate a couple of MS-DOS-era archaisms.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:03 -04:00
Ben Crocker b2f4d3c7aa [redhat] ark-rebase-patches.sh: Fix for shellcheck
Changes actually consist of disabling shellcheck on a few lines:
• SC2086: Double quote to prevent globbing and word splitting.
• SC2059: Don't use variables in the printf format string. Use printf...

For the former, in the two gitlab commands involved,
GITLAB_CONFIG_OPT DEPENDS on word splitting.
For the latter, the ShellCheck wiki actually recommend disabling the warning
because a multi-line pattern is in use and there is no good rewrite.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:03 -04:00
Ben Crocker cc750b7018 [redhat] ark-create-release.sh: Fix syntax flagged by shellcheck
Fix syntax flagged by shellcheck:
SC2086: Double quote to prevent globbing and word splitting.

(There is only one instance.)

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:03 -04:00
Ben Crocker a0cdf2a410 [redhat] merge-subtrees.sh: Fix syntax flagged by shellcheck
SC2162: read without -r will mangle backslashes
SC2086: Double quote to prevent globbing and word splitting

Rewrote main loop so it will work.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>

merge-subtrees.h: fix

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:03 -04:00
Ben Crocker 497bf60763 [redhat] rh-dist-git.sh: Fix syntax flagged by shellcheck
SC2086: Double quote to prevent globbing and word splitting.
SC2145: Argument mixes string and array. Use * or separate argument.

SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:03 -04:00
Ben Crocker f0169a781a [redhat] update_scripts.sh: Fix syntax flagged by shellcheck
SC2231: Quote expansions in this for loop glob to prevent wordsplitting.
SC2086: Double quote to prevent globbing and word splitting.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker 4ceb39cebe [redhat] x86_rngd.sh: Fix syntax flagged by shellcheck
SC2039: bash-isms
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker af994b7205 [redhat] parallel_xz.sh: Fix syntax flagged by shellcheck
SC2086: Double quote to prevent globbing and word splitting.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker 3843b6f0b4 [redhat] expand_srpm.sh: Fix syntax flagged by shellcheck
SC2034: tree appears unused. Verify use (or export if used externally).
SC2035: Use ./*glob* or -- *glob* so names with dashes won't become options.
SC2086: Double quote to prevent globbing and word splitting.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker ee0750cb0b [redhat] create-tarball.sh: Fix syntax flagged by shellcheck
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC1083: This { is literal. Check expression (missing ;/\n?) or quote it.
SC2086: Double quote to prevent globbing and word splitting.

BUT:
Disable shellcheck on last step:

On the last step, we DEPEND on word splitting for correct interpretation
of XZ_OPTIONS and XZ_THREADS, so remove quotes and, just before the
xz step:

  shellcheck disable=SC2086

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker ad8abd1f40 [redhat] generate_bls_conf.sh: Fix syntax flagged by shellcheck
SC2086: Double quote to prevent globbing and word splitting.

Ignoring:
SC1091: Not following: /etc/os-release was not specified as input (see shellcheck -x).
SC2154: bootprefix is referenced but not assigned.
It is perfectly OK for bootprefix not to be assigned in this script.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker 1302e06199 [redhat] clone_tree.sh: Fix syntax flagged by shellcheck
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2013: To read lines rather than words, pipe/redirect to a 'while read' loop.
SC2086: Double quote to prevent globbing and word splitting.
SC2166: Prefer [ p ] && [ q ] as [ p -a q ] is not well defined.
EVEN BETTER: use [[ p || q ]]

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker e32b352bbf [redhat] new_release.sh: Fix syntax flagged by shellcheck
SC2007: Use $((..)) instead of deprecated $[..]
SC2086: Double quote to prevent globbing and word splitting.
SC2166: Prefer [ p ] || [ q ] as [ p -o q ] is not well defined.
EVEN BETTER: use [[ p || q ]].

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker d1e58e304e [redhat] download_cross.sh: Fix syntax flagged by shellcheck
SC2068: Double quote array expansions to avoid re-splitting elements.
SC2086: Double quote to prevent globbing and word splitting.
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker ae29e046c2 [redhat] create_distgit_changelog.sh: Fix syntax flagged by shellcheck
SC2002: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead.
SC2086: Double quote to prevent globbing and word splitting.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker bc92957ac7 [redhat] generate_cross_report.sh: Fix syntax flagged by shellcheck
SC2002: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead.
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2086: Double quote to prevent globbing and word splitting.
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly with $?.

Disable by changing to #!/bin/bash:

SC2039: In POSIX sh, echo flags are undefined.
SC2039: In POSIX sh, >& is undefined.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:02 -04:00
Ben Crocker 7df2f886a7 [redhat] run_kabi-dw.sh: Fix syntax flagged by shellcheck
SC2039: In POSIX sh, == in place of = is undefined.
SC2086: Double quote to prevent globbing and word splitting.

Ignore:
SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.

Also, change 'if..elif..else..fi' block to case..esac.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:01 -04:00
Ben Crocker 59abbbbbf0 mod-blacklist.sh: Fix syntax flagged by shellcheck
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2013: To read lines rather than words, pipe/redirect to a 'while read' loop. ???
SC2086: Double quote to prevent globbing and word splitting.
SC2144: -f doesn't work with globs. Use a for loop.
SC2155: Declare and assign separately to avoid masking return values. ???
SC2162: read without -r will mangle backslashes.
SC2236: Use -z instead of ! -n.

Disable:
SC2164: Use 'pushd ... || exit' or 'pushd ... || return' in case pushd fails.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:01 -04:00
Ben Crocker e33f06c615 [redhat] scripts/configdiff.sh: Fix syntax flagged by shellcheck
SC2001: See if you can use ${variable//search/replace} instead.
SC2045: Iterating over ls output is fragile. Use globs.
SC2046: Quote this (command) to prevent word splitting.
SC2086: Double quote to prevent globbing and word splitting.
SC2162: read without -r will mangle backslashes.
SC2231: Quote expansions in this for loop glob to prevent wordsplitting, e.g. "$dir"/*.txt .

Also, change to #!/bin/bash so bash-isms won't be flagged, e.g.

SC2039: In POSIX sh, [[ ]] is undefined.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:30:01 -04:00
Justin M. Forbes a062c27891 Enable Speakup accessibility driver
The Speakup accessiblility driver is no longer in staging as of 5.9, and is a useful accessibility tool. This enables Speakup core, and all of the synth drivers which do not depend on ISA. More information can be found at http://www.linux-speakup.org/

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:01 -04:00
Fedora Kernel Team 0198792098 New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEFAULT_INIT:

 This option determines the default init for the system if no init=
 option is passed on the kernel command line. If the requested path is
 not present, we will still then move on to attempting further
 locations (e.g. /sbin/init, etc). If this is empty, we will just use
 the fallback list when init= is not passed.

 Symbol: DEFAULT_INIT [=]
 Type  : string
 Defined at init/Kconfig:267
   Prompt: Default init path
   Location:
     -> General setup

Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:30:01 -04:00
CKI Gitlab a105795c21 [redhat] New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_ALDERLAKE:

 This pinctrl driver provides an interface that allows configuring
 of Intel Alder Lake PCH pins and using them as GPIOs.

 Symbol: PINCTRL_ALDERLAKE [=n]
 Type  : tristate
 Defined at drivers/pinctrl/intel/Kconfig:58
   Prompt: Intel Alder Lake pinctrl and GPIO driver
   Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_INTEL [=y]

---

 CONFIG_PINCTRL_ELKHARTLAKE:

 This pinctrl driver provides an interface that allows configuring
 of Intel Elkhart Lake SoC pins and using them as GPIOs.

 Symbol: PINCTRL_ELKHARTLAKE [=n]
 Type  : tristate
 Defined at drivers/pinctrl/intel/Kconfig:98
   Prompt: Intel Elkhart Lake SoC pinctrl and GPIO driver
   Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_INTEL [=y]

---

 CONFIG_PINCTRL_LAKEFIELD:

 This pinctrl driver provides an interface that allows configuring
 of Intel Lakefield SoC pins and using them as GPIOs.

 Symbol: PINCTRL_LAKEFIELD [=n]
 Type  : tristate
 Defined at drivers/pinctrl/intel/Kconfig:138
   Prompt: Intel Lakefield SoC pinctrl and GPIO driver
   Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_INTEL [=y]

---

 CONFIG_PINCTRL_LPASS_LPI:

 This is the pinctrl, pinmux, pinconf and gpiolib driver for the
 Qualcomm Technologies Inc LPASS (Low Power Audio SubSystem) LPI
 (Low Power Island) found on the Qualcomm Technologies Inc SoCs.

 Symbol: PINCTRL_LPASS_LPI [=n]
 Type  : tristate
 Defined at drivers/pinctrl/qcom/Kconfig:268
   Prompt: Qualcomm Technologies Inc LPASS LPI pin controller driver
   Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINMUX [=n] && PINCONF [=y] && GENERIC_PINCONF [=y]

---

 CONFIG_PINCTRL_MICROCHIP_SGPIO:

 Support for the serial GPIO interface used on Microsemi and
 Microchip SoC's. By using a serial interface, the SIO
 controller significantly extends the number of available
 GPIOs with a minimum number of additional pins on the
 device. The primary purpose of the SIO controller is to
 connect control signals from SFP modules and to act as an
 LED controller.

 Symbol: PINCTRL_MICROCHIP_SGPIO [=n]
 Type  : bool
 Defined at drivers/pinctrl/Kconfig:378
   Prompt: Pinctrl driver for Microsemi/Microchip Serial GPIO
   Depends on: PINCTRL [=y] && OF [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: GPIOLIB [=y] && GPIOLIB_IRQCHIP [=y] && GENERIC_PINCONF [=y] && GENERIC_PINCTRL_GROUPS [=n] && GENERIC_PINMUX_FUNCTIONS [=n] && OF_GPIO [=y]

---

Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:30:01 -04:00
Justin M. Forbes 3c5600f0c8 Fix fedora config mismatch due to dep changes
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:01 -04:00
Fedora Kernel Team 69d303b2a5 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:01 -04:00
Jeremy Cline ff75f0f738 New configs in drivers/crypto
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CHELSIO_TLS_DEVICE:

 This flag enables support for kernel tls offload over Chelsio T6
 crypto accelerator. CONFIG_CHELSIO_TLS_DEVICE flag can be enabled
 only if CONFIG_TLS and CONFIG_TLS_DEVICE flags are enabled.

 Symbol: CHELSIO_TLS_DEVICE [=y]
 Type  : bool
 Defined at drivers/crypto/chelsio/Kconfig:46
   Prompt: Chelsio Inline KTLS Offload
   Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && CHELSIO_T4 [=m] && TLS_DEVICE [=y]
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Hardware crypto devices (CRYPTO_HW [=y])
 Selects: CRYPTO_DEV_CHELSIO [=m]

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>

V2: Update CONFIG_CHELSIO_TLS_DEVICE to =m because inline is not allowed.
2021-08-30 14:30:01 -04:00
Peter Robinson 6e7f8ce4dd Remove duplicate ENERGY_MODEL configs
All configs enable ENERGY_MODEL so just enable it in generic
and remove the duplicates.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
CC: Phil Auld <pauld@redhat.com>
2021-08-30 14:30:00 -04:00
Fedora Kernel Team f167b4c029 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:00 -04:00
Fedora Kernel Team 9b85f82314 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:00 -04:00
Fedora Kernel Team 573de790e4 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:00 -04:00
Fedora Kernel Team 2ae1bd5e84 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:00 -04:00
Fedora Kernel Team 7c4a2e23ec [redhat] AUTOMATIC: New configs 2021-08-30 14:30:00 -04:00
Fedora Kernel Team 361305c816 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:00 -04:00
Justin M. Forbes 28f1c3bb46 This is selected by PCIE_QCOM so must match
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:30:00 -04:00
Fedora Kernel Team d83d74a5b1 [redhat] AUTOMATIC: New configs 2021-08-30 14:30:00 -04:00
Fedora Kernel Team c835d049ba [redhat] AUTOMATIC: New configs 2021-08-30 14:29:59 -04:00
Fedora Kernel Team 15acce53e9 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:59 -04:00
Fedora Kernel Team e33f46d3fa [redhat] AUTOMATIC: New configs 2021-08-30 14:29:59 -04:00
Fedora Kernel Team 2ba018cd2e [redhat] New configs in drivers/media
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VIDEO_CCS:

 This is a generic driver for MIPI CCS, SMIA++ and SMIA compliant
 camera sensors.

 Symbol: VIDEO_CCS [=n]
 Type  : tristate
 Defined at drivers/media/i2c/ccs/Kconfig:2
   Prompt: MIPI CCS/SMIA++/SMIA sensor support
   Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m] && HAVE_CLK [=y]
   Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m] && HAVE_CLK [=y] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && VIDEO_CCS_PLL [=n] && V4L2_FWNODE [=n]

---

 CONFIG_VIDEO_OV02A10:

 This is a Video4Linux2 sensor driver for the OmniVision
 OV02A10 camera.

 To compile this driver as a module, choose M here: the
 module will be called ov02a10.

 Symbol: VIDEO_OV02A10 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:828
   Prompt: OmniVision OV02A10 sensor support
   Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y]
   Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]

---

 CONFIG_VIDEO_OV9734:

 This is a Video4Linux2 sensor driver for the OmniVision
 OV9734 camera.

 To compile this driver as a module, choose M here: the
 module's name is ov9734.

 Symbol: VIDEO_OV9734 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:1067
   Prompt: OmniVision OV9734 sensor support
   Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && (ACPI [=y] || COMPILE_TEST [=n])
   Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:59 -04:00
Peter Robinson 8c12d4e145 drop unused BACKLIGHT_GENERIC
Upstream removed this driver with commit 7ecdea4a02 so it
can now be removed from our configs.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:29:59 -04:00
Fedora Kernel Team ead1ea3a41 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:59 -04:00
Fedora Kernel Team 76b652e533 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:59 -04:00
Jeremy Cline 6112a2176b [redhat] New configs in drivers/pci
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PCIE_HISI_ERR:

 Say Y here if you want error handling support
 for the PCIe controller's errors on HiSilicon HIP SoCs

 Symbol: PCIE_HISI_ERR [=n]
 Type  : bool
 Defined at drivers/pci/controller/Kconfig:301
   Prompt: HiSilicon HIP PCIe controller error handling driver
   Depends on: PCI [=y] && ACPI_APEI_GHES [=y] && (ARM64 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> PCI support (PCI [=y])
         -> PCI controller drivers

---

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:59 -04:00
Jeremy Cline 6d59cc5404 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM64_ERRATUM_1508412:

 This option adds a workaround for Arm Cortex-A77 erratum 1508412.

 Affected Cortex-A77 cores (r0p0, r1p0) could deadlock on a sequence
 of a store-exclusive or read of PAR_EL1 and a load with device or
 non-cacheable memory attributes. The workaround depends on a firmware
 counterpart.

 KVM guests must also have the workaround implemented or they can
 deadlock the system.

 Work around the issue by inserting DMB SY barriers around PAR_EL1
 register reads and warning KVM users. The DMB barrier is sufficient
 to prevent a speculative PAR_EL1 read.

 If unsure, say Y.

 Symbol: ARM64_ERRATUM_1508412 [=y]
 Type  : bool
 Defined at arch/arm64/Kconfig:639
   Prompt: Cortex-A77: 1508412: workaround deadlock on sequence of NC/Device load and store exclusive or PAR read
   Location:
     -> Kernel Features
       -> ARM errata workarounds via the alternatives framework

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:58 -04:00
Paulo E. Castro 02c4f6cfca Remove cp instruction already handled in instruction below.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-08-30 14:29:58 -04:00
Paulo E. Castro d2e7467a50 Add all the dependencies gleaned from running `make prepare` on a bloated devel kernel.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-08-30 14:29:58 -04:00
Paulo E. Castro 3edd97f1e7 Add tools to path mangling script.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-08-30 14:29:58 -04:00
Paulo E. Castro 4d90283de0 Remove duplicate cp statement which is also not specific to x86.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-08-30 14:29:58 -04:00
Paulo E. Castro ce41923d93 Correct orc_types failure whilst running `make prepare` https://bugzilla.redhat.com/show_bug.cgi?id=1882854
In file included from scripts/sorttable.c:191:
scripts/sorttable.h:89:10: fatal error: asm/orc_types.h: No such file or directory
   89 | #include <asm/orc_types.h>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [scripts/Makefile.host:103: scripts/sorttable] Error 1
make: *** [Makefile:1155: scripts] Error 2

Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-08-30 14:29:58 -04:00
Jiri Olsa eb00c8002f redhat: ark: enable CONFIG_IKHEADERS
Enabling kheaders module that carries kernel headers
to compile eBPF programs and will allow bcc-tools rpm
to get rid of kernel-devel dependency.

Signed-off-by: Jiri Olsa <jolsa@kernel.org>
2021-08-30 14:29:58 -04:00
Prarit Bhargava 713b8470cc Add new entries to RHMAINTAINERS
General updates and add new entries for several subsystems to
RHMAINTAINERS.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Alaa Hleihel <ahleihel@redhat.com>
Signed-off-by: Arun Easi <aeasi@redhat.com>
Signed-off-by: Don Brace <dbrace@redhat.com>
Signed-off-by: Frank Ramsay <framsay@redhat.com>
Signed-off-by: Igor Russkikh <irusskik@redhat.com>
Signed-off-by: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Manish Chopra <mchopra@redhat.com>
Signed-off-by: Nilesh Javali <njavali@redhat.com>
Signed-off-by: Selvin Xavier <sxavier@redhat.com>
Signed-off-by: Vishal Kulkarni <viskulka@redhat.com>
Signed-off-by: Wei Huang <wehuang@redhat.com>
2021-08-30 14:29:58 -04:00
Augusto Caringi a1e61eb88b Add missing '$' sign to (GIT) in redhat/Makefile
This commit fixes the following problem (make dist-srpm):

Creating linux-20201213git7f376f1917d7.tar.xz...
/bin/sh: -c: line 0: syntax error near unexpected token `diff'
/bin/sh: -c: line 0: `(GIT) diff --no-renames HEAD
":(exclude,top).get_maintainer.conf" \'
make[1]: *** [Makefile:224: generate-testpatch-tmp] Error 1
make[1]: Leaving directory 'kernel-ark/redhat'
make: *** [makefile:12: dist-srpm] Error

Signed-off-by: Augusto Caringi <acaringi@redhat.com>
2021-08-30 14:29:58 -04:00
Don Zickus b180128c9f Remove filterdiff and use native git instead
Closes: #34

Long ago, we needed the ability to filter out files and directories
from patches.  Now that ability is built into git a few years ago,
let's use that instead of filterdiff.

One less tool to depend on and require.

V2: rebase and fix conflicts

Cc: Bastien Nocera <bnocera@redhat.com>
Cc: Herton Krzesinski <hkrzesin@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:57 -04:00
Fedora Kernel Team 2adc7da80b [redhat] New configs in usr/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RD_ZSTD:

 Support loading of a ZSTD encoded initial ramdisk or cpio buffer.
 If unsure, say N.

 Symbol: RD_ZSTD [=y]
 Type  : bool
 Defined at usr/Kconfig:103
   Prompt: Support initial ramdisk/ramfs compressed using ZSTD
   Depends on: BLK_DEV_INITRD [=y]
   Location:
     -> General setup
       -> Initial RAM filesystem and RAM disk (initramfs/initrd) support (BLK_DEV_INITRD [=y])
 Selects: DECOMPRESS_ZSTD [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:57 -04:00
Justin M. Forbes 41aea2d033 New configs in net/sched
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NET_ACT_GATE:

 Say Y here to allow to control the ingress flow to be passed at
 specific time slot and be dropped at other specific time slot by
 the gate entry list.

 If unsure, say N.
 To compile this code as a module, choose M here: the
 module will be called act_gate.

 Symbol: NET_ACT_GATE [=n]
 Type  : tristate
 Defined at net/sched/Kconfig:984
   Prompt: Frame gate entry list control tc action
   Depends on: NET [=y] && NET_SCHED [=y] && NET_CLS_ACT [=y]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> QoS and/or fair queueing (NET_SCHED [=y])
           -> Actions (NET_CLS_ACT [=y])

Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Xin Long <lxin@redhat.com>
2021-08-30 14:29:57 -04:00
Fedora Kernel Team 9d5080e38e [redhat] AUTOMATIC: New configs 2021-08-30 14:29:57 -04:00
Fedora Kernel Team cf9784fac7 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:57 -04:00
Fedora Kernel Team ab5a1e6aba [redhat] New configs in drivers/usb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_USB_XHCI_PCI_RENESAS:

 Say 'Y' to enable the support for the Renesas xHCI controller with
 firwmare. Make sure you have the firwmare for the device and
 installed on your system for this device to work.
 If unsure, say 'N'.

 Symbol: USB_XHCI_PCI_RENESAS [=n]
 Type  : tristate
 Defined at drivers/usb/host/Kconfig:46
   Prompt: Support for additional Renesas xHCI controller with firwmare
   Depends on: USB_SUPPORT [=y] && USB [=y] && USB_XHCI_HCD [=y]
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
         -> xHCI HCD (USB 3.0) support (USB_XHCI_HCD [=y])

---

Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:57 -04:00
CKI@GitLab a0d1643b2a New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_INTEL_PMC_BXT:

 This driver provides support for the PMC (Power Management
 Controller) on Intel Broxton and Apollo Lake. The PMC is a
 multi-function device that exposes IPC, General Control
 Register and P-unit access. In addition this creates devices
 for iTCO watchdog and telemetry that are part of the PMC.

 Symbol: MFD_INTEL_PMC_BXT [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:650
   Prompt: Intel PMC Driver for Broxton
   Depends on: HAS_IOMEM [=y] && X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: INTEL_SCU_IPC [=n] && MFD_CORE [=y]

Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
2021-08-30 14:29:57 -04:00
Fedora Kernel Team 5353946c35 New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_MP2629:

 Select this option to enable support for Monolithic Power Systems
 battery charger. This provides ADC, thermal and battery charger power
 management functions.

 Symbol: MFD_MP2629 [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:452
   Prompt: Monolithic Power Systems MP2629 ADC and Battery charger
   Depends on: HAS_IOMEM [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: REGMAP_I2C [=m]

Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
2021-08-30 14:29:56 -04:00
Fedora Kernel Team 725a654644 New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EFI_CUSTOM_SSDT_OVERLAYS:

 Allow loading of an ACPI SSDT overlay from an EFI variable specified
 by a kernel command line option.

 See Documentation/admin-guide/acpi/ssdt-overlays.rst for more
 information.

 Symbol: EFI_CUSTOM_SSDT_OVERLAYS [=y]
 Type  : bool
 Defined at drivers/firmware/efi/Kconfig:282
   Prompt: Load custom ACPI SSDT overlay from an EFI variable
   Depends on: EFI_VARS [=y] && ACPI [=y]
   Location:
     -> Firmware Drivers

Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
2021-08-30 14:29:56 -04:00
Justin M. Forbes 370938b97e Temporarily backout parallel xz script
For quite some time, the parallel_xz.sh script has been hanging up
builds in koji.  While it may be a benefit to get this fixed, it is much
better to back that change out in the short term.  This reverts us to
the way that Fedora used to compress the modules.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:56 -04:00
Bruno Meneguele df49639711 redhat: explicitly disable CONFIG_IMA_APPRAISE_SIGNED_INIT
To avoid warnings during dist-configs we need to explicitly set a value for
this options, which should be disabled.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:56 -04:00
Bruno Meneguele 9c6a1cf6fe redhat: enable CONFIG_EVM_LOAD_X509 on ARK
Both CONFIG_EVM_LOAD_X509 and CONFIG_EVM_X509_PATH are complementary and
should be enabled. It behaves in the same way as the x509 certificates on
IMA, which can be added to '.evm' keyring once they are signed with a
trusted key placed in the '.platform_keyring'.

And, as dependency, CONFIG_ENCRYPTED_KEYS must be also set to =y in all
arches.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:56 -04:00
Bruno Meneguele 9b4d0cbdec redhat: enable CONFIG_EVM_ATTR_FSUUID on ARK
Make it default to all arches on ARK. x86_64 and powerpc already had it
enabled, and keep it disabled elsewhere.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:56 -04:00
Bruno Meneguele bb8ec99d51 redhat: enable CONFIG_EVM in all arches and flavors
The same way IMA should be enabled in all arches, EVM also should be.
EVM is independent, but also complementary, from IMA.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:56 -04:00
Bruno Meneguele cfae01f00b redhat: enable CONFIG_IMA_LOAD_X509 on ARK
Both options CONFIG_IMA_LOAD_X509 and CONFIG_IMA_X509_PATH are complementary
and should be enabled for all ARK flavors: IBM requested it for powerpc some
time ago on RHEL and others arches should be in sync.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:55 -04:00
Bruno Meneguele 04a320e3a4 redhat: set CONFIG_IMA_DEFAULT_HASH to SHA256
Set SHA256 as the default IMA hash on all arches and flavors.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:55 -04:00
Bruno Meneguele 467252d96c redhat: enable CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT
x86 and powerpc have this config to let IMA know it can check for secure
and/or trusted boot state during runtime, allowing other features to be
initialized.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:55 -04:00
Bruno Meneguele 2b4d218e33 redhat: enable CONFIG_IMA_READ_POLICY on ARK
It's already enabled for all Fedora arches and has no reason for not be
enabled on ARK.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:55 -04:00
Bruno Meneguele c4fa975eb7 redhat: set default IMA template for all ARK arches
Fedora and ARK uses different IMA templates, and that's fine, but the
templates should be kept the same across arches in the same flavor (ARK in
this case).

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:55 -04:00
Bruno Meneguele 5ab9994bfc redhat: enable CONFIG_IMA_DEFAULT_HASH_SHA256 for all flavors
IMA default hash was already defaulted to SHA256 on Fedora.
It's time to make it the default for all arches in ARK too.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:55 -04:00
Bruno Meneguele 3a8d43fb37 redhat: disable CONFIG_IMA_DEFAULT_HASH_SHA1
CONFIG_IMA_DEFAULT_HASH_SHA1 is already disabled for all Fedora arches and
ARK should also drop it and use SHA256 instead.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:55 -04:00
Bruno Meneguele d30ee3d875 redhat: enable CONFIG_IMA_ARCH_POLICY for ppc and x86
Upstream kernel supports specific architecture IMA policies and has been
requested by IBM on RHEL. With that, enable it on ARK and Fedora too.

Two another options: PPC_SECURE_BOOT and PPC_SECVAR_SYSFS, are brought as
dependency for IMA_ARCH_POLICY on PPC.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:54 -04:00
Bruno Meneguele f357a47b66 redhat: enable CONFIG_IMA_APPRAISE_MODSIG
Fedora was already enabling it to all arches. ARK had it only disabled for
aarch64 because this arch hand't INTEGRITY subsystem enabled. This patch
only make it enabled for all arches and flavors and remove the
pending-common/ referent file.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:54 -04:00
Bruno Meneguele 38de39fbf6 redhat: enable CONFIG_IMA_APPRAISE_BOOTPARAM
CONFIG_IMA_APPRAISE_BOOTPARAM was enabled for all Fedora flavor arches. It's
now also being enabled for all ARK supported arches, with that, enable it
by default in all arches and flavors.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:54 -04:00
Bruno Meneguele cf952320ab redhat: enable CONFIG_IMA_APPRAISE
It's one of the basic operations offered by IMA, there isn't any reason to
keep it disabled.  Make it enabled by default in all flavors and arches.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:54 -04:00
Bruno Meneguele 8f84e6ca94 redhat: enable CONFIG_INTEGRITY for aarch64
It was disabled when RHEL was experimenting AARCH64 and was left in that way
since then.  There is no good reason for keep it disabled on aarch64
architecture today.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 14:29:54 -04:00
Ben Crocker 09897c5c48 [redhat] self-test/0001-shellcheck.bats: check for shellcheck
Check via 'test -x' whether /usr/bin/shellcheck is present; if not,
skip the test and print a message.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:29:54 -04:00
Ben Crocker 9eef9379bc [redhat] self-test/1001-rpmlint.bats, 1003-rpminspect.bats
1003-rpminspect.bats: initial commit.

Like the 1001-rpmlint.bats test, this test
• tests for exactly one SRPM
• runs rpminspect (instead of rpmlint) on that SRPM,
  after checking for the presence of the /usr/bin/rpminspect.

Both 1001-rpmlint.bats and 1003-rpminspect.bats
Check via 'test -x' whether the /usr/bin/rpmlint or rpminspect,
respectively, is installed; if not, skip the test and print a message.

For now, skip both tests entirely, pending fixes to kernel.spec.template.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:29:54 -04:00
Ben Crocker 6194173450 [redhat] Makefile, Makefile.common, egit.sh, 1005-dist-dump-variables.bats
• Makefile:

  Create new dist-dump-variables target for dynamically deriving variables
  from Makefile.common and dumping them.

  Create new dist-clean-scripts target to clean up generated scripts.

  Create new dist-self-test target and hook up the BATS
  self tests.  Check for the presence of /usr/bin/bats
  (via 'test -x') and complain if it is not installed.

  Add a description of the new dist-self-test target to dist-full-help.

• Makefile.common: make HEAD an overridable variable.
  Change
  GITID:= $(shell $(GIT) log --max-count=1 --pretty=format:%H)
  to
  GITID:= $(shell $(GIT) log --max-count=1 --pretty=format:%H $(HEAD))

  making the argument to 'git log' explicit and allowing it to be
  overridden by, e.g., self-tests.

• self-test/egit.sh: Initial commit

  This is a sample script providing a thin layer over the git command.
  It is meant to substitute in redhat/Makefile and Makefile.common via the
  GIT macro defined in Makefile.

  Each git subcommand currently used by Makefile and Makefile.common can
  be broken out into its own case.  At the moment, the output of
  'git describe' can be overridden by means of an
  environment variable, EGIT_OVERRIDE_DESCRIBE.

  Use case: self test with test values for 'git describe'.

  Other git subcommands are simply passed through.

  Usage:

  GIT=<path to egit.sh> EGIT_OVERRIDE_DESCRIBE=v5.9-rc8 DIST=.elrdy make dist-srpm

• self-test/1005-dist-dump-variables.bats: initial commit

The four tests in 1005-dist-dump-variables.bats test the RPM version
generation, name generation, and snapshot designation for several
previously chosen tags/commits.

The tags/commits chosen are:

a) v5.8
b) v5.8-rc7
c) v5.8-9-g565674d613d7
d) v5.8-rc5-99-g25ccd24ffd91

and the expected results are:
a) RPMVERSION = 5.8.0, no rc
b) RPMVERSION = 5.8.0, .rc7
c) RPMVERSION = 5.9.0, .rc0, snapshot
d) RPMVERSION = 5.8.0, .rc5, snapshot

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:29:53 -04:00
Ben Crocker 7cc64e95a0 [redhat] Add GIT macro to Makefile and Makefile.common:
GIT ?= git

and replace literal occurrences of 'git' with $(GIT).
This change enables us to override 'git' with, e.g., some
arbitrary shell script that prints additional information
and/or does additional processing before and/or after (or
even instead of) invoking /usr/bin/git.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:29:53 -04:00
Jeremy Linton c282c84a73 kernel: Update some missing KASAN/KCSAN options
The kernel option validator complains that these tags are
missing, lets default them to off.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:29:53 -04:00
Jeremy Linton 6e632971d8 kernel: Enable coresight on aarch64
Coresight is a hardware assisted debug and trace technology.
Now that 5.10 allows them to be built as modules lets
enable the functionality in fedora.

More information about coresight may be found here:

https://developer.arm.com/ip-products/system-ip/coresight-debug-and-trace

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
2021-08-30 14:29:53 -04:00
Justin Forbes 143d72cbdb Update CONFIG_INET6_ESPINTCP 2021-08-30 14:29:53 -04:00
Justin M. Forbes 63b9fed88a New configs in net/ipv6
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INET6_ESPINTCP:

 Support for RFC 8229 encapsulation of ESP and IKE over
 TCP/IPv6 sockets.

 If unsure, say N.

 Symbol: INET6_ESPINTCP [=n]
 Type  : bool
 Defined at net/ipv6/Kconfig:91
   Prompt: IPv6: ESP in TCP encapsulation (RFC 8229)
   Depends on: NET [=y] && INET [=y] && IPV6 [=y] && XFRM [=y] && INET6_ESP [=m]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> TCP/IP networking (INET [=y])
           -> The IPv6 protocol (IPV6 [=y])
             -> IPv6: ESP transformation (INET6_ESP [=m])
 Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y] && XFRM_ESPINTCP [=y]

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
2021-08-30 14:29:53 -04:00
Peter Robinson 73b9d2e927 fedora: move CONFIG_RTC_NVMEM options from ark to common
Move CONFIG_RTC_NVMEM to common so Fedora is enabled and the same as ARK kernels.
No changes to ARK kernels

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:29:53 -04:00
Don Zickus b3e57db357 configs: Enable CONFIG_DEBUG_INFO_BTF
This option is needed to allow the latest features of bpftool
to compile correctly.  Currently it was disabled because of
a gcc bug around DWARF info.  That has been resolved with the
latest gcc and/or dwarves package.  Re-enable.

Signed-off-by: Don Zickus <dzickus@redhat.com>

V2: Add dwarves BuildRequires to eln
2021-08-30 14:29:53 -04:00
Jeremy Cline ec0e71546a [redhat] New configs in drivers/video
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BACKLIGHT_LED:

 If you have a LCD backlight adjustable by LED class driver, say Y
 to enable this driver.

 Symbol: BACKLIGHT_LED [=n]
 Type  : tristate
 Defined at drivers/video/backlight/Kconfig:459
   Prompt: Generic LED based Backlight Driver
   Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y] && LEDS_CLASS [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Backlight & LCD device support
           -> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])

Lyude isn't aware of anything that uses this currently, but noted that
that it's likely it will be needed for newer laptops and so recommended
"m".

---

Cc: Lyude Paul <lyude@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:29:52 -04:00
Peter Robinson 77818b7cf3 fedora: some minor arm audio config tweaks
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:29:52 -04:00
Bastien Nocera af31b44991 Ship xpad with default modules on Fedora and RHEL
XBox 360 and XBox One controllers are very common as PC joypads.
iOS, macOS, Android and Windows all support those joypads out of the
box, so Fedora should too.
2021-08-30 14:29:52 -04:00
Peter Robinson 5246c401a3 Fedora: Only enable legacy serial/game port joysticks on x86
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:29:52 -04:00
Peter Robinson 97e53739a2 Fedora: Enable the options required for the Librem 5 Phone
There's a bunch of interest around various phones ATM such as the Librem 5
so enable the options that are upstream.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 14:29:52 -04:00
Justin M. Forbes 879f977db7 Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:52 -04:00
Justin M. Forbes 05a886262a Fedora config change because CONFIG_FSL_DPAA2_ETH now selects CONFIG_FSL_XGMAC_MDIO
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:52 -04:00
Herton R. Krzesinski 905fdcb8d8 [redhat] fix kernel changelog release mismatch in dist-release
The kernel changelog which is created also have a wrong release number eg.:

  ...
  +RHEL_RELEASE = 69
  --- a/redhat/kernel.changelog-8.99
  +++ b/redhat/kernel.changelog-8.99
  @@ -1,3 +1,7 @@
  +* Wed Nov 11 2020 Fedora Kernel Team <kernel-team@fedoraproject.org> [5.10.0-0.rc3.20201111giteccc87672492.68.test]
  ...

That's because of stale data/changelog which is created before the release
bump is done. We need to revert changes and recreate the changelog after
the diff-index check and release bump, so we get the updated number and do
not have a duplicate changelog entry.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:52 -04:00
Herton R. Krzesinski 781028a33e [redhat] fix the detection of changed files in dist-release
The git diff-index has a catch which you must pay attention, if you eg.
do this:

touch redhat/Makefile
git diff-index HEAD

It'll show there is a change even if contents didn't change. This makes
the current logic to not work since we may not really have changed the
contents, but the redirection will act similar as a touch on those files.
We need to run update-index before it so diff-index check works properly.

Also, the "exit 0" was not working as intended, and the Makefile commands
after the check were still running, thus I changed the code to use an if
conditional to make it work.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:51 -04:00
Herton R. Krzesinski 2aa20d15a3 [redhat] Avoid ".test" suffix with ark-create-release.sh
The first release commit was always being created with the test
suffix because the default is to append ".test" if there is no
localversion or BUILDID given to dist-release. Move up the touch
localversion so we avoid it.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:51 -04:00
Herton R. Krzesinski 217a407902 [redhat] Avoid offset of 1 between release in Makefile and commit
When doing dist-release, the release commit will have the wrong release
number, eg.:

  commit db61196cc6aab3f6ece65027551ebfb2f5edea90
  ...
      [redhat] kernel-5.10.0-0.rc3.20201111giteccc87672492.69.test
  ...
  -RHEL_RELEASE = 69
  +RHEL_RELEASE = 70
  ...

While the new release is 70 in example above, the commit title has the wrong
value. That mismatch happens because the release number is a Makefile.rhelver
variable included and used by make rules, and make doesn't see the updated
value, you need to eg. reload it through a sub make process. This change adds
a new rule and new make invocation so the proper RHEL_RELEASE value is used when
doing the release commit.

Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:51 -04:00
Davide Caratti 26ad98d3fc redhat: generic enable CONFIG_INET_MPTCP_DIAG
so that MPTCP-level socket diagnostics are available to userspace
applications like 'ss'.

Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:51 -04:00
Justin M. Forbes 70ed11bfc8 Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:51 -04:00
Fedora Kernel Team 2fa80bb83b [redhat] AUTOMATIC: New configs 2021-08-30 14:29:51 -04:00
Justin M. Forbes ac293ac07d Enable NANDSIM for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:51 -04:00
Justin M. Forbes 47ea68dbe1 Re-enable CONFIG_ACPI_TABLE_UPGRADE for Fedora since upstream disables this if secureboot is active
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:51 -04:00
Justin M. Forbes a792705c8e Ath11k related config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:50 -04:00
Fedora Kernel Team e7bb3d3943 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:50 -04:00
Justin M. Forbes c998c9811d Fedora config updates for ath11k
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:50 -04:00
Fedora Kernel Team 1b7eba0666 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:50 -04:00
Justin M. Forbes 569b570376 Turn on ATH11K for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:50 -04:00
Fedora Kernel Team 2e2758c175 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:50 -04:00
Jerry Snitselaar 0b2a205ec6 redhat: enable CONFIG_INTEL_IOMMU_SVM
Enable Intel Shared Virtual Memory config option. Since it is already
enabled for Fedora, move it to common/x86/x86_64 to enable it
for both RHEL and Fedora.

Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
2021-08-30 14:29:50 -04:00
Justin M. Forbes ebce1e9237 More Fedora config fixes
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:50 -04:00
Justin M. Forbes 449f99b163 Fedora 5.10 config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:49 -04:00
Fedora Kernel Team f4dc7eaf8d [redhat] AUTOMATIC: New configs 2021-08-30 14:29:49 -04:00
Justin M. Forbes c3200d5896 Fedora 5.10 configs round 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:49 -04:00
Justin M. Forbes 6aefbca32f Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:49 -04:00
Fedora Kernel Team e7dd031ebd [redhat] AUTOMATIC: New configs 2021-08-30 14:29:49 -04:00
Fedora Kernel Team 390091b6ff [redhat] AUTOMATIC: New configs 2021-08-30 14:29:49 -04:00
Don Zickus 1a265ac24f Allow kernel-tools to build without selftests
While debugging LTO issues, I disabled kernel-selftests
temporarily.  This exposed an issue in turbostat that
required libcap to compile.  Add the BuildRequires to
the spec file.

I don't expect this scenario to happen at all. This
fix is for completeness and less headaches in the future.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:49 -04:00
Don Zickus 81e3263d99 Allow building of kernel-tools standalone
For CKI and its cross-compile environment, it can not cross
compile userspace tools.  Instead we will native compiles them.

To allow this split, the kernel.spec needs to support only
building userspace stuff and not the kernel itself.

However the userspace tools need some vars defined. This
patch creates a new function and sets up those vars.

Also very useful for debugging userspace tools and skipping
the hour long kernel build times (like LTO).

To use this effectively, one would use
--without_up
--without_debug
--without_zfcpdump

Original author is Brian Masney <bmasney@redhat.com>, which
I took from his RHEL-8 contribution.  His original changelog

    The kernel.spec file initializes the .config file and Arch variable
    in the BuildKernel() function. This works fine when the user space
    tools are built at the same time as the kernel, however this fails
    when attempting to build the user space tools in isolation.
    Specifically, this fails when debug, zfcpdump, and up are all
    disabled. The kernel-tools and kernel-selftests packages fail to
    build.

    Let's fix this by adding a new function InitBuildKernel() that
    initializes a kernel build. This function is called when debug,
    zfcpdump, and up are all disabled.

V2: Fix inline comment and add original changelog.

Cc: Brian Masney <bmasney@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:49 -04:00
Davide Caratti 431790983e redhat: ark: disable CONFIG_NET_ACT_CTINFO
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti 23cdd58cee redhat: ark: disable CONFIG_NET_SCH_TEQL
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti d7c1112a4d redhat: ark: disable CONFIG_NET_SCH_SFB
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti b4890b21d1 redhat: ark: disable CONFIG_NET_SCH_QFQ
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti a4023ff86b redhat: ark: disable CONFIG_NET_SCH_PLUG
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti 54eb7b78d6 redhat: ark: disable CONFIG_NET_SCH_PIE
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti 69f678e953 redhat: ark: disable CONFIG_NET_SCH_HHF
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti f3517a79fa redhat: ark: disable CONFIG_NET_SCH_DSMARK
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti 9839fc8519 redhat: ark: disable CONFIG_NET_SCH_DRR
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti f260b60cd7 redhat: ark: disable CONFIG_NET_SCH_CODEL
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:48 -04:00
Davide Caratti 030878d6ff redhat: ark: disable CONFIG_NET_SCH_CHOKE
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti 7b5024bc47 redhat: ark: disable CONFIG_NET_SCH_CBQ
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti 088684e2ac redhat: ark: disable CONFIG_NET_SCH_ATM
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti 11b2fbe530 redhat: ark: disable CONFIG_NET_EMATCH and sub-targets
CONFIG_NET_EMATCH
 CONFIG_NET_EMATCH_CMP
 CONFIG_NET_EMATCH_IPSET
 CONFIG_NET_EMATCH_META
 CONFIG_NET_EMATCH_NBYTE
 CONFIG_NET_EMATCH_STACK
 CONFIG_NET_EMATCH_TEXT
 CONFIG_NET_EMATCH_U32
 # ./scripts/config --file redhat/configs/ark/generic/${a} -d ${a} ; done

please note,

 CONFIG_NET_EMATCH_IPT
 CONFIG_NET_EMATCH_CANID

are already disabled in "generic": Only fedora enables them.

Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti 5ac29dbcc8 redhat: ark: disable CONFIG_NET_CLS_TCINDEX
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti b50767c3dc redhat: ark: disable CONFIG_NET_CLS_RSVP6
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti 1c56670363 redhat: ark: disable CONFIG_NET_CLS_RSVP
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti 72e12af274 redhat: ark: disable CONFIG_NET_CLS_ROUTE4
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti dd82be15f4 redhat: ark: disable CONFIG_NET_CLS_BASIC
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti da4e8ae39b redhat: ark: disable CONFIG_NET_ACT_SKBMOD
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:47 -04:00
Davide Caratti f3daf0a69a redhat: ark: disable CONFIG_NET_ACT_SIMP
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:46 -04:00
Davide Caratti d0df16477e redhat: ark: disable CONFIG_NET_ACT_NAT
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 14:29:46 -04:00
Fedora Kernel Team ca4fd49c56 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:46 -04:00
Bhupesh Sharma 26c83bae2e arm64/defconfig: Enable CONFIG_KEXEC_FILE
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1821565
Upstream Status: 2a379716f3

kexec_file_load() syscall interface is now supported for
arm64 architecture as well via upstream commits:
3751e728ce ("arm64: kexec_file: add crash dump support") and
3ddd9992a5 ("arm64: enable KEXEC_FILE config")].

This patch enables config KEXEC_FILE by default in the fedora
arm64 defconfig, so that user-space tools like kexec-tools
can use the same as the default interface for kexec/kdump
on arm64 fedora systems.

Cc: kernel-team@fedoraproject.org
Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
2021-08-30 14:29:46 -04:00
Prarit Bhargava 757809bcd9 redhat/configs: Cleanup CONFIG_CRYPTO_SHA512
Sending new version, previous version not acked.

P.

--8<--

dzickus pointed out that my change is not optimal.  CONFIG_CRYPTO_SHA512
can be moved to the common/generic directory since it is enabled on
both Fedora and ARK.

Cleanup the CONFIG_CRYPTO_SHA512 files.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
2021-08-30 14:29:46 -04:00
Fedora Kernel Team e196ce3d8a New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
2021-08-30 14:29:46 -04:00
Fedora Kernel Team 882530b8ba [redhat] New configs in drivers/usb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TYPEC_QCOM_PMIC:

 Driver for supporting role switch over the Qualcomm PMIC.  This will
 handle the USB Type-C role and orientation detection reported by the
 QCOM PMIC if the PMIC has the capability to handle USB Type-C
 detection.

 It will also enable the VBUS output to connected devices when a
 DFP connection is made.

 Symbol: TYPEC_QCOM_PMIC [=n]
 Type  : tristate
 Defined at drivers/usb/typec/Kconfig:88
   Prompt: Qualcomm PMIC USB Type-C driver
   Depends on: USB_SUPPORT [=y] && TYPEC [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
         -> USB Type-C Support (TYPEC [=y])

---

 CONFIG_TYPEC_STUSB160X:

 Say Y or M here if your system has STMicroelectronics STUSB160x
 Type-C port controller.

 If you choose to build this driver as a dynamically linked module, the
 module will be called stusb160x.ko.

 Symbol: TYPEC_STUSB160X [=n]
 Type  : tristate
 Defined at drivers/usb/typec/Kconfig:76
   Prompt: STMicroelectronics STUSB160x Type-C controller driver
   Depends on: USB_SUPPORT [=y] && TYPEC [=y] && I2C [=y] && REGMAP_I2C [=m] && (USB_ROLE_SWITCH [=m] || !USB_ROLE_SWITCH [=m])
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
         -> USB Type-C Support (TYPEC [=y])

---

 CONFIG_TYPEC_TCPCI_MAXIM:

 MAXIM TCPCI based Type-C/PD chip driver. Works with
 with Type-C Port Controller Manager.

 Symbol: TYPEC_TCPCI_MAXIM [=n]
 Type  : tristate
 Defined at drivers/usb/typec/tcpm/Kconfig:38
   Prompt: Maxim TCPCI based Type-C chip driver
   Depends on: USB_SUPPORT [=y] && TYPEC [=y] && TYPEC_TCPM [=m] && TYPEC_TCPCI [=m]
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
         -> USB Type-C Support (TYPEC [=y])
           -> USB Type-C Port Controller Manager (TYPEC_TCPM [=m])
             -> Type-C Port Controller Interface driver (TYPEC_TCPCI [=m])

---

 CONFIG_USB_FEW_INIT_RETRIES:

 When a new USB device is detected, the kernel tries very hard
 to initialize and enumerate it, with lots of nested retry loops.
 This almost always works, but when it fails it can take a long time.
 This option tells the kernel to make only a few retry attempts,
 so that the total time required for a failed initialization is
 no more than 30 seconds (as required by the USB OTG spec).

 Say N here unless you require new-device enumeration failure to
 occur within 30 seconds (as might be needed in an embedded
 application).

 Symbol: USB_FEW_INIT_RETRIES [=n]
 Type  : bool
 Defined at drivers/usb/core/Kconfig:35
   Prompt: Limit USB device initialization to only a few retries
   Depends on: USB_SUPPORT [=y] && USB [=y]
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])

---

Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:46 -04:00
Fedora Kernel Team 3133147b94 [redhat] New configs in net/xfrm
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_XFRM_USER_COMPAT:

 Transformation(XFRM) user configuration interface like IPsec
 used by compatible Linux applications.

 If unsure, say N.

 Symbol: XFRM_USER_COMPAT [=n]
 Type  : tristate
 Defined at net/xfrm/Kconfig:31
   Prompt: Compatible ABI support
   Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> Transformation user configuration interface (XFRM_USER [=y])
 Selects: WANT_COMPAT_NETLINK_MESSAGES [=n]

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:46 -04:00
Fedora Kernel Team b628770ec0 [redhat] New configs in kernel/rcu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RCU_SCALE_TEST:

 This option provides a kernel module that runs performance
 tests on the RCU infrastructure.  The kernel module may be built
 after the fact on the running kernel to be tested, if desired.

 Say Y here if you want RCU performance tests to be built into
 the kernel.
 Say M if you want the RCU performance tests to build as a module.
 Say N if you are unsure.

 Symbol: RCU_SCALE_TEST [=n]
 Type  : tristate
 Defined at kernel/rcu/Kconfig.debug:26
   Prompt: performance tests for RCU
   Depends on: DEBUG_KERNEL [=y]
   Location:
     -> Kernel hacking
       -> RCU Debugging
 Selects: TORTURE_TEST [=n] && SRCU [=y] && TASKS_RCU [=n] && TASKS_RUDE_RCU [=y] && TASKS_TRACE_RCU [=y]

---

Cc: Waiman Long <longman@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:46 -04:00
Fedora Kernel Team 899434d366 [redhat] New configs in drivers/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_QCOM_CPR:

 Say Y here to enable support for the CPR hardware found on Qualcomm
 SoCs like QCS404.

 This driver populates CPU OPPs tables and makes adjustments to the
 tables based on feedback from the CPR hardware. If you want to do
 CPUfrequency scaling say Y here.

 To compile this driver as a module, choose M here: the module will
 be called qcom-cpr

 Symbol: QCOM_CPR [=n]
 Type  : tristate
 Defined at drivers/soc/qcom/Kconfig:29
   Prompt: QCOM Core Power Reduction (CPR) support
   Depends on: ARCH_QCOM [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> SOC (System On Chip) specific Drivers
         -> Qualcomm SoC drivers
 Selects: PM_OPP [=n] && REGMAP [=y]

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:45 -04:00
Don Zickus 8d70be5412 Fix LTO issues with kernel-tools
There are two parts to this fix.  One is using the recommended way
to disable LTO.  The other is to make it work for the kernel.spec
file.

Various kernel-tool programs (like perf) can not handle LTO yet, so
they are disabled.

This is done with '%define _lto_cflags {nil}'.

However that doesn't quite work for the kernel for the %install
section.  It works for the %build section.

Oddly, back at the birth of dist-git, the initial kernel.spec
file was imported with a line at the top

%global __spec_install_pre %{___build_pre}

For whatever reason, the kernel was deemed special and that line
pre-built the %install scripts _before_ the lto_cflags could
dynamically be disabled.

Moving the _lto_cflags line above the _pre line disables LTO for both the
%build and %install sections of the spec file successfully.

However, because that _pre line is unintiutive and caused hours
of debugging headache, I hacked up the output to see what the
%__spec_install_pre and ___build_pre looked like at the
beginning of the %install section.  The idea was __build_pre
is what we want going forward.

Unfortunately, after examining the results, I learned the %install
section expects a clean RPM_BUILD_ROOT.  But the kernel %build
section puts each compiled variant into the RPM_BUILD_ROOT as
it completes.  Thus is gets removed on %install setup.  So the
%__spec_install_pre line has to stay.

Instead I add a bunch of comments explaining why it is necessary
and where to add changes like _lto_cflags.  This hopefully
reduces headaches in the future.

V2: restore __spec_install_pre line and add comments.

Cc: Jeff Law <law@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:45 -04:00
Justin M. Forbes d22fcd1d19 Point pathfix to the new location for gen_compile_commands.py
The existing call for pathfix.py fails because
scripts/gen_compile_commands.py is no longer present. It has been moved
to scripts/clang-tools and another script has been added there as well,
so fix up the directory.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:45 -04:00
Ondrej Mosnacek db857b41d0 configs: Disable CONFIG_SECURITY_SELINUX_DISABLE
The functionality has been deprecated upstream, so let's disable it
procatively in Fedora to not delay the inevitable. We are ready to
inherit this in RHEL-9, so do the change directly in
redhat/configs/common.

Quoting basic information from the Fedora change proposal [1]:
"""
Currently, SELinux can be disabled using selinux=0 on the kernel command
line, or in userspace via /etc/selinux/config. In the latter case,
/etc/selinux/config is read by libselinux userspace library during boot
and if it contains SELINUX=disabled, it writes 1 into
/sys/fs/selinux/disable and unmounts /sys/fs/selinux.

Support for SELinux runtime disable via /etc/selinux/config was
originally developed to make it easier for Linux distributions to
support architectures where adding parameters to the kernel command line
was difficult. Unfortunately, supporting runtime disable meant we had to
make some security trade-offs when it comes to the kernel LSM hooks.

Marking the kernel LSM hooks as read only provides some very nice
security benefits, but it does mean that we can no longer disable
SELinux at runtime. Toggling between enforcing and permissive mode while
booted will remain unaffected and it will still be possible to disable
SELinux by adding selinux=0 to the kernel command line via the boot
loader (GRUB).

System with SELINUX=disabled in /etc/selinux/config will come up with
/sys/fs/selinux unmounted, userspace will detect SELinux as disabled.
Internally SELinux will be enabled but not initialized so that there
will be no SELinux checks applied. This state is very similar to SELinux
disabled - the hooks are active, but they mostly do almost nothing so
there should be very little effect on the time spent in syscalls
compared to SELinux fully disabled.

Runtime disable is considered deprecated by upstream, and using it will
become increasingly painful (e.g. sleeping/blocking) through future
kernel releases until eventually it is removed completely. Current
kernel reports the following message during runtime disable:

    SELinux: Runtime disable is deprecated, use selinux=0 on the kernel
    cmdline

Additional info:
* https://lwn.net/Articles/666550
* https://lore.kernel.org/selinux/159110207843.57260.5661475689740939480.stgit@chester/
* https://lore.kernel.org/selinux/157836784986.560897.13893922675143903084.stgit@chester/#t
"""

[1] https://fedoraproject.org/wiki/Changes/Remove_Support_For_SELinux_Runtime_Disable

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 14:29:45 -04:00
Fedora Kernel Team dd1851c12a [redhat] New configs in drivers/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PHY_INTEL_KEEMBAY_EMMC:

 Choose this option if you have an Intel Keem Bay SoC.

 To compile this driver as a module, choose M here: the module
 will be called phy-keembay-emmc.ko.

 Symbol: PHY_INTEL_KEEMBAY_EMMC [=n]
 Type  : tristate
 Defined at drivers/phy/intel/Kconfig:5
   Prompt: Intel Keem Bay EMMC PHY driver
   Depends on: (OF [=y] && ARM64 [=y] || COMPILE_TEST [=n]) && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=y] && REGMAP_MMIO [=y]

---

 CONFIG_PHY_INTEL_LGM_EMMC:

 Enable this to support the Intel EMMC PHY

 Symbol: PHY_INTEL_LGM_EMMC [=n]
 Type  : tristate
 Defined at drivers/phy/intel/Kconfig:31
   Prompt: Intel Lightning Mountain EMMC PHY driver
   Depends on: X86 [=y] || COMPILE_TEST [=n]
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=n]

---

 CONFIG_USB_LGM_PHY:

 Enable this to support Intel DWC3 PHY USB phy. This driver provides
 interface to interact with USB GEN-II and USB 3.x PHY that is part
 of the Intel network SOC.

 Symbol: USB_LGM_PHY [=n]
 Type  : tristate
 Defined at drivers/phy/Kconfig:52
   Prompt: INTEL Lightning Mountain USB PHY Driver
   Depends on: USB_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: USB_PHY [=n] && REGULATOR [=n] && REGULATOR_FIXED_VOLTAGE [=n]

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:45 -04:00
Fedora Kernel Team 67a9fe2734 [redhat] New configs in drivers/misc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HISI_HIKEY_USB:

 If you say yes here this adds support for the on-board USB GPIO hub
 found on HiKey 960/970 boards, which is necessary to support
 switching between the dual-role USB-C port and the USB-A host ports
 using only one USB controller.

 Symbol: HISI_HIKEY_USB [=n]
 Type  : tristate
 Defined at drivers/misc/Kconfig:459
   Prompt: USB GPIO Hub on HiSilicon Hikey 960/970 Platform
   Depends on: (OF [=y] && GPIOLIB [=y] || COMPILE_TEST [=n]) && USB_ROLE_SWITCH [=m]
   Location:
     -> Device Drivers
       -> Misc devices

---

 CONFIG_INTEL_MEI_VIRTIO:

 This module implements mei hw emulation over virtio transport.
 The module will be called mei_virtio.
 Enable this if your virtual machine supports virtual mei
 device over virtio.

 Symbol: INTEL_MEI_VIRTIO [=n]
 Type  : tristate
 Defined at drivers/misc/mei/Kconfig:49
   Prompt: Intel MEI interface emulation with virtio framework
   Depends on: X86 [=y] && PCI [=y] && VIRTIO_PCI [=y]
   Location:
     -> Device Drivers
       -> Misc devices
 Selects: INTEL_MEI [=m]

---

Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:45 -04:00
Fedora Kernel Team 938835e7ef [redhat] AUTOMATIC: New configs 2021-08-30 14:29:45 -04:00
Fedora Kernel Team fec98ec09a [redhat] AUTOMATIC: New configs 2021-08-30 14:29:44 -04:00
Don Zickus daf2a4ec42 [Automatic] Handle config dependency changes
A few configs changed their dependencies and that affects what options
the configs can be.  Two configs can no longer be inline and one brings
in more confgs that are unnecessary.  Fix them quickly for a review
later.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:44 -04:00
Fedora Kernel Team bf982b4ffa [redhat] AUTOMATIC: New configs 2021-08-30 14:29:44 -04:00
Fedora Kernel Team 824833ff76 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:44 -04:00
Fedora Kernel Team ab5a0d534a [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DRM_AMD_DC_SI:

 Choose this option to enable new AMD DC support for SI asics
 by default. This includes Tahiti, Pitcairn, Cape Verde, Oland.
 Hainan is not supported by AMD DC and it has no physical DCE6.

 Symbol: DRM_AMD_DC_SI [=n]
 Type  : bool
 Defined at drivers/gpu/drm/amd/display/Kconfig:34
   Prompt: AMD DC support for Southern Islands ASICs
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m]
   Location:
     -> Device Drivers
       -> Graphics support
         -> AMD GPU (DRM_AMDGPU [=m])
           -> Display Engine Configuration

---

 CONFIG_DRM_CDNS_MHDP8546:

 Support Cadence DPI to DP bridge. This is an internal
 bridge and is meant to be directly embedded in a SoC.
 It takes a DPI stream as input and outputs it encoded
 in DP format.

 Symbol: DRM_CDNS_MHDP8546 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/cadence/Kconfig:2
   Prompt: Cadence DPI/DP bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && DRM_PANEL_BRIDGE [=y]

---

 CONFIG_DRM_LONTIUM_LT9611:

 Driver for Lontium LT9611 DSI to HDMI bridge
 chip driver that converts dual DSI and I2S to
 HDMI signals
 Please say Y if you have such hardware.

 Symbol: DRM_LONTIUM_LT9611 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:51
   Prompt: Lontium LT9611 DSI/HDMI bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: SND_SOC_HDMI_CODEC [=n] && DRM_PANEL_BRIDGE [=y] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]

---

 CONFIG_DRM_TOSHIBA_TC358762:

 Toshiba TC358762 DSI/DPI bridge driver.

 Symbol: DRM_TOSHIBA_TC358762 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:169
   Prompt: TC358762 DSI/DPI bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y]

---

 CONFIG_DRM_TOSHIBA_TC358775:

 Toshiba TC358775 DSI/LVDS bridge chip driver.

 Symbol: DRM_TOSHIBA_TC358775 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:205
   Prompt: Toshiba TC358775 DSI/LVDS bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:44 -04:00
Fedora Kernel Team 1339886293 [redhat] New configs in drivers/video
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BACKLIGHT_KTD253:

 Say y to enabled the backlight driver for the Kinetic KTD253
 which is a 1-wire GPIO-controlled backlight found in some mobile
 phones.

 Symbol: BACKLIGHT_KTD253 [=n]
 Type  : tristate
 Defined at drivers/video/backlight/Kconfig:185
   Prompt: Backlight Driver for Kinetic KTD253
   Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Graphics support
         -> Backlight & LCD device support
           -> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:44 -04:00
Fedora Kernel Team 121b91cf3e [redhat] AUTOMATIC: New configs 2021-08-30 14:29:44 -04:00
Fedora Kernel Team 78808877a2 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:44 -04:00
Brian Masney 313fcdd239 RHMAINTAINERS: add GPIO subsystem and update pinctrl entry
Add myself and darcari as maintainers for the GPIO and pinctrl
subsystems.

CC: David Arcari <darcari@redhat.com>
Signed-off-by: Brian Masney <bmasney@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:29:44 -04:00
Prarit Bhargava 7021cc0792 RHMAINTAINERS: Update vmxnet3 driver entry
Assign the vmxnet3 driver to Cathy Avery.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: cavery@redhat.com
Cc: linville@redhat.com
2021-08-30 14:29:43 -04:00
Jan Stancek ce9d032d92 RHMAINTAINERS: add entry for 8.4
Add entry for 8.4.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:29:43 -04:00
Jerry Snitselaar 240c5f6d8d configs/iommu: Add config comment to empty CONFIG_SUN50I_IOMMU file
Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
2021-08-30 14:29:43 -04:00
Fedora Kernel Team e1387b2991 [redhat] New configs in drivers/iommu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

---

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:43 -04:00
Fedora Kernel Team 53fe0c0142 [redhat] New configs in drivers/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_XILINX_ZYNQMP_DPDMA:

 Enable support for Xilinx ZynqMP DisplayPort DMA. Choose this option
 if you have a Xilinx ZynqMP SoC with a DisplayPort subsystem. The
 driver provides the dmaengine required by the DisplayPort subsystem
 display driver.

 Symbol: XILINX_ZYNQMP_DPDMA [=n]
 Type  : tristate
 Defined at drivers/dma/Kconfig:711
   Prompt: Xilinx DPDMA Engine
   Depends on: DMADEVICES [=y]
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
 Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:43 -04:00
Fedora Kernel Team 8b47920c92 [redhat] New configs in kernel/bpf
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BPF_PRELOAD:

 This builds kernel module with several embedded BPF programs that are
 pinned into BPF FS mount point as human readable files that are
 useful in debugging and introspection of BPF programs and maps.

 Symbol: BPF_PRELOAD [=n]
 Type  : bool
 Defined at kernel/bpf/preload/Kconfig:6
   Prompt: Preload BPF file system with kernel specific program and map iterators
   Depends on: BPF [=y] && !COMPILE_TEST [=n]
   Location:
     -> General setup
 Selects: USERMODE_DRIVER [=n]

---

Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Yauheni Kaliuta <ykaliuta@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:43 -04:00
Fedora Kernel Team cfa566fd1c [redhat] New configs in lib/Kconfig.kasan
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TEST_KASAN_MODULE:

 This is a part of the KASAN test suite that is incompatible with
 KUnit. Currently includes tests that do bad copy_from/to_user
 accesses.

 Symbol: TEST_KASAN_MODULE [=n]
 Type  : tristate
 Defined at lib/Kconfig.kasan:181
   Prompt: KUnit-incompatible tests of KASAN bug detection capabilities
   Depends on: m && MODULES [=y] && KASAN [=y]
   Location:
     -> Kernel hacking
       -> Memory Debugging
         -> KASAN: runtime memory debugger (KASAN [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:43 -04:00
Fedora Kernel Team 053fc96ab7 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TEST_FREE_PAGES:

 Test that a memory leak does not occur due to a race between
 freeing a block of pages and a speculative page reference.
 Loading this module is safe if your kernel has the bug fixed.
 If the bug is not fixed, it will leak gigabytes of memory and
 probably OOM your system.

 Symbol: TEST_FREE_PAGES [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:2370
   Prompt: Test freeing pages
   Depends on: RUNTIME_TESTING_MENU [=y]
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Runtime Testing (RUNTIME_TESTING_MENU [=y])

---

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:43 -04:00
Fedora Kernel Team 3e2a77ae5b New configs in kernel/trace
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HIST_TRIGGERS_DEBUG:

 Add "hist_debug" file for each event, which when read will
 dump out a bunch of internal details about the hist triggers
 defined on that event.

 The hist_debug file serves a couple of purposes:

   - Helps developers verify that nothing is broken.

   - Provides educational information to support the details
     of the hist trigger internals as described by
     Documentation/trace/histogram-design.rst.

 The hist_debug output only covers the data structures
 related to the histogram definitions themselves and doesn't
 display the internals of map buckets or variable values of
 running histograms.

 If unsure, say N.

 Symbol: HIST_TRIGGERS_DEBUG [=n]
 Type  : bool
 Defined at kernel/trace/Kconfig:850
   Prompt: Hist trigger debug support
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && HIST_TRIGGERS [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])

Cc: Jerome Marchand <jmarchan@redhat.com>
2021-08-30 14:29:42 -04:00
Justin M. Forbes 92a8ceba7a Fix Fedora config locations
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:42 -04:00
Justin M. Forbes d74a4f5eaf Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:42 -04:00
Fedora Kernel Team 16c0d6b47d [redhat] New configs in net/can
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CAN_ISOTP:

 CAN Transport Protocols offer support for segmented Point-to-Point
 communication between CAN nodes via two defined CAN Identifiers.
 As CAN frames can only transport a small amount of data bytes
 (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
 segmentation is needed to transport longer PDUs as needed e.g. for
 vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
 This protocol driver implements data transfers according to
 ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
 If you want to perform automotive vehicle diagnostic services (UDS),
 say 'y'.

 Symbol: CAN_ISOTP [=n]
 Type  : tristate
 Defined at net/can/Kconfig:58
   Prompt: ISO 15765-2:2016 CAN transport protocol
   Depends on: NET [=y] && CAN [=m]
   Location:
     -> Networking support (NET [=y])
       -> CAN bus subsystem support (CAN [=m])

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:42 -04:00
Fedora Kernel Team cf94741547 [redhat] New configs in drivers/acpi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DPTF_PCH_FIVR:

 This driver adds support for Dynamic Platform and Thermal Framework
 (DPTF) PCH FIVR Participant device support. This driver allows to
 switch PCH FIVR (Fully Integrated Voltage Regulator) frequency.
 This participant is responsible for exposing:
       freq_mhz_low_clock
       freq_mhz_high_clock

 To compile this driver as a module, choose M here:
 the module will be called dptf_pch_fivr.

 Symbol: DPTF_PCH_FIVR [=n]
 Type  : tristate
 Defined at drivers/acpi/dptf/Kconfig:18
   Prompt: DPTF PCH FIVR Participant
   Depends on: ACPI [=y] && X86 [=y]
   Location:
     -> Power management and ACPI options
       -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])

---

Cc: Al Stone <ahs3@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:42 -04:00
Fedora Kernel Team 3b18eba1d2 [redhat] New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_MSM8226:

 This is the pinctrl, pinmux, pinconf and gpiolib driver for the
 Qualcomm Technologies Inc TLMM block found on the Qualcomm
 Technologies Inc MSM8226 platform.

 Symbol: PINCTRL_MSM8226 [=n]
 Type  : tristate
 Defined at drivers/pinctrl/qcom/Kconfig:65
   Prompt: Qualcomm 8226 pin controller driver
   Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_MSM [=y]

---

Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:42 -04:00
Fedora Kernel Team 86475f5597 [redhat] New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_INTEL_M10_BMC:

 Support for the Intel MAX 10 board management controller using the
 SPI interface.

 This driver provides common support for accessing the device,
 additional drivers must be enabled in order to use the functionality
 of the device.

 Symbol: MFD_INTEL_M10_BMC [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:2156
   Prompt: Intel MAX 10 Board Management Controller
   Depends on: HAS_IOMEM [=y] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: REGMAP_SPI_AVMM [=n] && MFD_CORE [=y]

---

 CONFIG_MFD_SL28CPLD:

 Say yes here to enable support for the Kontron sl28cpld board
 management controller.

 It can be found on the following boards:
       * SMARC-sAL28

 Symbol: MFD_SL28CPLD [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:1189
   Prompt: Kontron sl28cpld Board Management Controller
   Depends on: HAS_IOMEM [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_SIMPLE_MFD_I2C [=n]

---

Cc: Torez Smith <torez@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:42 -04:00
Fedora Kernel Team 9f1cb20808 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:41 -04:00
Fedora Kernel Team a4cfa0c313 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:41 -04:00
Vladis Dronov 9679214320 configs: enable CONFIG_CRYPTO_CTS=y so cts(cbc(aes)) is available in FIPS mode
Currently the CTS algo is built as a module. This is a problem if any
ciphers using CTS are marked as FIPS-enabled and the system is booted
in FIPS mode, as dracut does not include cts.ko in the initramfs. This
change is necessary for NFS with sec=krb5{,i,p} to work in FIPS mode.
Otherwise, the following panic would result:

[    8.462065] alg: skcipher: Failed to load transform for cts(cbc(aes)): -2
[    8.463705] Kernel panic - not syncing: cts(cbc(aes)): cts(cbc(aes)) alg self test failed in fips mode!

Fix this by embedding the CTS code into a kernel, the same way as Fedora
already does. This was tested by a reproducer in bz1855161 #c24, #c28.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1855161
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-08-30 14:29:41 -04:00
Fedora Kernel Team 9b9b496881 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:41 -04:00
Fedora Kernel Team 9de149380c [redhat] AUTOMATIC: New configs 2021-08-30 14:29:41 -04:00
Don Zickus 40f49bb290 Partial revert: Add master merge check
I created an optimization to speed up the automated scripts when there was
nothing to merge in redhat/scripts/ci/ark-update-configs.sh under
2d1d129bbe

The thought was, if 'master' wasn't updated or needed merging, how can there be
any new configs to add?

Well it turns out that when merge conflicts arise, the merge of master into
os-build has to be done by hand and pushed manually.  This usually skips the
new config generation.

The above optimization then skips the config generation on later cron jobs
because the merge already happened (until the master is actually updated).

There is nothing wrong with re-running the config generation script even if
there is nothing to do.  Just undo the optimization.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:41 -04:00
Don Zickus 772442a5ab Update Maintainers doc to reflect workflow changes
Recently the maintainer workflow has been changed to include a single os-build
branch for development and various makefile scripts to help with automation.
Update the docs to reflect that.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:41 -04:00
Prarit Bhargava 28b264afbd WIP: redhat/docs: Update documentation for single branch workflow
The kernel-ark wiki needs an update after the inclusion of the single
branch workflow patches.

Update documentation for the single branch workflow.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
2021-08-30 14:29:41 -04:00
Justin M. Forbes b64b54aa87 Add CONFIG_ARM64_MTE which is not picked up by the config scripts for some reason
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:41 -04:00
Fedora Kernel Team 7b0a918180 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_ADM1266:

 If you say yes here you get hardware monitoring support for Analog
 Devices ADM1266 Cascadable Super Sequencer.

 This driver can also be built as a module. If so, the module will
 be called adm1266.

 Symbol: SENSORS_ADM1266 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:29
   Prompt: Analog Devices ADM1266 Sequencer
   Depends on: HWMON [=y] && PMBUS [=m] && GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])
 Selects: CRC8 [=m]

---

 CONFIG_SENSORS_MP2975:

 If you say yes here you get hardware monitoring support for MPS
 MP2975 Dual Loop Digital Multi-Phase Controller.

 This driver can also be built as a module. If so, the module will
 be called mp2975.

 Symbol: SENSORS_MP2975 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:214
   Prompt: MPS MP2975
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

 CONFIG_SENSORS_MR75203:

 If you say yes here you get support for Moortec MR75203
 PVT controller.

 This driver can also be built as a module. If so, the module
 will be called mr75203.

 Symbol: SENSORS_MR75203 [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:1115
   Prompt: Moortec Semiconductor MR75203 PVT Controller
   Depends on: HWMON [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
 Selects: REGMAP_MMIO [=n]

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:40 -04:00
Fedora Kernel Team b6fa201ba1 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:40 -04:00
Fedora Kernel Team 650dd561b5 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:40 -04:00
Prarit Bhargava 87e2dc584a RHMAINTAINERS: Update with new entries
Add new entries for

- drivers/bus
- drivers/dma
- drivers/firmware
- drivers/leds
- drivers/mailbox
- drivers/mfd
- drivers/platform
- drivers/power
- drivers/spi
- usr/

Also make a small change and rename "LINUX FOR POWERPC" to just "POWERPC".

RH-Acked-by: Torez Smith <torez@redhat.com>
RH-Acked-by: Lenny Szubowicz <lszubowi@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Al Stone <ahs3@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Lenny Szubowicz <lszubowi@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Steve Best <sbest@redhat.com>
Cc: Tony Camuso <tcamuso@redhat.com>
Cc: Torez Smith <torez@redhat.com>
Cc: Al Stone <ahs3@redhat.com>
2021-08-30 14:29:40 -04:00
Justin M. Forbes 233c97b68e Disable Speakup synth DECEXT
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:40 -04:00
Justin M. Forbes 4743bb76cc Enable Speakup for Fedora since it is out of staging
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 14:29:40 -04:00
Don Zickus b322b38269 Modify patchlist changelog output
Based on a suggestion from Thorsten Leemhuis.

Thorsten suggested making it easier to see that individual change
by embedding the url to the commit in the patchlist.changelog file.

This change does exactly that.

Old output:
e338eecf3f PCI: rockchip: Fix bus checks in rockchip_pcie_valid_device()
850280156f phy: ti: am654: Fix a leak in serdes_am654_probe()
43557447af gitattributes: Remove unnecesary export restrictions
f003c79ead Add RHMAINTAINERS file and supporting conf
825b7aa116 gitlab: Add CI job for packaging scripts

New output:
e338eecf3f
 e338eecf3f PCI: rockchip: Fix bus checks in rockchip_pcie_valid_device()

850280156f
 850280156f phy: ti: am654: Fix a leak in serdes_am654_probe()

43557447af
 43557447af gitattributes: Remove unnecesary export restrictions

f003c79ead
 f003c79ead Add RHMAINTAINERS file and supporting conf

825b7aa116
 825b7aa116 gitlab: Add CI job for packaging scripts

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:40 -04:00
Tony Camuso aca5291cda RHMAINTAINERS: Add ipmi files
IPMI entry was missing the file list.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>

Signed-off-by: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:29:40 -04:00
Prarit Bhargava a3d22a6aeb RHMAINTAINERS: Add entire drivers/nvme to NVM EXPRESS DRIVER entry
Currently drivers/nvme/Kconfig is not identified as belonging to the
NVM EXPRESS DRIVER maintainers.  Add the entire drivers/nvme/ directory
to capture all code.

RH-Acked-by: Gopal Tiwari <gtiwari@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Milburn <dmilburn@redhat.com>
Cc: Gopal Tiwari <gtiwari@redhat.com>
2021-08-30 14:29:40 -04:00
Prarit Bhargava 17687b8b4a RHMAINTAINERS: Reorganize some entries
Put entries back in alphabetical order.

RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: Bruno Meneguele <bmeneg@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:29:40 -04:00
Prarit Bhargava 02d34c1b6f RHMAINTAINERS: Add security subsystem entry
Add an entry for the common Linux Security Module infrastructure, which
is crucical for SELinux and other security features. Add myself as the
maintainer, since I already need to maintain it because of SELinux.

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:29:39 -04:00
Ben Crocker bd959a665c process_configs.sh: Fix syntax flagged by shellcheck
• SC2006: Use $(...) notation instead of legacy backticked `...`.
• SC2034: <variable> appears unused. Verify use (or export if used externally).
• SC2038: Use -print0/-0 or find -exec + to allow for non-alphanumeric filenames.
• SC2045: Iterating over ls output is fragile. Use globs.
• SC2046: Quote this to prevent word splitting.
• SC2086: Double quote to prevent globbing and word splitting.
• SC2231: Quote expansions in this for-loop glob to prevent wordsplitting, e.g. "$dir"/*.txt .

Ignore:
• SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:29:39 -04:00
Ben Crocker c4358a1655 generate_all_configs.sh: Fix syntax flagged by shellcheck
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2039: In POSIX sh, == in place of = is undefined.  (NOTE: works fine in bash.)
SC2086: Double quote to prevent globbing and word splitting.
SC2231: Quote expansions in this for-loop glob to prevent wordsplitting, e.g. "$dir"/*.txt .

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:29:39 -04:00
Ben Crocker 17ee283cec redhat/self-test: Initial commit
0001-shellcheck.bats
• tests whether all scripts under redhat/ pass shellcheck

1001-rpmlint.bats
• tests for exactly one SRPM
• runs rpmlint on that SRPM

1002-basic-structural-test.bats
• tests whether SRPM unpacks OK
• tests whether Linux tree unpacks OK
• runs top-level structural check on Linux tree

Nothing is hooked up yet, i.e. there is no Makefile target that
invokes these tests; however, tests may be run manually using the
bats command, e.g.

• bats 0001-shellcheck.bats
• bats *.bats

Requires installation of the 'bats' package; shellcheck tests require
the 'ShellCheck' package (note capitalization):

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 14:29:39 -04:00
Fedora Kernel Team d8e6c23974 [redhat] New configs in drivers/video
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FB_ARMCLCD:

 This framebuffer device driver is for the ARM PrimeCell PL110
 Colour LCD controller.  ARM PrimeCells provide the building
 blocks for System on a Chip devices.

 If you want to compile this as a module (=code which can be
 inserted into and removed from the running kernel), say M
 here and read <file:Documentation/kbuild/modules.rst>.  The module
 will be called amba-clcd.

 Symbol: FB_ARMCLCD [=n]
 Type  : tristate
 Defined at drivers/video/fbdev/Kconfig:275
   Prompt: ARM PrimeCell PL110 support
   Depends on: (ARM || ARM64 [=y] || COMPILE_TEST [=n]) && FB [=y] && ARM_AMBA [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Frame buffer Devices
           -> Support for frame buffer devices (FB [=y])
 Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && FB_CFB_IMAGEBLIT [=y] && FB_MODE_HELPERS [=n] && VIDEOMODE_HELPERS [=n] && BACKLIGHT_CLASS_DEVICE [=y]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 14:29:39 -04:00
Fedora Kernel Team ff080459f8 [redhat] AUTOMATIC: New configs 2021-08-30 14:29:39 -04:00
Peter Robinson ae14bf5c73 Fixes "acpi: prefer booting with ACPI over DTS" to be RHEL only
The ACPI prefernce is RHEL specific, in Fedora we use upstream defaults so
it doesn't randomly change the expectations as to how certain hardware works
that generally isn't classed as "enterprise". So wrap it in the special RHEL
check as it should be for the ARK kernels.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
CC: Mark Salter <msalter@redhat.com>
2021-08-30 14:29:39 -04:00
Prarit Bhargava 702d353d2f arch/x86: Remove vendor specific CPU ID checks
Upstream Status: RHEL only

After discussions with Devel, QE, Support, and Certification we have
decided to drop the CPU specific checks in rh_check_supported().
Certification is adopting a new process in which CPU certifications will
be tracked on https://catalog.redhat.com.

Remove the vendor specific CPU ID checks from rh_check_supported().

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
2021-08-30 14:29:39 -04:00
Prarit Bhargava e87219730d redhat: Replace hardware.redhat.com link in Unsupported message
Resending ... did not get any reviews.

P.

---8<---

Bugzilla: http://bugzilla.redhat.com/1810301
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=27902812
Local Tree: git://git.engineering.redhat.com/users/prarit/rhel8 1810301

Upstream Status: RHEL only

For almost a decade, RHEL kernels have output the message

"this hardware has not undergone testing by Red Hat and might not be
certified. Please consult https://hardware.redhat.com for certified
hardware."

for unsupported hardware.  This link should be now be updated to the
new catalog.redhat.com location.  The old hardware.redhat.com is now
redirecting to catalog.redhat.com for older releases.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
2021-08-30 14:29:39 -04:00
Don Zickus 83e4c12bcf x86: Fix compile issues with rh_check_supported()
Upstream status: RHEL only

The function rh_check_supported is a RHEL function to limit the
platforms RHEL does not want to support.

To avoid imposing this requirement on Fedora, the function was
wrapped with CONFIG_RHEL_DIFFERENCES so Fedora can disable this.

However, this has a few compile warnings that need to be cleaned up
when disabled.

Move CONFIG_RHEL_DIFFERENCES to include the functions themselves
instead of the call.  As the unused functions created warnings.

V2: modified stub definition

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 14:29:38 -04:00
Robert Holmes 5e0381929c KEYS: Make use of platform keyring for module signature verify
This patch completes commit 278311e417 ("kexec, KEYS: Make use of
platform keyring for signature verify") which, while adding the
platform keyring for bzImage verification, neglected to also add
this keyring for module verification.

As such, kernel modules signed with keys from the MokList variable
were not successfully verified.

Signed-off-by: Robert Holmes <robeholmes@gmail.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:38 -04:00
Benjamin Tissoires 518428c950 Input: rmi4 - remove the need for artificial IRQ in case of HID
The IRQ from rmi4 may interfere with the one we currently use on i2c-hid.
Given that there is already a need for an external API from rmi4 to
forward the attention data, we can, in this particular case rely on a
separate workqueue to prevent cursor jumps.

Reported-by: Cameron Gutman <aicommander@gmail.com>
Reported-by: Thorsten Leemhuis <linux@leemhuis.info>
Reported-by: Jason Ekstrand <jason@jlekstrand.net>
Tested-by: Andrew Duggan <aduggan@synaptics.com>
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Lyude <lyude@redhat.com>
2021-08-30 14:29:38 -04:00
Peter Robinson 67898d5790 ARM: tegra: usb no reset
Patch for disconnect issues with storage attached to a
 tegra-ehci controller
2021-08-30 14:29:38 -04:00
Jon Masters 80a44e877e arm: make CONFIG_HIGHPTE optional without CONFIG_EXPERT
We will use this to force CONFIG_HIGHPTE off on LPAE for now

Signed-off-by: Jon Masters <jcm@redhat.com>
2021-08-30 14:29:38 -04:00
Jiri Benc 2843fcb40c redhat: rh_kabi: deduplication friendly structs
RH-Acked-by: Bruno Meneguele <bmeneg@redhat.com>
RH-Acked-by: Jesper Brouer <brouer@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Olsa <jolsa@redhat.com>
RH-Acked-by: Toke Høiland-Jørgensen <toke@redhat.com>

Upstream status: RHEL only

We don't really need the field names to be globally unique, it is enough
when they are unique in the given struct. Since structs do not generally
span mutliple files, using the line number is enough to ensure an unique
identifier. It means that we can't use two RH_KABI_RENAME macros on the same
line but that's not happening anyway.

This allows pahole to deduplicate the type info of structs using kABI
macros, lowering the size of vmlinuz from 26M to 8.5M.

Upstream Status: RHEL only
Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 14:29:38 -04:00
Jiri Benc 687fba0fbf redhat: rh_kabi add a comment with warning about RH_KABI_EXCLUDE usage
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>

Upstream status: RHEL only

We've seen attempts of incorrect RH_KABI_EXCLUDE usage. The macro is
dangerous and any structure marked by it becomes fragile. It completely
mutes the kABI checker and a future attempt to whitelist anything using
a structure annotated by RH_KABI_EXCLUDE will generate easily broken, error
prone code. Also, it bypasses module loading checks for the structure and
can lead to kernel crashes triggered by 3rd party modules unless carefully
prevented by RH_KABI_FORCE_CHANGE.

As such, it should not be used routinely. The only valid usage is a code
heavily in flux upstream that is going to be refactored and turned upside
down, which is indirectly whitelisted and which we expect to need
backported.

Any usage of this macro requires deep understanding of how kABI works.

Add a big fat warning to stop the misuse.

Upstream Status: RHEL only
Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 14:29:38 -04:00
Jiri Benc f5c00a7c20 redhat: rh_kabi: introduce RH_KABI_EXTEND_WITH_SIZE
RH-Acked-by: Toke Høiland-Jørgensen <toke@redhat.com>
RH-Acked-by: Hangbin Liu <haliu@redhat.com>

Upstream status: RHEL only

This allows addition of a struct into struct while reserving extra space.
See the documentation in rh_kabi.h for details.

The check for size is automatically disabled in -debug kernels that have
many fields larger than the production kernels (mutexes etc.) and that are
not under kABI guarantee.

I'm also moving a misplaced comment for RH_KABI_FILL_HOLE.

(Pointed out by Sabrina:) We need to force align the added field to 8 byte
offset. Otherwise, if the required alignment of the added field changed
later (e.g. it was a structure with only a single field that was changed
from int to char) and the previous field was smaller than long, it could
lead to the whole union shifting position and offsets of the following
fields could change. It's also safer to align the size, too.

Let the 'size' parameter specify number of longs to be added and not number
of bytes. Note we assume a 64 bit architecture, which is the case for RHEL.

Upstream Status: RHEL only
Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 14:29:38 -04:00
Don Dutile 5318263465 redhat: rh_kabi: Indirect EXTEND macros so nesting of other macros will resolve.
RH-Acked-by: Neil Horman <nhorman@redhat.com>
RH-Acked-by: Jonathan Toppins <jtoppins@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

Upstream status: RHEL only

rh_kabi: Indirect EXTEND macros so nesting of other macros will resolve.

Upstream Status: RHEL only
Suggested-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Donald Dutile <ddutile@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 14:29:38 -04:00
Tony Camuso d2e466ff7a redhat: rh_kabi: Fix RH_KABI_SET_SIZE to use dereference operator
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

Upstream Status: RHEL only

Since this macro is intended to record the sizeof extension structs that
are dynamically allocated, using the structure dereference operator '->'
is a better choice, else the macro would have to be invoked with the
_name argument dereferenced as (*_name).

Also added a short note explaining that, unlike the other RH_KABI
macros that are invoked from within structs, this macro is invoked
outside a struct and therefore needs a semicolon termination.

Upstream Status: RHEL only
Signed-off-by: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 14:29:38 -04:00
Prarit Bhargava 2211cd0f70 redhat: rh_kabi: Add macros to size and extend structs
RH-Acked-by: Ivan Vecera <ivecera@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

Upstream: RHEL-only

As noted in the reviews, there are some areas of future work:

1) A further restriction on the access of the extended struct fields
would be to require the addition of an accessor function.
2) Additional macros to use RH_KABI_EXTEND fields.
3) Additional macros to mark extended struts' field for internal kernel
versus module use.

The RHEL7 code contains macros to extend kernel structs.  For example, the
RH_KABI_EXTEND() can be used to extend a struct when used appropriately.
This macro (and others similar to it) has a significant shortcoming as it
cannot be used in the case where a struct is known to allocate the struct
within a 3rd party module.  For example, in RHELX.0, suppose there exists
a struct,

struct in_kernel {
	int foo0;
};

and an exported function,

void in_kernel_set_foo(struct in_kernel *ink)
{
	...
	ink->foo0 = 0xBA5EBA11;
	...
}

Let's also suppose a struct in_kernel is statically defined within a 3rd
party module, or dynamically allocated as

	struct in_kernel *3rd_party_ink;
	...
	ink = kmalloc(sizeof(*3rd_party_ink), GFP_KERNEL);
	...

In RHELX.1, suppose the struct is expanded by

struct in_kernel {
	int foo0;
	RH_KABI_EXTEND(foo1)
};

and the exported function is modified as

void in_kernel_set_foo(struct in_kernel *ink)
{
	...
	ink->foo0 = 0xBA5EBA11;
	ink->foo1 = 0xBA5EBA11;
	...
}

The 3rd party module, compiled against RHELX.0, will not have allocated
memory for foo1, and in_kernel_set_foo() will reference garbage in memory.

To fix this problem, Jiri Benc came up with an great solution that should
be unified for all future RHELX.0 expansions of structs.  RHEL7 commit
e33a3c136b56 ("[net] introduce net_device_ops_extended") adds a size
parameter to net_device_ops that can be queried to validate memory
accesses.  In the patch, net_device_ops is expanded by embedding a
net_device_ops_extended struct and addig a size parameter.  The size
parameter is used to compare the offset of a parameter in the
net_device_ops_extended struct to the size of the struct at compile time,
and if valid, the memory access can be programmatically allowed to occur.

I have taken his idea and created several new standard macros that allow
structs to be expanded by embedding a new struct or by adding a pointer
to a new struct.

There are, however, some rules that must be followed when using these
new macros:

1.  The default name of the extended struct is ##name##_rh.  For example,
pci_dev_rh, device_rh, net_device_ops_rh, etc.
2.  _rh structs cannot be shrunk in size as such changes would break the
size & offset comparison.
3.  The size field _must_ be set at the spot of allocation for use.  Use of the
_rh fields without setting the size field via RH_KABI_SET_SIZE|_PTR() is
invalid in the kernel or in a 3rd party module.
4.  These new macros do not preclude expansions like

struct in_kernel_rh {
};

struct in_kernel {
	...
	RH_KABI_EXTEND(void *ptr1)
	RH_KABI_EXTEND(void *ptr2)
	RH_KABI_EXTEND(void *ptr3)
	RH_KABI_EXTEND(void *ptr4)
	RH_KABI_SIZE_AND_EXTEND_PTR(in_kernel)
};

These macros are generally intended for pre-KABI freeze use, however,
there may be cases where these macros can be used post-KABI freeze.
Due to the design of RH_KABI_EXTEND() which embeds __GENKSYMS__ care must
be taken when using RH_KABI_SIZE_AND_EXTEND|_PTR() post-KABI freeze to
ensure that structs are not embedded within another struct, verifying
offsets, etc.

Add RH_KABI_SIZE_AND_EXTEND(), RH_KABI_SIZE_AND_EXTEND_PTR(), and
other macros that allow for safe expansion of structs.

v2: Cleanup comments.
v3: Cleanup comments.

Upstream Status: RHEL only
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 14:29:38 -04:00
Dick Kennedy 7ed290f787 Removing Obsolete hba pci-ids from rhel8
Message-id: <1525206184-20470-1-git-send-email-dkennedy@redhat.com>
Patchwork-id: 212089
O-Subject: [RHEL8 PATCH e-stor] Removing Obsolete hba pci-ids from rhel8.
Bugzilla: 1572321
RH-Acked-by: Chris Leech <cleech@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

These adapters printed an Obsolete Unsupported message is rhel7. They
are being removed for rhel8

brew-id: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID^U948800
bugzilla: 1572321
tested on: rhel-storage-44 and on rhel-storage-07

RHEL Specific

Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Backport Notes: Simplify by filtering using pci_ids
-
2021-08-30 14:29:37 -04:00
Laura Abbott ee382017e8 mptsas: pci-id table changes
Author: Tomas Henzl <thenzl@redhat.com>
Date:   Thu Jan 31 16:54:51 2019 -0500

    [message] mptsas: pci-id table changes

    Message-id: <20190131165452.7562-3-thenzl@redhat.com>
    Patchwork-id: 239765
    O-Subject: [RHEL8 e-stor 2/3] mptsas: pci-id table changes
    Bugzilla: 1666730
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>

    RHEL-only

    We want to provide this driver only for the virtualisation use case,
    so we remove all other entries from the pci-id table and add only the
    single entry needed for virtualisation.

    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 14:29:37 -04:00
Laura Abbott c2b3035917 mptsas: Taint kernel if mptsas is loaded
Author: Tomas Henzl <thenzl@redhat.com>
Date:   Thu Jan 31 16:54:50 2019 -0500

    [message] mptsas: Taint kernel if mptsas is loaded

    Message-id: <20190131165452.7562-2-thenzl@redhat.com>
    Patchwork-id: 239764
    O-Subject: [RHEL8 e-stor 1/3] mptsas: Taint kernel if mptsas is loaded
    Bugzilla: 1666730
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>

    RHEL-only

    We are only keeping it to ease developer transitions, we're not
    supporting it, so mark it as unsupported by tainting the kernel and
    issuing an impossible to misunderstand message to the log

    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 14:29:37 -04:00
Laura Abbott 7034944b60 mptspi: pci-id table changes
Author: Tomas Henzl <thenzl@redhat.com>
Date:   Thu Jan 10 16:11:44 2019 -0500

    [message] mptspi: pci-id table changes

    Message-id: <20190110161145.5117-3-thenzl@redhat.com>
    Patchwork-id: 237190
    O-Subject: [RHEL-8.0 e-stor 2/3] mptspi: pci-id table changes
    Bugzilla: 1651803
    RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Chris Leech <cleech@redhat.com>

    RHEL-only
    We want to provide this driver only for the virtualisation use case,
    so we remove all other entries from the pci-id table and add only the
    single entry needed for virtualisation.

    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 14:29:37 -04:00
Jeremy Cline 344ae03f7e qla2xxx: Remove PCI IDs of deprecated adapter
Message-id: <20190708192223.21890-1-jcline@redhat.com>
Patchwork-id: 266422
O-Subject: [ARK INTERNAL PATCH] qla2xxx: Remove PCI IDs of deprecated adapter
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Commit ecc89f25e2 ("scsi: qla2xxx: Add Device ID for ISP28XX")
introduced addition device IDs which broke the patch context.

    Message-id: <20180503234750.33648-1-hmadhani@redhat.com>
    Patchwork-id: 212501
    O-Subject: [RHEL 8 e-stor PATCH v2] qla2xxx: Remove PCI IDs of deprecated adapter
    Bugzilla: 1572233
    RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
    RH-Acked-by: Chris Leech <cleech@redhat.com>
    RH-Acked-by: Tom Coughlan <coughlan@redhat.com>

    Bugzilla:
    ========    https://bugzilla.redhat.com/show_bug.cgi?id72233

    commit none

    Brewbuild:
    ==========    https://brewweb.engineering.redhat.com/brew/taskinfo?taskID977226

    Tetsing:
    =======    N/A. PCI IDs are removed as part of this patch

    Signed-off-by: Himanshu Madhani <hmadhani@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>

Note: Simplified backport to just pci-ids
2021-08-30 14:29:37 -04:00
Chris Leech 098baeebbe be2iscsi: remove unsupported device IDs
Message-id: <20180503194032.1461134-1-cleech@redhat.com>
Patchwork-id: 212454
O-Subject: [RHEL8 PATCH e-stor] scsi: be2iscsi: remove unsupported device IDs
Bugzilla: 1574502
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Tom Coughlan <coughlan@redhat.com>
RH-Acked-by: Ewan Milne <emilne@redhat.com>

Bugzilla: 1574502
Upstream Status: RHEL Specific
Build Info: brew 15975638

BladeEngine 2 generation devices are deprecated in RHEL 7
and not supported in RHEL 8

Signed-off-by: Chris Leech <cleech@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

be2iscsi: remove BE3 family support

Message-id: <1530890927-5792-1-git-send-email-mlombard@redhat.com>
Patchwork-id: 223576
O-Subject: [RHEL8 e-stor PATCH] be2iscsi: remove BE3 family support
Bugzilla: 1598366
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
RH-Acked-by: Chris Leech <cleech@redhat.com>

BZ: https://bugzilla.redhat.com/show_bug.cgi?id98366
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID996775
Upstream: RHEL-only, they tried to mark BE3 as unsupported
          in upstream kernel but the patch has been rejected.
          See: https://marc.info/?l=linux-scsi&m2835991600881&w=2

Broadcom doesn't want to provide support for the BE3 device family
in RHEL8.

This patch removes the BE3's PCI-IDs.

Upstream Status: RHEL only
Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:37 -04:00
Laura Abbott 67ac7dcc2a mptspi: Taint kernel if mptspi is loaded
Author: Tomas Henzl <thenzl@redhat.com>
Date:   Thu Jan 10 16:11:43 2019 -0500

    [message] mptspi: Taint kernel if mptspi is loaded

    Message-id: <20190110161145.5117-2-thenzl@redhat.com>
    Patchwork-id: 237188
    O-Subject: [RHEL-8.0 e-stor 1/3] mptspi: Taint kernel if mptspi is loaded
    Bugzilla: 1651803
    RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Chris Leech <cleech@redhat.com>

    RHEL-only
    We are only keeping it to ease developer transitions, we're not
    supporting it, so mark it as unsupported by tainting the kernel and
    issuing an impossible to misunderstand message to the log

    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 14:29:37 -04:00
Joseph Szczypek f609237dc9 hpsa: remove old cciss-based smartarray pci ids
Message-id: <1524750809-43700-2-git-send-email-jszczype@redhat.com>
Patchwork-id: 211573
O-Subject: [RHEL8 e-stor PATCH 1/2] hpsa: remove old cciss-based smartarray pci ids
Bugzilla: 1471185
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>

Per discussion with Microsemi, the old PCI IDs for smartarrays
originally used with the old cciss driver are not being
supported with RHEL8. They are also not supported with RHEL7.
Therefore the PCI IDs and the catch-all are being removed.

    Acked-by: Don Brace <don.brace@microsemi.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
2021-08-30 14:29:37 -04:00
Chad Dupuis c6b10bcd19 qla4xxx: Remove deprecated PCI IDs from RHEL 8
Message-id: <1524063895-23086-1-git-send-email-cdupuis@redhat.com>
Patchwork-id: 209742
O-Subject: [RHEL 8 e-stor PATCH] qla4xxx: Remove depricated PCI IDs from RHEL 8.
Bugzilla: 1518874
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Bugzilla: 1518874

RHEL 8 specific

Brew build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID822250

Three PCI device IDs are marked as deprecated in RHEL 7:

PCI_DEVICE_ID_QLOGIC_ISP8022
PCI_DEVICE_ID_QLOGIC_ISP8324
PCI_DEVICE_ID_QLOGIC_ISP8042

This patch removes them from the PCI table in RHEL 8 so the
qla4xxx driver will not bind to the hardware.

Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:37 -04:00
Raghava Aditya Renukunta 81abd2b189 aacraid: Remove depreciated device and vendor PCI id's
Message-id: <20180315040041.9449.8525.stgit@dhcp187-32.khw.lab.eng.bos.redhat.com>
Patchwork-id: 206793
O-Subject: [RHEL8 e-stor PATCH] scsi: aacraid: Remove depreciated device and vendor PCI id's
Bugzilla: 1495307
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id95307
Brew Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID552286
Upstream Status: N/A (RHEL 8 internal)
Tested: Code Review

Remove Vendor PCI ID and Device PCI ID of depreciated devices from
aacraid pci table, preventing these device from attaching to the aacraid
driver.

Upstream Status: RHEL only
Signed-off-by: Raghava Aditya Renukunta <rrenukun@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:37 -04:00
Tomas Henzl 9e89075cef megaraid_sas: remove deprecated pci-ids
Message-id: <20180403143030.4971-2-thenzl@redhat.com>
Patchwork-id: 7432
O-Subject: [kernel team] [RHEL8 e-stor PATCH] megaraid_sas: remove deprecated pci-ids
Bugzilla: 1509329
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Chris Leech <cleech@redhat.com>

bz#1509329
brew - task_15594743

RH specific - remove EOL devices from the pci-id table
(devices to remove were selected by Broadcom)

Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:36 -04:00
Jeremy Cline 60f540b911 mpt*: remove certain deprecated pci-ids
Message-id: <20190708192032.20922-1-jcline@redhat.com>
Patchwork-id: 266421
O-Subject: [ARK INTERNAL PATCH] mpt*: remove certain deprecated pci-ids
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Commit 8f8384503e ("scsi: mpt3sas: Add support for NVMe Switch
Adapter") introduced a new PCI device ID which broke the patch context.

    Message-id: <20180403143030.4971-1-thenzl@redhat.com>
    Patchwork-id: 7431
    O-Subject: [kernel team] [RHEL8 e-stor PATCH] mpt*: remove certain deprecated pci-ids
    Bugzilla: 1511953
    RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
    RH-Acked-by: Chris Leech <cleech@redhat.com>

    bz#1511953
    brew - task_15594743

    RH specific - remove EOL devices from the pci-id table
    (devices to remove were selected by Broadcom)

    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:36 -04:00
Tomas Henzl 8a9bf88e9d kernel: add SUPPORT_REMOVED kernel taint
Message-id: <e9a9812a-6a4c-a205-e66a-1d47de58306a@redhat.com>
Patchwork-id: 226423
O-Subject: [RHEL-8.0 V4 01/10] kernel: add SUPPORT_REMOVED kernel taint
Bugzilla: 1602033
RH-Acked-by: Maurizio Lombardi <mlombard@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Rob Evers <revers@redhat.com>

Upstream Status: RHEL only

rh_taint, pci : add information about removed hardware

Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:36 -04:00
Don Zickus 096684c2cb Rename RH_DISABLE_DEPRECATED to RHEL_DIFFERENCES
The intent of RH_DISABLE_DEPRECATED was to provide Red Hat a
simple way to disable drivers it did not want to support in RHEL.

As the config option was applied to more drivers and infra, it became
clear the option was being used for not only deprecating drivers (which
implied limited support) to disabling drivers (implying no support).

Using the word 'deprecated' seemed confusing in the second scenario.
Rename the option to be more generic and useable across more parts
of the kernel tree.

The new wording is RHEL_DIFFERENCES.

Upstream Status: RHEL only
2021-08-30 14:29:36 -04:00
Peter Robinson 9c5c002fb6 Add option of 13 for FORCE_MAX_ZONEORDER
This is a hack, but it's what the other distros currently use
for aarch64 with 4K pages so we'll do the same while upstream
decides what the best outcome is (which isn't this).

Upstream Status: RHEL only
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
[Add a dependency on RHEL_DIFFERENCES]
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:36 -04:00
Jeremy Cline 0d4a6e4961 s390: Lock down the kernel when the IPL secure flag is set
Automatically lock down the kernel to LOCKDOWN_CONFIDENTIALITY_MAX if
the IPL secure flag is set.

Upstream Status: RHEL only
Suggested-by: Philipp Rudo <prudo@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:36 -04:00
David Howells dc67b5f4fd efi: Lock down the kernel if booted in secure boot mode
UEFI Secure Boot provides a mechanism for ensuring that the firmware
will only load signed bootloaders and kernels.  Certain use cases may
also require that all kernel modules also be signed.  Add a
configuration option that to lock down the kernel - which includes
requiring validly signed modules - if the kernel is secure-booted.

Upstream Status: RHEL only
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:36 -04:00
David Howells 22705ce40e efi: Add an EFI_SECURE_BOOT flag to indicate secure boot mode
UEFI machines can be booted in Secure Boot mode.  Add an EFI_SECURE_BOOT
flag that can be passed to efi_enabled() to find out whether secure boot is
enabled.

Move the switch-statement in x86's setup_arch() that inteprets the
secure_boot boot parameter to generic code and set the bit there.

Upstream Status: RHEL only
Suggested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
cc: linux-efi@vger.kernel.org
[Rebased for context; efi_is_table_address was moved to arch/x86]
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:36 -04:00
Jeremy Cline 7eb67f94a0 security: lockdown: expose a hook to lock the kernel down
In order to automatically lock down kernels running on UEFI machines
booted in Secure Boot mode, expose the lock_kernel_down() hook.

Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:36 -04:00
Peter Jones 93e316e604 Make get_cert_list() use efi_status_to_str() to print error messages.
Upstream Status: RHEL only
Signed-off-by: Peter Jones <pjones@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:36 -04:00
Peter Jones 7408475406 Add efi_status_to_str() and rework efi_status_to_err().
This adds efi_status_to_str() for use when printing efi_status_t
messages, and reworks efi_status_to_err() so that the two use a common
list of errors.

Upstream Status: RHEL only
Signed-off-by: Peter Jones <pjones@redhat.com>
2021-08-30 14:29:35 -04:00
Laura Abbott 2ebec7e205 Add support for deprecating processors
Message-id: <20191113144431.9403-4-labbott@redhat.com>
Patchwork-id: 286081
O-Subject: [ARK INTERNAL PATCHv2 3/4] [redhat] Add support for deprecating processors
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

This is the squashed version of the following patches
modifed to use the new CONFIG_RH_DISABLE_DEPRECATED option

add rh_check_supported

Message-id: <1525313397-75200-1-git-send-email-darcari@redhat.com>
Patchwork-id: 212189
O-Subject: [RHEL8.0 BZ 1565717 v2] x86: add rh_check_supported
Bugzilla: 1565717
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: Mikulas Patocka <mpatocka@redhat.com>

Description:

Add code to verify that the booted x86 processor is supported by
Red Hat.  In cases where the processor is not supported a critical
message is logged.

Initially the supported set of processors for RHEL8 remains the same
as RHEL7.

Bugzilla: http://bugzilla.redhat.com/1565717
Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=15966242

Test: Booted brew build on supported (Haswell) and unsupported processor (CNL)
      and achieved desired results.

Upstream: RHEL Only

Cc: David Arcari <darcari@redhat.com>
Cc: Mikulas Patocka <mpatocka@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

update rh_check_supported processor list

Message-id: <1530618602-17477-1-git-send-email-darcari@redhat.com>
Patchwork-id: 223452
O-Subject: [RHEL8.0 BZ 1595918] x86: update rh_check_supported processor list
Bugzilla: 1595918
RH-Acked-by: Jarod Wilson <jarod@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>

Bugzilla: http://bugzilla.redhat.com/1595918
Upstream Status: RHEL_only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16916208
Tested: Verified on a varity of supported and unsupported Intel and AMD systems.
	Results as expected.

In RHEL8, we are marking some of the older processors as unsupported. No code
is being removed; however, the older processors are not supported and as such
are not candidates for certification.

Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Steve Best <sbest@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Signed-off-by: Jakub Racek <jracek@redhat.com>
refresh: rename FAM6_ATOM again, see f2c4db1bd

mark whiskey-lake processor supported

Message-id: <1533125629-12870-1-git-send-email-darcari@redhat.com>
Patchwork-id: 225809
O-Subject: [ BZ 1609604] mark whiskey-lake processor supported
Bugzilla: 1609604
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

Bugzilla: http://bugzilla.redhat.com/1609604
Build Info: https://brewweb.devel.redhat.com/taskinfo?taskID=17474338
Upstream Status: RHEL Only
Tested: Successful excecution of platform-test suite.

Whiskey Lake is cpu model 142 with stepping 11.  Stepping > 11 for cpu model
142 is not supported.

For model 158, the highest supported stepping is 10.

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

mark intel knights landing and knights mill unsupported

Message-id: <1533580277-126323-1-git-send-email-darcari@redhat.com>
Patchwork-id: 226187
O-Subject: [RHEL8.0 BZ 1610493] mark intel knights landing and knights mill unsupported
Bugzilla: 1610493
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>

Bugzilla: http://bugzilla.redhat.com/1610493
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17625348

Tested: verified on KNL/KNM system
Upstream Status: RHEL Only
Depends: http://bugzilla.redhat.com/1609604

We are marking KNL/KNM processors as unsupported. No code is being removed;
however, the older processors are not supported and as such are not
candidates for certification.

Upstream Status: RHEL only
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:35 -04:00
Jeremy Cline f4de4b173f arm: aarch64: Drop the EXPERT setting from ARM64_FORCE_52BIT
Message-id: <20191001181256.22935-1-jcline@redhat.com>
Patchwork-id: 275498
O-Subject: [ARK INTERNAL PATCH] [ARK INTERNAL PATCH] [redhat] Add patch
    to drop the EXPERT setting from ARM64_FORCE_52BIT
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

We don't turn on EXPERT as there are few settings we actually want to
mess with. Remove the dependency for ARM64_FORCE_52BIT as we do want
that on in debug builds to help find 52-bit bugs.

Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:35 -04:00
Laura Abbott 7b37a2f62e iommu/arm-smmu: workaround DMA mode issues
Message-id: <20190520222102.19488-1-labbott@redhat.com>
Patchwork-id: 259215
O-Subject: [ARK INTERNAL PATCH] iommu/arm-smmu: workaround DMA mode issues
Bugzilla:
RH-Acked-by: Mark Langsdorf <mlangsdo@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>

From: Mark Salter <msalter@redhat.com>

Rebased for v5.2-rc1

	Bugzilla: 1652259
	Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19244562
	Upstream status: RHEL only.

	rhel8 commit 65feb1ed0ec9a088a63a90d46c0f7563ac96ad0f
	Author: Mark Salter <msalter@redhat.com>
	Date:   Wed Nov 21 17:15:59 2018 +0100

	    [iommu] iommu/arm-smmu: workaround DMA mode issues

	    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1624077
	    Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=18112820
	    Testing: Verified iommu.passthrough=1 no longer needed on gigabyte platforms.
	    Upstream Status: RHEL-only

	    In RHEL_ALT 7.5 we carried a RHEL-only patch which forced the arm smmuv2
	    into bypass mode due to performance issues on CN88xx. This was intended
	    to be a temporary hack until the issues were resolved. Another vendor
	    had issues with the iommu in bypass mode so we reverted the RHEL-only
	    patch so that iommu is in DMA mode by default (upstream default).

	    It turns on that there are remaining SMMU DMA mode issues on Gigabyte
	    platformws with CN88xx cpus. The problem manifests itself by pcie
	    card drivers failing to initialize the cards when SMMU is in DMA mode.
	    The root cause has not been determined yet, but looks likely to be
	    a hw or firmware issue. This patch forces bypass mode for Gigabyte
	    platforms. CN88xx isn't officially supported in RHEL but we have a
	    lot of them being used internally for testing, so I think we want
	    this to support that use case in RHEL8.

	    Signed-off-by: Mark Salter <msalter@redhat.com>
	    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

	Acked-by: Mark Salter <msalter@redhat.com>
	Acked-by: Donald Dutile <ddutile@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 14:29:35 -04:00
Jakub Racek 51810484d6 rh_kabi: introduce RH_KABI_EXCLUDE
Message-id: <1542891606-8048-24-git-send-email-jracek@redhat.com>
Patchwork-id: 233503
O-Subject: [ARK PATCH 23/44] [kernel] rh_kabi: introduce RH_KABI_EXCLUDE
Bugzilla: 1652256
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

From: Jiri Benc <jbenc@redhat.com>

Bugzilla: 1652256
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19244562

rhel8 commit 1c588b1bbe6ea3e9e1701ccf10e22f73f687ad02
Author: Jiri Benc <jbenc@redhat.com>
Date:   Wed Nov 21 17:15:39 2018 +0100

    [kernel] rh_kabi: introduce RH_KABI_EXCLUDE

    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1568551

    Add a way to exclude certain fields of a structure that would be otherwise
    kABI whitelisted. The new RH_KABI_EXCLUDE macro serves two purposes:

    1. Not adding the excluded fields to symbol checksums, making their later
       changes easier.

    2. Document that the given fields are not considered to be kABI whitelisted
       by Red Hat.

    Note that:

    - This needs to be done _before_ the actual structure gets whitelisted.

    - It still allows later conversion of the excluded fields to whitelist
      covered fields by simply changing RH_KABI_EXCLUDE to RH_KABI_EXTEND.

    - The excluded fields can be modified at will but extra care needs to be
      taken to not cause problems with 3rd party drivers using the fields. See
      the comment inside the patch for details.

    Signed-off-by: Jiri Benc <jbenc@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Jakub Racek <jracek@redhat.com>
2021-08-30 14:29:35 -04:00
Laura Abbott 9e35c09b5d ipmi: do not configure ipmi for HPE m400
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1670017
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=20147017

Commit 913a89f009 ("ipmi: Don't initialize anything in the core until
something uses it") added new locking which broke context.

    Message-id: <20180713142210.15700-1-tcamuso@redhat.com>
    Patchwork-id: 224899
    O-Subject: [RHEL8 BZ 1583537 1/1] ipmi: do not configure ipmi for HPE m400
    Bugzilla: 1583537
    RH-Acked-by: Dean Nelson <dnelson@redhat.com>
    RH-Acked-by: Al Stone <ahs3@redhat.com>
    RH-Acked-by: Mark Salter <msalter@redhat.com>

    bugzilla:https://bugzilla.redhat.com/show_bug.cgi?id=1583537
    brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17150528

    RHEL-only

    The ARM-based HPE m400 reports host-side ipmi as residing in intel
    port-io space, which does not exist in ARM processors. Therefore, when
    running on an m400, host-side ipmi configuration code must simply return
    zero without trying to configure the host-side ipmi.

    This patch prevents panic on boot by averting attempts to configure
    host-side ipmi on this platform.

    Though HPE m400 is not certified with RHEL, and HPE has relegated it to
    EOL status, the platform is still used extensively in ARM development
    and test for RHEL.

    Testing:
    Boot without blacklisting ipmi and check to see that no ipmi modules
    are loaded.

    Signed-off-by: Tony Camuso <tcamuso@redhat.com>

    cc: Prarit Bhargava <prarit@redhat.com>
    cc: Brendan Conoboy <blc@redhat.com>
    cc: Jeff Bastian <jbastian@redhat.com>
    cc: Scott Herold <sherold@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
Acked-by: Tony Camuso <tcamuso@redhat.com>
Acked-by: Dean Nelson <dnelson@redhat.com>
Acked-by: Jarod Wilson <jarod@redhat.com>
Acked-by: Mark Salter <msalter@redhat.com>
2021-08-30 14:29:35 -04:00
Myron Stowe bbe1f3e99d kABI: Add generic kABI macros to use for kABI workarounds
Message-id: <20180629200436.151355.18581.stgit@tak.stowe>
Patchwork-id: 223206
O-Subject: [RHEL8.0 PATCH v3] kABI: Add generic kABI macros to use for kABI workarounds
Bugzilla: 1546831
RH-Acked-by: Larry Woodman <lwoodman@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Some kernel subsystem maintainers have asked about kABI for RHEL8.0
- getting kABI related "extension" structures and such into place.  The
consensus was to wait until the 4.17 re-base.  Now that that's occurred,
lets get this first step, kABI macros, into RHEL8.0 so developers will
notice, and use, them in subsequent kABI related efforts.

Content taken from RHEL 7.  No functional change intended.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1546831
Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=16694565
Upstream Status: N/A (RHEL only)
Testing: Passed through brew build.

Upstream Status: RHEL only
Signed-off-by: Myron Stowe <myron.stowe@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:35 -04:00
Maurizio Lombardi 51b35f4357 add pci_hw_vendor_status()
Message-id: <1529326285-28560-1-git-send-email-mlombard@redhat.com>
Patchwork-id: 222337
O-Subject: [RHEL8 PATCH] pci: add pci_hw_vendor_status()
Bugzilla: 1590829
RH-Acked-by: Tomas Henzl <thenzl@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

This patch adds pci_hw_vendor_status() like in RHEL7 which should be called
during the driver's probe to identify deprecated devices.

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1590829
Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=16761315

See RHEL7 commits e0dddd9a63403ec82077ed410074fc6485873d4b and
3fcddde5ddf4b190c84ce9d83d56a75137513bd7

RHEL_only.

Upstream Status: RHEL only
Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:35 -04:00
Robert Richter 4bfbf90b26 ahci: thunderx2: Fix for errata that affects stop engine
Message-id: <1528412373-19128-3-git-send-email-rrichter@redhat.com>
Patchwork-id: 220952
O-Subject: [RHEL-8.0 BZ 1563590 v2 2/2] ahci: thunderx2: Fix for errata that affects stop engine
Bugzilla: 1563590
RH-Acked-by: Dean Nelson <dnelson@redhat.com>
RH-Acked-by: Mark Langsdorf <mlangsdo@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>

From: Jayachandran C <jnair@caviumnetworks.com>

Apply workaround for this errata:
  Synopsis: Resetting PxCMD.ST may hang the SATA device

  Description: An internal ping-pong buffer state is not reset
  correctly for an PxCMD.ST=0 command for a SATA channel. This
  may cause the SATA interface to hang when a PxCMD.ST=0 command
  is received.

  Workaround: A SATA_BIU_CORE_ENABLE.sw_init_bsi must be asserted
  by the driver whenever the PxCMD.ST needs to be de-asserted. This
  will reset both the ports. So, it may not always work in a 2
  channel SATA system.

  Resolution: Fix in B0.

Add the code to ahci_stop_engine() to do this. It is not easy to
stop the other "port" since it is associated with a different AHCI
interface. Please note that with this fix, SATA reset does not
hang any more, but it can cause failures on the other interface
if that is in active use.

Unfortunately, we have nothing other the the CPU ID to check if the
SATA block has this issue.

RHEL-only:

Both patches are in RHEL-7.6 also. Inclusion of the patches into RHEL-8
was discussed. Since there are partners with Ax system configurations it
was decided to carry them in RHEL8 too. See:

 https://bugzilla.redhat.com/show_bug.cgi?id=1563590#c1

[v3 with new delays]
Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>

Upstream Status: RHEL only
Signed-off-by: Robert Richter <rrichter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:35 -04:00
Robert Richter 4e05d8a20f Vulcan: AHCI PCI bar fix for Broadcom Vulcan early silicon
Message-id: <1528412373-19128-2-git-send-email-rrichter@redhat.com>
Patchwork-id: 220950
O-Subject: [RHEL-8.0 BZ 1563590 v2 1/2] PCI: Vulcan: AHCI PCI bar fix for Broadcom Vulcan early silicon
Bugzilla: 1563590
RH-Acked-by: Dean Nelson <dnelson@redhat.com>
RH-Acked-by: Mark Langsdorf <mlangsdo@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>

From: Ashok Kumar Sekar <asekar@redhat.com>

PCI BAR 5 is not setup correctly for the on-board AHCI
controller on Broadcom's Vulcan processor. Added a quirk to fix BAR 5
by using BAR 4's resources which are populated correctly but NOT used
by the AHCI controller actually.

RHEL-only:

Both patches are in RHEL-7.6 also. Inclusion of the patches into RHEL-8
was discussed. Since there are partners with Ax system configurations it
was decided to carry them in RHEL8 too. See:

 https://bugzilla.redhat.com/show_bug.cgi?id=1563590#c1

Upstream Status: RHEL only
Signed-off-by: Ashok Kumar Sekar <asekar@redhat.com>
Signed-off-by: Jayachandran C <jchandra@broadcom.com>
Signed-off-by: Robert Richter <rrichter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:35 -04:00
Eugene Syromiatnikov 9ce398ab77 bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter
Message-id: <133022c6c389ca16060bd20ef69199de0800200b.1528991396.git.esyr@redhat.com>
Patchwork-id: 8250
O-Subject: [kernel team] [RHEL8 PATCH v4 2/5] [bpf] bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter
Bugzilla: 1561171
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>

This patch sets kernel.unprivileged_bpf_disabled sysctl knob to 1
by default, and provides an ability (in a form of a boot-time parameter)
to reset it to 0, as it is impossible to do so in runtime.  Since
unprivileged BPF is considered unsupported, it also taints the kernel.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1561171
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16716594
Upstream: RHEL only.  The patch (in a more generic form) has been
          proposed upstream[1] and subsequently rejected.

[1] https://lkml.org/lkml/2018/5/21/344

Upstream Status: RHEL only
Signed-off-by: Eugene Syromiatnikov <esyr@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:35 -04:00
Eugene Syromiatnikov d3c11e8d59 add Red Hat-specific taint flags
Message-id: <56f71e5f8cf63afd0cdb1c4550c625cc90d59a75.1528991395.git.esyr@redhat.com>
Patchwork-id: 8249
O-Subject: [kernel team] [RHEL8 PATCH v4 1/5] kernel: add Red Hat-specific taint flags
Bugzilla: 1559877
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>

Based on RHEL 7 commit "Backport RH specific TAINT flags" by Prarit
Bhargava.

Upstream Status: RHEL only
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1559877
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16716594
Signed-off-by: Eugene Syromiatnikov <esyr@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 14:29:34 -04:00
Jeremy Cline abae7ce67e tags.sh: Ignore redhat/rpm
Rebased for v5.3-rc1. Commit 95fd3f87bf ("kbuild: add a flag to force
absolute path for srctree") changed the context.

    Message-id: <20180529180112.28376-1-prarit@redhat.com>
    Patchwork-id: 8101
    O-Subject: [kernel team] [RHEL8.0 BZ 1582586] scripts/tags.sh: Ignore redhat/rpm
    Bugzilla: 1582586
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>
    RH-Acked-by: Neil Horman <nhorman@redhat.com>

    Bugzilla: http://bugzilla.redhat.com/1582586
    Brew: https://brewweb.devel.redhat.com/taskinfo?taskID=16502319

    RHEL_only.

    If 'make cscope' is run on a tree which has had 'make rh-rpm',
    'make rh-cross-*', etc., on it, the tags information contains entries
    from the redhat/rpm/ directories.

    Ignore the tags search in redhat/rpm.

    Backport of RHEL7 464ad7779507 ("[scripts] tags.sh: ignore redhat/rpm").

    Signed-off-by: Prarit Bhargava <prarit@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 14:29:34 -04:00
Laura Abbott d603bdb771 put RHEL info into generated headers
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1663728

Commit 43fee2b238 ("kbuild: do not redirect the first prerequisite for
filechk") upstream introduced some context diff. This just fixes that up.

    Bugzilla: http://bugzilla.redhat.com/1544999

    kernel-alt commit b3bbf3db12b8a48491eb4175eae25eb907f092ac
    Author: Prarit Bhargava <prarit@redhat.com>
    Date:   Fri Feb 9 18:09:25 2018 -0500

        [kernel] put RHEL info into generated headers

         Message-id: <20180209180926.5955-2-prarit@redhat.com>
         Patchwork-id: 205585
         O-Subject: [RHEL-ALT-7.5 BZ 1542796 1/2] put RHEL info into generated headers
        Bugzilla: 1542796
        RH-Acked-by: David Arcari <darcari@redhat.com>
        RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
        RH-Acked-by: Steve Best <sbest@redhat.com>

        Bugzilla: http://bugzilla.redhat.com/1542796

        rhel7 commit 6199c642a685fba61a298901190659dbedb7c3c3
        Author: Jarod Wilson <jarod@redhat.com>
        Date:   Thu Oct 10 20:14:33 2013 -0400

             [redhat] put RHEL info into generated headers

             Message-id: <1381436073-8850-1-git-send-email-jarod@redhat.com>
             Patchwork-id: 69475
             O-Subject: [RHEL7 PATCH] [redhat] put RHEL info into generated headers
            Bugzilla:
            RH-Acked-by: Neil Horman <nhorman@redhat.com>
            RH-Acked-by: Rafael Aquini <aquini@redhat.com>
            RH-Acked-by: Kyle McMartin <kmcmarti@redhat.com>

            While glancing at the differences between RHEL6 and RHEL7's modifications to the
            top-level Makefile, some discrepancies popped up... This brings RHEL7 in line
            with all of the customizations we make in RHEL6 to get distro info propagated.

            Signed-off-by: Jarod Wilson <jarod@redhat.com>

        Cc: Herton R. Krzesinski <herton@redhat.com>
        Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Acked-by: Don Zickus <dzickus@redhat.com>
Acked-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 14:29:34 -04:00
Mark Salter 7e4dc6ad7b acpi: prefer booting with ACPI over DTS
Message-id: <20180511210117.10457-1-msalter@redhat.com>
Patchwork-id: 214708
O-Subject: [RHEL-8 BZ1576869] [RHEL only] acpi: prefer booting with ACPI over DTS
Bugzilla: 1576869
RH-Acked-by: Jonathan Toppins <jtoppins@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: Bhupesh Sharma <bhsharma@redhat.com>
RH-Acked-by: Dean Nelson <dnelson@redhat.com>

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1576869
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16208479
Testing: Verified kernel defaults to ACPI on Mustang

From: Jonathan Toppins <jtoppins@redhat.com>

    This patch forces ACPI boot tables to be preferred over DTS.

    Currently for ACPI to be used a user either has to set acpi=on on the
    kernel command line or make sure any device tree passed to the kernel
    is empty. If the dtb passed to the kernel is non-empty then device-tree
    will be chosen as the boot method of choice.

    RHEL does not wish to support this boot method so change table boot
    preferences to use ACPI. In the event ACPI table checks fail the kernel
    will fallback to using DTS to boot.

    Signed-off-by: Jonathan Toppins <jtoppins@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 10:50:56 -04:00
Mark Salter e31b8137cb aarch64: acpi scan: Fix regression related to X-Gene UARTs
Message-id: <20180510173844.29580-4-msalter@redhat.com>
Patchwork-id: 214381
O-Subject: [RHEL-8 BZ1519554 3/3] aarch64: acpi scan: Fix regression related to X-Gene UARTs
Bugzilla: 1519554
RH-Acked-by: Al Stone <astone@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1519554
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16144520

Commit e361d1f858 ("ACPI / scan: Fix enumeration for special UART
devices") caused a regression with some X-Gene based platforms (Mustang
and M400) with invalid DSDT. The DSDT makes it appear that the UART
device is also a slave device attached to itself. With the above commit
the UART won't be enumerated by ACPI scan (slave serial devices shouldn't
be). So check for X-Gene UART device and skip slace device check on it.

Upstream Status: RHEL only
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 10:50:56 -04:00
Mark Salter 7e0a2ca8b0 ACPI / irq: Workaround firmware issue on X-Gene based m400
Message-id: <20180510173844.29580-3-msalter@redhat.com>
Patchwork-id: 214383
O-Subject: [RHEL-8 BZ1519554 2/3] ACPI / irq: Workaround firmware issue on X-Gene based m400
Bugzilla: 1519554
RH-Acked-by: Al Stone <astone@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1519554
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16144520

The ACPI firmware on the xgene-based m400 platorms erroneously
describes its UART interrupt as ACPI_PRODUCER rather than
ACPI_CONSUMER. This leads to the UART driver being unable to
find its interrupt and the kernel unable find a console.
Work around this by avoiding the producer/consumer check
for X-Gene UARTs.

Upstream Status: RHEL only
Signed-off-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 10:50:56 -04:00
Laura Abbott d2857e6759 modules: add rhelversion MODULE_INFO tag
There were several changes in the 5.0-rc1 kernel that required
this patch to be rebased with some context diff.

    Patchwork-id: 7379
    O-Subject: [kernel team] [RHEL8.0 BZ 1544999 1/2] modules: add rhelversion MODULE_INFO tag
    Bugzilla: 1544999
    RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
    RH-Acked-by: Oleg Nesterov <oleg@redhat.com>
    RH-Acked-by: Jarod Wilson <jarod@redhat.com>

    Bugzilla: http://bugzilla.redhat.com/1544999

    kernel-alt commit 9816b4b6ca5d4c0504d8806ce99442c90afbc8e6
    Author: Prarit Bhargava <prarit@redhat.com>
    Date:   Fri Feb 9 18:09:26 2018 -0500

        [kernel] modules: add rhelversion MODULE_INFO tag

        Message-id: <20180209180926.5955-3-prarit@redhat.com>
        Patchwork-id: 205587
        O-Subject: [RHEL-ALT-7.5 BZ 1542796 2/2] modules: add rhelversion MODULE_INFO tag
        Bugzilla: 1542796
        RH-Acked-by: David Arcari <darcari@redhat.com>
        RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
        RH-Acked-by: Steve Best <sbest@redhat.com>

        Bugzilla: http://bugzilla.redhat.com/1542796

        rhel7 commit 9af8c3992ce5fff253c49abc0dedb3ec77badba4
        Author: Kyle McMartin <kmcmarti@redhat.com>
        Date:   Fri Sep 12 17:46:12 2014 -0400

            [kernel] modules: add rhelversion MODULE_INFO tag

            Message-id: <20140912174612.GS29420@redacted.bos.redhat.com>
            Patchwork-id: 94052
            O-Subject: [RHEL7.1 PATCH 2/6 v4] modules: add rhelversion MODULE_INFO tag
            Bugzilla: 1110315
            RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
            RH-Acked-by: Johannes Weiner <jweiner@redhat.com>
            RH-Acked-by: Don Zickus <dzickus@redhat.com>

            From: Kyle McMartin <kmcmarti@redhat.com>

            Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1110315

            >From kylem's RHEL8 post:

            Let's not lose this ability in RHEL8. Sadly can't be applied to RHEL7
            because it breaks KABI due to the struct module change.

            Inspired by bits of a147e4729d9920ccae2c717ca65c811cc0f93a1d in RHEL6,
            which got lost for RHEL7.0. :/

            Kyle is correct and doing this would break RHEL7's KABI.  I'm taking this
            patch in as a base and the next patch will resolve the KABI issues.

            [v2]: dzickus, cleanup add_rhelversion()
            [v4]: resubmitted along with 16k stacks change

            Signed-off-by: Jarod Wilson <jarod@redhat.com>

        Cc: Richard Guy Briggs <rgb@redhat.com>
        Cc: Peter Rajnoha <prajnoha@redhat.com>
        Cc: Laura Abbott <labbott@redhat.com>
        Cc: Josh Poimboeuf <jpoimboe@redhat.com>
        Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Acked-by: Don Zickus <dzickus@redhat.com>
Acked-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:55 -04:00
Al Stone 1fbf4313b1 ACPI: APEI: arm64: Ignore broken HPE moonshot APEI support
Message-id: <20180227002123.21608-1-ahs3@redhat.com>
Patchwork-id: 206052
O-Subject: [RHEL8 BZ1518076 PATCH] ACPI: APEI: arm64: Ignore broken HPE moonshot APEI support
Bugzilla: 1518076
RH-Acked-by: Mark Salter <msalter@redhat.com>
RH-Acked-by: Jeremy McNicoll <jmcnicol@redhat.com>

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1518076
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15417197
Tested: compile-only; several other patches are required for full booting
        QE has tested limited boot (see comment#12 of BZ)

This is a re-post of a RHEL-ALT-7.5 patch specific to aarch64 moonshots
that we use in beaker.  It is required for these machines to boot.

    commit 8a663a264863efedf8bb4a9d76ac603920fdd739
    Author: Robert Richter <rrichter@redhat.com>
    Date:   Wed Aug 16 19:49:30 2017 -0400

    [acpi] APEI: arm64: Ignore broken HPE moonshot APEI support

    From: Mark Salter <msalter@redhat.com>
    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1344237
    Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13768971
    Tested: Booted on moonshot with patched 4.11.0-20 kernel
    Upstream: RHEL-only

    The aarch64 HP moonshot platforms we have in beaker and elsewhere have
    a firmware bug which causes a spurious fatal memory error via APEI at
    boot time. This platform is no longer supported and no further firmware
    updates are expected. This is a downstream-only hack to avoid the problem
    by bailing out of HEST table probing if we detect a moonshot HEST table.

    Signed-off-by: Mark Salter <msalter@redhat.com>
    Signed-off-by: Robert Richter <rrichter@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

Upstream Status: RHEL only
Signed-off-by: Al Stone <ahs3@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 10:50:55 -04:00
Laura Abbott 54b6d49a09 Add Red Hat tainting
Message-id: <20191113144431.9403-5-labbott@redhat.com>
Patchwork-id: 286078
O-Subject: [ARK INTERNAL PATCHv2 4/4] [redhat] Add Red Hat tainting
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

This is a combination of the following commits including support
for adding CONFIG_RH_DEPRECATED support

rh_taint: add support

Message-id: <1524831536-47239-1-git-send-email-darcari@redhat.com>
Patchwork-id: 211655
O-Subject: [RHEL8.0 BZ 1565704 v2] rh_taint: add support
Bugzilla: 1565704
RH-Acked-by: Jonathan Toppins <jtoppins@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

Bugzilla: http://bugzilla.redhat.com/1565704
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15910441
Upstream: RHEL Only
Test: Sanity boot of brew build.  Previous private build testing of functions.

rh_taint.c adds the following functions which are utilized by Red Hat to
indicate limited or no support for hardware and/or drivers.

mark_hardware_unsupported
mark_hardware_deprecated
mark_tech_preview

See code comments for usage.

RHEL8 change: TAINT_AUX will be used in place of TAINT_TECH_PREVIEW as it
limits the number RHEL only changes that must be made to the kernel.

If at a later date it is determined that additional flags are required,
the associated RHEL only infrastructure can be added at that time.

Cc: David Arcari <darcari@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

rh_taint: add support for marking driver as unsupported

Message-id: <f42d35b07bd02f34b14a6341a219c80b21a8aff9.1524523802.git.jtoppins@redhat.com>
Patchwork-id: 211020
O-Subject: [RHEL8.0] rh_taint: add support for marking driver as unsupported
Bugzilla: 1565704
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>

In some cases a driver needs to be enabled by Red Hat to support internal
testing but the driver is not intended to be supported on customer hardware.
This adds a function "make_driver_unsupported()" to facilitate such
situations. The function will print a kernel log message.

Bugzilla: 1565704
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=15873552
Tested: compile only

Signed-off-by: Jonathan Toppins <jtoppins@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

rh_taint: correct loaddable module support dependencies

Message-id: <20181123111337.26898-5-prudo@redhat.com>
Patchwork-id: 233658
O-Subject: [ARK PATCH RESEND v2 4/8] [kernel] rh_taint: correct loaddable module support dependencies
Bugzilla: 1652266
RH-Acked-by: Jakub Racek <jracek@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Cornelia Huck <cohuck@redhat.com>

Bugzilla: 1652266
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19252944
Upstream Status: RHEL_only

The kernel configuration for the s390/zfcpdump kernel variant turns
loaddable module support off.  The build breaks in rh_taint.c due to
compiler errors caused by dereferencing struct module variables which
is just a declaration if CONFIG_MODULES is not set.

To solve this build break, access struct module members only if
CONFIG_MODULES is enabled.

Upstream Status: RHEL only
Signed-off-by: Philipp Rudo <prudo@redhat.com>
2021-08-30 10:50:55 -04:00
Laura Abbott f36d30523d Introduce CONFIG_RH_DISABLE_DEPRECATED
Message-id: <20191113144431.9403-2-labbott@redhat.com>
Patchwork-id: 286080
O-Subject: [ARK INTERNAL PATCHv2 1/4] [redhat] Introduce CONFIG_RH_DISABLE_DEPRECATED
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

For many drivers that RHEL doesn't want to support, we've typically deleted
PCI ids from the tree. This precludes those drivers from being used at all
which is fine for RHEL but a problem if we want to use a similar source base
for Fedora. Instead of just deleting IDs, introduce a config
CONFIG_RH_DISABLE_DEPRECATED. This way RHEL can remove IDs while still allowing
kernels to be built with the option off from the same source.

Upstream Status: RHEL only
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:50:55 -04:00
Don Zickus 3b480ba373 Stop merging ark-patches for release
With the new single workflow, ark-patches is rolled into the os-build
branch.  There is no more need to merge the external branch.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:55 -04:00
Don Zickus 225d55218d Fix path location for ark-update-configs.sh
The ark-update-configs.sh script is written to be executed from the top of the
git tree.  However, from a make -C redhat/ command it is executed from the
redhat/ path.  This breaks the script when it needs to generate new configs
(redhat/gen_config_patches.sh).

A simple fix is to execute the script inside the redhat/Makefile from the top
level.  The alternative is to teach the script to be location agnostic, but
there is a handful of hardcoded places across 2 scripts that I thought it
wasn't worth it.

Tested by running the 'scheduled' merge-upstream job using my test-os-build
branch where it passed
(https://gitlab.com/cki-project/kernel-ark/-/pipelines/199415525)

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:55 -04:00
Don Zickus b38444c686 Combine Red Hat patches into single patch
This in spirit reverts 0409b21839
and converts the broken out Red Hat patches back into a single diff.

The original idea was to make it easy for the Fedora community to see
what changes Red Hat was making on top of upstream's tarball.  The
concept was good, the reality with a source git tree had a flaw.

While 'git merging' with upstream, various conflicts were resolved
through git or the merge.  However, when broken out into individual
patches and placed on top of a tarball, this becomes a rebase.

The conflicts could not be resolved with later patches as the initial
patch was a problem.  The only solution was to periodically rebase
the source git tree which dampens the spirit of the idea of source-git.

This patch takes another apporach to solve the original problem:
- create a diff from upstream as a single patch
- create a Patchlist.changelog file to list the individual patches
  and their shas1 as seen in the source git tree.

This is what was there original and hence the partial revert (though
that patch went through many changes since then).

It isn't perfect, but we are still evolving.  This should resolve the
CKI build failures they continuously run into.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:54 -04:00
Jeremy Cline c63c99fe6b New configs in drivers/misc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_UACCE:

 UACCE provides interface for the user process to access the hardware
 without interaction with the kernel space in data path.

 The user-space interface is described in
 include/uapi/misc/uacce/uacce.h

 See Documentation/misc-devices/uacce.rst for more details.

 If you don't know what to do here, say N.

 Symbol: UACCE [=n]
 Type  : tristate
 Defined at drivers/misc/uacce/Kconfig:1
   Prompt: Accelerator Framework for User Land
   Depends on: IOMMU_API [=y]
   Location:
     -> Device Drivers
       -> Misc devices

Cc: John Linville <linville@redhat.com>
2021-08-30 10:50:54 -04:00
Justin M. Forbes d387e70777 New configs in drivers/net/wireless
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MT7663U:

 This adds support for MT7663U 802.11ax 2x2:2 wireless devices.

 To compile this driver as a module, choose M here.

 Symbol: MT7663U [=n]
 Type  : tristate
 Defined at drivers/net/wireless/mediatek/mt76/mt7615/Kconfig:31
   Prompt: MediaTek MT7663U (USB) support
   Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && USB [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless LAN (WLAN [=y])
           -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
 Selects: MT76_USB [=m] && MT7615_COMMON [=n]

Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
2021-08-30 10:50:54 -04:00
Fedora Kernel Team a652a5f424 New configs in drivers/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PHY_QCOM_IPQ806X_USB:

 This option enables support for the Synopsis PHYs present inside the
 Qualcomm USB3.0 DWC3 controller on ipq806x SoC. This driver supports
 both HS and SS PHY controllers.

 Symbol: PHY_QCOM_IPQ806X_USB [=n]
 Type  : tristate
 Defined at drivers/phy/qualcomm/Kconfig:108
   Prompt: Qualcomm IPQ806x DWC3 USB PHY driver
   Depends on: HAS_IOMEM [=y] && OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=y]

Cc: John Linville <linville@redhat.com>
2021-08-30 10:50:54 -04:00
Fedora Kernel Team 59058e3e13 New configs in drivers/tty
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SERIAL_LANTIQ:

 Support for UART on Lantiq and Intel SoCs.
 To compile this driver as a module, select M here. The
 module will be called lantiq.

 Symbol: SERIAL_LANTIQ [=n]
 Type  : tristate
 Defined at drivers/tty/serial/Kconfig:1036
   Prompt: Lantiq serial driver
   Depends on: TTY [=y] && HAS_IOMEM [=y] && (LANTIQ || X86 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Character devices
         -> Enable TTY (TTY [=y])
           -> Serial drivers
 Selects: SERIAL_CORE [=y]

Cc: John Linville <linville@redhat.com>
2021-08-30 10:50:54 -04:00
Bohdan Khomutskyi c008de8ffd Set SquashFS decompression options for all flavors to match RHEL
I discovered that several kernel configuration options related to SquashFS decompression are set sub-optimally in Fedora. But the optimal configuration is used in RHEL 8.
If we set those options to match RHEL, a performance improvement could be achieved while reading from compressed SquashFS filesystem.

Please see my original message in Fedora kernel mailing list archive:
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org/thread/4M6WYFOZAZYIEVNZTBVM2BTT7SIEZBNQ/
There you can find an excerpt from Linux documentation for the changed options.

I found the disparity while working on Fedora change proposal:
https://fedoraproject.org/wiki/Changes/OptimizeSquashFS

Signed-off-by: Bohdan Khomutskyi <bkhomuts@redhat.com>
2021-08-30 10:50:53 -04:00
Phil Auld 4e43c43a58 configs: Enable CONFIG_ENERGY_MODEL
CONFIG_ENERGY_MODEL will help make the schedutil frequency governor
more accurate. This will be useful in the future. It also enables
the use of the energy aware scheduler.

Signed-off-by: Phil Auld <pauld@redhat.com>
2021-08-30 10:50:53 -04:00
Fedora Kernel Team a8a5fa4a86 [redhat] New configs in drivers/infiniband
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INFINIBAND_RTRS_CLIENT:

 RDMA transport client module.

 RDMA Transport (RTRS) client implements a reliable transport layer
 and also multipathing functionality and that it is intended to be
 the base layer for a block storage initiator over RDMA.

 Symbol: INFINIBAND_RTRS_CLIENT [=n]
 Type  : tristate
 Defined at drivers/infiniband/ulp/rtrs/Kconfig:7
   Prompt: RTRS client module
   Depends on: INFINIBAND [=m] && INFINIBAND_ADDR_TRANS [=y]
   Location:
     -> Device Drivers
       -> InfiniBand support (INFINIBAND [=m])
 Selects: INFINIBAND_RTRS [=n]

---

 CONFIG_INFINIBAND_RTRS_SERVER:

 RDMA transport server module.

 RDMA Transport (RTRS) server module processing connection and IO
 requests received from the RTRS client module, it will pass the
 IO requests to its user eg. RNBD_server.

 Symbol: INFINIBAND_RTRS_SERVER [=n]
 Type  : tristate
 Defined at drivers/infiniband/ulp/rtrs/Kconfig:18
   Prompt: RTRS server module
   Depends on: INFINIBAND [=m] && INFINIBAND_ADDR_TRANS [=y]
   Location:
     -> Device Drivers
       -> InfiniBand support (INFINIBAND [=m])
 Selects: INFINIBAND_RTRS [=n]

---

Cc: Kamal Heib <kheib@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:53 -04:00
Fedora Kernel Team 9c2899843f New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_JASPERLAKE:

 This pinctrl driver provides an interface that allows configuring
 of Intel Jasper Lake PCH pins and using them as GPIOs.

 Symbol: PINCTRL_JASPERLAKE [=n]
 Type  : tristate
 Defined at drivers/pinctrl/intel/Kconfig:114
   Prompt: Intel Jasper Lake PCH pinctrl and GPIO driver
   Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_INTEL [=m]

v2: enable for JASPERLAKE on x86

Cc: David Arcari <darcari@redhat.com>
2021-08-30 10:50:53 -04:00
Justin Forbes fed442909c Update CONFIG_THERMAL_NETLINK
Cc: David Arcari <darcari@redhat.com>
2021-08-30 10:50:53 -04:00
Fedora Kernel Team 9cd676051f [redhat] New configs in drivers/thermal
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_THERMAL_NETLINK:

 The thermal framework has a netlink interface to do thermal
 zones discovery, temperature readings and events such as
 trip point crossed, cooling device update or governor
 change. It is recommended to enable the feature.

 Symbol: THERMAL_NETLINK [=n]
 Type  : bool
 Defined at drivers/thermal/Kconfig:20
   Prompt: Thermal netlink management
   Depends on: THERMAL [=y] && NET [=y]
   Location:
     -> Device Drivers
       -> Thermal drivers (THERMAL [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:53 -04:00
Don Zickus 2c7ce220ea Separate merge-upstream and release stages
Now that the merge-upstream stage is separated and working, let's
remove it from the release stage.  These scripts are already excuted by the
'merge-upstream' stage.  This changes just removes the duplication. Trivial
change.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:52 -04:00
Prarit Bhargava cd9a29553e RHMAINTAINERS: Reassign FIREWIRE
Reassign FIREWIRE to Jarod.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: jarod@redhat.com
2021-08-30 10:50:52 -04:00
Prarit Bhargava b0086f7631 RHMAINTAINERS: update for unassigned kernel areas
These areas are unassigned in the kernel

- lib/
- drivers/phy
- init/
- drivers/input
- drivers/clk
- drivers/tty
- drivers/misc
- drivers/soc
- mm/

Also fix an out-of-order entry (MMC).

v2: Remove darcari from SYSTEM ON CHIP (darcari)
v3: Helps to actually send the right version of the patch.

RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Tony Camuso <tcamuso@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: prarit@redhat.com
Cc: linville@redhat.com
Cc: darcari@redhat.com
Cc: tcamuso@redhat.com
Cc: msalter@redhat.com
Cc: aquini@redhat.com
2021-08-30 10:50:52 -04:00
Prarit Bhargava 4f8d646687 Re-enable CONFIG_IR_SERIAL on Fedora
The serial IR driver is needed for Fedora media-centers.

Re-enable the serial IR module for Fedora.

Suggested-by: Craig Gelowitz <craig@gelowitz.org>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: jbastian@redhat.com
2021-08-30 10:50:52 -04:00
Don Zickus f6043503e1 Create Patchlist.changelog file
A source git tree's workflow and Fedora's separation of upstream and distro
contributions don't overlap well.

A source git tree is always merging upstream content and downstream content
while avoiding a rebase.  By separating the tarballs and patches out, this
effectively causes a rebase.  This 'rebase' causes patches to not apply
correctly as git took care of it previously.

This patch creates a Patchlist.changelog file that lists all the SHAs that
are added to the upstream tree.

The goal is to create a useful file such that the source git tree can
create a single tarball and use the Patchlist.changelog file to adhere
to the spirit of the Fedora's separation rules.

No technical changes, just a new file added to the srpm.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:52 -04:00
Don Zickus 0ddb277f06 Filter out upstream commits from changelog
I updated the release code to include more changelog info
in the os-build branch.  This resulted in adding upstream
merge commits.  This is not interesting for a Fedora tree
as it is covered by a generic 'merge' entry.

Use a simple git trick to filter those upstream commits out, "^master".
See 'man gitrevisions' for more tricks.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:52 -04:00
Don Zickus 56659676ad Merge Upstream script fixes
As part of splitting the merge-upstream and release stages apart,
the merge upstream wasn't working quite right.  These are cleanup
fixes to fix that.

The main change is to drop the ark rebase patches script.  Running
that through a Makefile through gitlab CI creates a funky environment
where the next script (update-configs.sh) no longer exists because
of the git checkout changes.  Keep rebase-patches in the gitlab-ci
script for now.

That will be removed soon enough.  No effect on normal workflow.

The other fixes are self-explanatory.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:51 -04:00
Prarit Bhargava d8ec8c2b3e kernel.spec: Remove kernel-keys directory on rpm erase
An empty /usr/share/doc/kernel-keys/VR directory is left after executing
an 'rpm -e kernel-core-VR'.

Remove the directory when the rpm is erased.

v2: Only list directory and simplify code (bmeneg)

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
2021-08-30 10:50:51 -04:00
Justin M. Forbes 9c3fcb773f Add mlx5_vdpa to module filter for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:51 -04:00
Justin M. Forbes f4d2a002d4 Add python3-sphinx_rtd_theme buildreq for docs
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:51 -04:00
Prarit Bhargava 642e6eaf6b redhat/configs/process_configs.sh: Remove *.config.orig files
The process_configs.sh created temporary *.config.orig files for each
config variant which were not being properly cleaned up.

Remove *.config.orig files.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
Cc: mleitner@redhat.com
Cc: jbenc@redhat.com
2021-08-30 10:50:51 -04:00
Prarit Bhargava 4a01f8f8f4 redhat/configs/process_configs.sh: Add process_configs_known_broken flag
The 'process_configs.sh -n -w -c' command on the fedora configs terminates with

Processing /home/prarit/git-kernel/kernel-ark/redhat/configs/kernel-5.8.0-aarch64-debug.config ... Error: Mismatches found in configuration files
Found CONFIG_FORCE_MAX_ZONEORDER=11 after generation, had CONFIG_FORCE_MAX_ZONEORDER=13 in Source tree
make: *** [Makefile:149: fedora-configs] Error 1

The fedora aarch64 CONFIG entry for CONFIG_FORCE_MAX_ZONEORDER notes that
the warning can only be fixed through an out-of-tree patch.   Unfortunately
this means that the process_configs checkoptions check cannot be run on
fedora aarch64 configs.

To work around this problem, add a special tag
"process_configs_known_broken" which can be added as a comment to a known
broken CONFIG file.  Adding the tag will result in process_configs
checkoptions skipping the CONFIG's error.

Add the process_configs_known_broken flag to process_config.sh and fix
'make fedora-configs' by adding process_configs_known_broken to
CONFIG_FORCE_MAX_ZONEORDER.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
Cc: mleitner@redhat.com
Cc: jbenc@redhat.com
2021-08-30 10:50:50 -04:00
Prarit Bhargava 04bd60bd6b redhat/Makefile: Fix '*-configs' targets
The 'dist-configs' is not working properly as it only creates ELN
configs.  The 'rh-configs' and 'fedora-configs' targets are not
working properly and should be creating ELN and Fedora configs but they
only create some temporary/intermediate build files.  These targets
should output final .config files for each supported arch.

There are several fixes necessary to get the *-configs targets working
properly:

- Fix dist-configs to use a specified flavor instead of only ELN.  By
default, dist-configs will build ELN configs.
- Add a flavor parameter to build_config.sh.  By default build_config.sh
will use still the configs/flavors file, o/w build_config will only build
the flavor specified.
- Silence a warning in generate_all_configs.sh

Fix the '*-configs' targets to output final .config files for each
supported flavor arch.

Cleanup: Remove unused DIST_TARGET and TARGET variables.

v2: Fix 'make dist-configs' by removing the default setting of FLAVOR (jforbes)
v3: Fix process_configs.sh

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Reported-by: mleitner@redhat.com
Cc: dzickus@redhat.com
Cc: jforbes@redhat.com
Cc: mleitner@redhat.com
Cc: jbenc@redhat.com
2021-08-30 10:50:50 -04:00
Waiman Long 68f33a0c1b RHMAINTAINERS: Add futex subsystem
As I am also tracking upstream changes in futex code, I may as well add
the futex subsystem entry.

RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jarod Wilson <jarod@redhat.com>

Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:50 -04:00
Don Zickus fcdc277f70 dist-merge-upstream: Checkout known branch for ci scripts
Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:50 -04:00
Prarit Bhargava e184b3660a RHMAINTAINERS: General update
These areas are unassigned:

- drivers/video
- drivers/dma
- arch/powerpc
- drivers/dma-buf
- kernel/trace
- drivers/vdpa
- drivers/crypto

Update RHMAINTAINERS for these entries.

v2: fix kernel-patches entry
v3: Rebase to latest (prarit), remove NVM entry (dmilburn)
    Add DMA BUFFER SHARING FRAMEWORK (lyude)
v4: Mirror upstream crypto entry (omosnace)
    Add lyude to PSCI (lyude)
    Remove drivers/dma from DMA SUPPORT (snits)
v5: Add lyude to correct entry (lyude)

RH-Acked-by: Lyude Paul <lyude@redhat.com>
RH-Acked-by: Jerry Snitselaar <jsnitsel@redhat.com>
RH-Acked-by: Jerome Marchand <jmarchan@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: lyude@redhat.com
Cc: airlied@redhat.com
Cc: gtiwari@redhat.com
Cc: dmilburn@redhat.com
Cc: jsnitsel@redhat.com
Cc: jmarchan@redhat.com
Cc: jasowang@redhat.com
Cc: herbert.xu@redhat.com
Cc: dzickus@redhat.com
Cc: pauld@redhat.com
Cc: omosnace@redhat.com
Cc: davem@redhat.com
2021-08-30 10:50:50 -04:00
David Arcari 81f240eb7c RHMAINTAINERS: add entries for THERMAL and PIN CONTROL
Add myself as maintainer for these two areas

Acked-by: Prarit Bhargava <prarit@redhat.com>

Signed-off-by: David Arcari <darcari@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:50 -04:00
Gopal Tiwari 0ecdd1bcd3 update : NVMe maintainers list.
Adding Gopal Tiwari, Ewan D. Milne and Chris Leech.

RH-Acked-by: David Milburn <dmilburn@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

Signed-off-by: Gopal Tiwari <gtiwari@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:49 -04:00
Prarit Bhargava 1e78bc65d3 RHMAINTAINERS: Remove mcroce
mcroce is no longer with Red Hat.

RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:49 -04:00
Prarit Bhargava b70ac41a06 RHMAINTAINERS: nhorman cleanup
nhorman is no longer at Red Hat.

These are some cleanups and a removal of the SIERRA_NET USB BROADBAND MODEM
which will be captured through other areas.

tcamuso has volunteered to take the ISMT SMBUS driver.

v2: rebase on top of latest tree

RH-Acked-by: Tony Camuso <tcamuso@redhat.com>
RH-Acked-by: David Arcari <darcari@redhat.com>
RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: tcamuso@redhat.com
Cc: mleitner@redhat.com
Cc: cleech@redhat.com
Cc: jbenc@redhat.com
2021-08-30 10:50:49 -04:00
Dan Horák ae78e03dcb kernel.spec: don't override upstream compiler flags for ppc64le
Related: rhbz#1866485

Signed-off-by: Dan Horák <dan@danny.cz>
2021-08-30 10:50:49 -04:00
Justin M. Forbes 9a4d9a2069 Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:49 -04:00
Fedora Kernel Team 21ef8bccb4 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:48 -04:00
Fedora Kernel Team 68246d25ca [redhat] AUTOMATIC: New configs 2021-08-30 10:50:48 -04:00
Justin M. Forbes 552448c086 Fedora confi gupdate
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:48 -04:00
Fedora Kernel Team 13fa9971d2 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:48 -04:00
Ben Crocker dacc754055 mod-sign.sh: Fix syntax flagged by shellcheck
SC2006: Use $(...) notation instead of legacy backticked `...`.
SC2086: Double quote to prevent globbing and word splitting.

Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-08-30 10:50:48 -04:00
Don Zickus ed137c63f0 Swap how ark-latest is built
Today ark-latest is built by starting with ark-patches, merging
os-build and applying 'extra' patches from gitlab, and finally
tagged.

In preparation for a single tree workflow where ark-patches disappears,
lets swap the process to make it easier for ark-patches to be
removed.

Instead let's build ark-latest by starting with os-build, merge
ark-patches, apply 'extra' patches and tag  it.

Later, it becomes easy to drop the ark-patches merge and when no
'extra' patches exist, ark-latest and os-build are identical.

However, this leads to a changelog quirk.  The genspec logic
thinks all the ark-patches are new additions and adds entries
for that whole branch into the changelog because the MARKER has
not changed.

This is noise.  For now I created a temporary hack to work around
this until a single workflow is implemented and the problem naturally
goes away.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:48 -04:00
Don Zickus 62a693de4e Add extra version bump to os-build branch
Currently, ark-latest is built, version bumped and the gitlab-ci.yml
file secretly copies that changelog back to os-build.

I think we can improve that process, but it requires a change in
the release behaviour, version bump os-build first, then create
ark-latest and version bump a second time.

The second version bump should have a small changelog and only
captures the 'extra' patches that are necessary for the release.

This _is_ a behaviour change for the changelog and kernel NVR.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:47 -04:00
Don Zickus 260b7ffcbe dist-release: Avoid needless version bump.
The dist-release target allows the caller to repeatedly bump
the version in Makefile.rhelver, even though no changes was
added.

Change this behaviour to _only_ bump the version when either
a changelog entry was detected or the marker file was updated,
otherwise skip the version bump.

This becomes necessary for the next patch, when I change the
behaviour of the release script.  I intend to version bump
the os-build branch first, then create ark-latest and version
bump again.  Later when we consolidate to a single tree workflow,
there will be scenarios where os-build and ark-latest are identical
and the second version bump will be unnecessary.

This change is not expected to change anything, unless blind version
bumps are expected in certain scenarios.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:47 -04:00
Don Zickus e31977cf5c Add dist-fedora-release target
This is a target that will create the rawhide branch, ark-latest.

It is mostly copied from the gitlab-ci.yml and turned into a
Makefile target for easier understanding and execution.

An optimization is to move some of the duplicate code to
git-tree-check and replace git-status with git-diff-index
to make it easier to detect a dirty tree.

This target will be called by the maintainer and the gitlab-ci.yml
file.  Currently unused.

No noticable changes.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:47 -04:00
Don Zickus 8732e0be01 Remove redundant code in dist-release
Back with commit 3a65b42715, make
dist-git was changed to depend on dist-srpm instead of the spec
file.  As a result some legacy optimizations are now redundant,
remove them.

In dist-git, dist-srpm depends on TARBALL, so remove the explict
dependency in dist-git.

In dist-release-finish, dist-srpm calls dist-configs, dist-kabi,
dist-kabi-dup, sources-rh, so remove them too.

These cleanups also help speed up release testing. :-)

No noticable changes expected.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:47 -04:00
Don Zickus 2d48e38478 Makefile.common rename TAG to _TAG
I would like to use the TAG variable as input to the make merge and
release targets.  This allows the maintainer to control where the
merge or release starts from.

The internal variable TAG conflicts with this when the external TAG
is empty.  The Makefile accidentally chooses the internal TAG variable.

Resolve this by renaming the internal TAG variable to _TAG.  This
allows the scripts to pass in an external TAG variable with no
conflict.

The internal TAG variable is not used anywhere outside
Makefile.common.

No expected changes, purely cosmetic.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:47 -04:00
Justin M. Forbes 6de2dc24d6 Fedora config change
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:47 -04:00
Justin M. Forbes f8ef5be0d2 Fedora filter update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:46 -04:00
Justin M. Forbes cd8413fef1 Config update for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:46 -04:00
Fedora Kernel Team 6ee3dc37bd [redhat] AUTOMATIC: New configs 2021-08-30 10:50:46 -04:00
Fedora Kernel Team bf01d5684e [redhat] AUTOMATIC: New configs 2021-08-30 10:50:46 -04:00
Jiri Benc 6451f47e36 RHMAINTAINERS: networking: update maintainers
Delete Neil from NETWORKING [GENERAL] and SCTP PROTOCOL, since he left Red
Hat. Add Marcelo as a networking maintainer.

RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:46 -04:00
Tony Camuso 8b3e5f345d RHMAINTAINERS: Update QAT maintainers
Reassign the QAT maintenance to vdronov and tcamuso.

RH-Acked-by: Vladis Dronov <vdronov@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>
RH-Acked-by: Steve Best <sbest@redhat.com>

Signed-off-by: Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:45 -04:00
Eric Sandeen a6610c8635 rhdocs: RHMAINTAINERS assign sections to FAST
Assign sections of the kernel to the appropriate entities

RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: John W. Linville <linville@redhat.com>

[Prarit - This patch was lost and brought forward with a simple rebase.]

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Cc: Eric Sandeen <esandeen@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jakub Racek <jracek@redhat.com>
Cc: John Linville <linville@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
2021-08-30 10:50:45 -04:00
Jerry Snitselaar b1793e492e RHMAINTAINERS: Update DMA Mapping entry
I'm taking over the primary role for DMA Mapping
so update the maintainers entry.

RH-Acked-by: Myron Stowe <mstowe@redhat.com
RH-Acked-by: Don Dutile <ddutile@redhat.com>

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Donald Dutile <ddutile@redhat.com>
Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:45 -04:00
Dan Horák 0a0d1d5774 enable PROTECTED_VIRTUALIZATION_GUEST for all s390x kernels
Signed-off-by: Dan Horák <dan@danny.cz>
2021-08-30 10:50:45 -04:00
Fedora Kernel Team 8a0acf3dba [redhat] New configs in drivers/nvme
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NVME_TARGET_PASSTHRU:

 This enables target side NVMe passthru controller support for the
 NVMe Over Fabrics protocol. It allows for hosts to manage and
 directly access an actual NVMe controller residing on the target
 side, incuding executing Vendor Unique Commands.

 If unsure, say N.

 Symbol: NVME_TARGET_PASSTHRU [=n]
 Type  : bool
 Defined at drivers/nvme/target/Kconfig:19
   Prompt: NVMe Target Passthrough support
   Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m])
   Location:
     -> Device Drivers
       -> NVME Support
         -> NVMe Target support (NVME_TARGET [=m])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:45 -04:00
Fedora Kernel Team 9b6a972e1b [redhat] New configs in drivers/spi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SPI_CADENCE_QUADSPI:

 Enable support for the Cadence Quad SPI Flash controller.

 Cadence QSPI is a specialized controller for connecting an SPI
 Flash over 1/2/4-bit wide bus. Enable this option if you have a
 device with a Cadence QSPI controller and want to access the
 Flash as an MTD device.

 Symbol: SPI_CADENCE_QUADSPI [=n]
 Type  : tristate
 Defined at drivers/spi/Kconfig:204
   Prompt: Cadence Quad SPI controller
   Depends on: SPI [=y] && SPI_MASTER [=y] && OF [=y] && (ARM || ARM64 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> SPI support (SPI [=y])

---

 CONFIG_SPI_LANTIQ_SSC:

 This driver supports the Lantiq SSC SPI controller in master
 mode. This controller is found on Intel (former Lantiq) SoCs like
 the Danube, Falcon, xRX200, xRX300, Lightning Mountain.

 Symbol: SPI_LANTIQ_SSC [=n]
 Type  : tristate
 Defined at drivers/spi/Kconfig:502
   Prompt: Lantiq SSC SPI controller
   Depends on: SPI [=y] && SPI_MASTER [=y] && (LANTIQ || X86 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> SPI support (SPI [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:45 -04:00
Davide Caratti fbd7514c2a redhat: ark: enable CONFIG_NET_SCH_TAPRIO
move from 'fedora' to 'common', and remove the explicit disable from ark,
so it's enabled in the same way both on ark and fedora.

Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 10:50:44 -04:00
Davide Caratti 464363a8a4 redhat: ark: enable CONFIG_NET_SCH_ETF
move from 'fedora' to 'common', and remove the explicit disable from ark,
so it's enabled in the same way both on ark and fedora.

Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 10:50:44 -04:00
Fedora Kernel Team 8db2e9f1fa [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARCH_KEEMBAY:

 This enables support for Intel Movidius SoC code-named Keem Bay.

 Symbol: ARCH_KEEMBAY [=n]
 Type  : bool
 Defined at arch/arm64/Kconfig.platforms:139
   Prompt: Keem Bay SoC
   Location:
     -> Platform selection

---

 CONFIG_ARCH_SPARX5:

 This enables support for the Microchip Sparx5 ARMv8-based
 SoC family of TSN-capable gigabit switches.

 The SparX-5 Ethernet switch family provides a rich set of
 switching features such as advanced TCAM-based VLAN and QoS
 processing enabling delivery of differentiated services, and
 security through TCAM-based frame processing using versatile
 content aware processor (VCAP).

 Symbol: ARCH_SPARX5 [=n]
 Type  : bool
 Defined at arch/arm64/Kconfig.platforms:92
   Prompt: ARMv8 based Microchip Sparx5 SoC family
   Location:
     -> Platform selection
 Selects: PINCTRL [=y] && DW_APB_TIMER_OF [=n]

---

Cc: Mark Salter <msalter@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:44 -04:00
Fedora Kernel Team 70c90f62c0 [redhat] New configs in drivers/char
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HW_RANDOM_BA431:

 This driver provides kernel-side support for the Random Number
 Generator hardware based on Silex Insight BA431 IP.

 To compile this driver as a module, choose M here: the
 module will be called ba431-rng.

 Symbol: HW_RANDOM_BA431 [=n]
 Type  : tristate
 Defined at drivers/char/hw_random/Kconfig:77
   Prompt: Silex Insight BA431 Random Number Generator support
   Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Hardware Random Number Generator Core support (HW_RANDOM [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:44 -04:00
Fedora Kernel Team 52171b2bca [redhat] New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_SMCCC_SOC_ID:

 Include support for the SoC bus on the ARM SMCCC firmware based
 platforms providing some sysfs information about the SoC variant.

 Symbol: ARM_SMCCC_SOC_ID [=y]
 Type  : bool
 Defined at drivers/firmware/smccc/Kconfig:18
   Prompt: SoC bus device for the ARM SMCCC SOC_ID
   Depends on: HAVE_ARM_SMCCC_DISCOVERY [=y]
   Location:
     -> Firmware Drivers
 Selects: SOC_BUS [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:44 -04:00
Justin M. Forbes 479bc68b9b More Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:43 -04:00
Justin M. Forbes 4b18fce9ea New config deps
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:43 -04:00
Justin M. Forbes f0074ad30f Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:43 -04:00
Fedora Kernel Team 2bd6e01d62 [redhat] New configs in drivers/net/wireless
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MT7663S:

 This adds support for MT7663S 802.11ac 2x2:2 wireless devices.

 To compile this driver as a module, choose M here.

 Symbol: MT7663S [=n]
 Type  : tristate
 Defined at drivers/net/wireless/mediatek/mt76/mt7615/Kconfig:46
   Prompt: MediaTek MT7663S (SDIO) support
   Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && MMC [=m]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless LAN (WLAN [=y])
           -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
 Selects: MT76_SDIO [=n] && MT7663_USB_SDIO_COMMON [=n]

---

 CONFIG_RTW88_8821CE:

 Select this option will enable support for 8821CE chipset

 802.11ac PCIe wireless network adapter

 Symbol: RTW88_8821CE [=n]
 Type  : tristate
 Defined at drivers/net/wireless/realtek/rtw88/Kconfig:64
   Prompt: Realtek 8821CE PCI wireless network adapter
   Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTW88 [=m] && PCI [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless LAN (WLAN [=y])
           -> Realtek devices (WLAN_VENDOR_REALTEK [=y])
             -> Realtek 802.11ac wireless chips support (RTW88 [=m])
 Selects: RTW88_CORE [=m] && RTW88_PCI [=m] && RTW88_8821C [=n]

---

 CONFIG_WLAN_VENDOR_MICROCHIP:

 If you have a wireless card belonging to this class, say Y.

 Note that the answer to this question doesn't directly affect the
 kernel: saying N will just cause the configurator to skip all the
 questions about these cards. If you say Y, you will be asked for
 your specific card in the following questions.

 Symbol: WLAN_VENDOR_MICROCHIP [=y]
 Type  : bool
 Defined at drivers/net/wireless/microchip/Kconfig:2
   Prompt: Microchip devices
   Depends on: NETDEVICES [=y] && WLAN [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Wireless LAN (WLAN [=y])

---

Cc: Jarod Wilson <jarod@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:43 -04:00
Fedora Kernel Team 142cf27bdf [redhat] New configs in drivers/video
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FB_MODE_HELPERS:

 This enables functions for handling video modes using the
 Generalized Timing Formula and the EDID parser. A few drivers rely
 on this feature such as the radeonfb, rivafb, and the i810fb. If
 your driver does not take advantage of this feature, choosing Y will
 just increase the kernel size by about 5K.

 Symbol: FB_MODE_HELPERS [=n]
 Type  : bool
 Defined at drivers/video/fbdev/Kconfig:192
   Prompt: Enable Video Mode Handling Helpers
   Depends on: HAS_IOMEM [=y] && FB [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Frame buffer Devices
           -> Support for frame buffer devices (FB [=y])
 Selected by [n]:
   - FB_CLPS711X [=n] && HAS_IOMEM [=y] && FB [=y] && (ARCH_CLPS711X || COMPILE_TEST [=n])
   - FB_IMX [=n] && FB [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (ARCH_MXC [=n] || COMPILE_TEST [=n])
   - FB_UVESA [=n] && HAS_IOMEM [=y] && FB [=y] && CONNECTOR [=y]
   - FB_ATMEL [=n] && FB [=y] && OF [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (HAVE_FB_ATMEL [=n] || COMPILE_TEST [=n])
   - FB_NVIDIA [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_RIVA [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_I740 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_I810 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86_32 && AGP_INTEL [=n]
   - FB_LE80578 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86
   - FB_INTEL [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86 && AGP_INTEL [=n] && EXPERT [=n] && !DRM_I915 [=n]
   - FB_RADEON [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_SAVAGE [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_NEOMAGIC [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_3DFX [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_TRIDENT [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
   - FB_VT8500 [=n] && HAS_IOMEM [=y] && FB [=y]=y && ARM && ARCH_VT8500
   - FB_WM8505 [=n] && FB [=y]=y && HAS_IOMEM [=y] && (ARCH_VT8500 || COMPILE_TEST [=n])
   - FB_PXA [=n] && HAS_IOMEM [=y] && FB [=y] && ARCH_PXA && OF [=y]
   - FB_FSL_DIU [=n] && HAS_IOMEM [=y] && FB [=y] && FSL_SOC
   - FB_SMSCUFX [=n] && HAS_IOMEM [=y] && FB [=y] && USB [=y]
   - FB_UDL [=n] && HAS_IOMEM [=y] && FB [=y] && USB [=y]
   - FB_DA8XX [=n] && FB [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (ARCH_DAVINCI_DA8XX || SOC_AM33XX || COMPILE_TEST [=n])
   - FB_SM750 [=n] && STAGING [=n] && FB [=y] && PCI [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:43 -04:00
Fedora Kernel Team abe2f02c2e [redhat] New configs in sound/pci
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM:

 Intel hardware has a feature called 'silent stream', that
 keeps external HDMI receiver's analog circuitry powered on
 avoiding 2-3 sec silence during playback start. This mechanism
 relies on setting channel_id as 0xf, sending info packet and
 preventing codec D3 entry (increasing  platform static power
 consumption when HDMI receiver is plugged-in). 2-3 sec silence
 at the playback start is expected whenever there is format change.
 (default is 2 channel format).
 Say Y to enable Silent Stream feature.

 Symbol: SND_HDA_INTEL_HDMI_SILENT_STREAM [=n]
 Type  : bool
 Defined at sound/pci/hda/Kconfig:243
   Prompt: Enable Silent Stream always for HDMI
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_HDA [=m] && SND_HDA_INTEL [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> HD-Audio

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:43 -04:00
Fedora Kernel Team 74225c2e15 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:42 -04:00
Justin M. Forbes 94c5dcd8e1 First half of config updates for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:42 -04:00
Peter Robinson e460a05fda Updates for Fedora arm architectures for the 5.9 window
Updates for aarch64/ARMv7 for the first part of the 5.9 merge window
and catch up on the outstanding pending-fedora ones I missed.

There's two deletion of obolete Kconfig options for ark too.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:42 -04:00
Justin M. Forbes 451f492460 Merge 5.9 config changes from Peter Robinson
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:42 -04:00
Justin M. Forbes 4344edff93 Add config options that only show up when we prep on arm
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:42 -04:00
Fedora Kernel Team 21ecacb0eb [redhat] AUTOMATIC: New configs 2021-08-30 10:50:41 -04:00
Justin M. Forbes 52509bdb3f Config updates for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:41 -04:00
Peter Robinson a889eaa7c8 fedora: enable enery model
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:41 -04:00
Fedora Kernel Team 654cf9b5c5 [redhat] New configs in kernel/rcu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RCU_REF_SCALE_TEST:

 This option provides a kernel module that runs performance tests
 useful comparing RCU with various read-side synchronization mechanisms.
 The kernel module may be built after the fact on the running kernel to be
 tested, if desired.

 Say Y here if you want these performance tests built into the kernel.
 Say M if you want to build it as a module instead.
 Say N if you are unsure.

 Symbol: RCU_REF_SCALE_TEST [=n]
 Type  : tristate
 Defined at kernel/rcu/Kconfig.debug:64
   Prompt: Scalability tests for read-side synchronization (RCU and others)
   Depends on: DEBUG_KERNEL [=y]
   Location:
     -> Kernel hacking
       -> RCU Debugging
 Selects: TORTURE_TEST [=n] && SRCU [=y] && TASKS_RCU [=n] && TASKS_RUDE_RCU [=y] && TASKS_TRACE_RCU [=n]

---

Cc: Waiman Long <longman@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:41 -04:00
Fedora Kernel Team f1e13c32d1 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TEST_FPU:

 Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu
 which will trigger a sequence of floating point operations. This is used
 for self-testing floating point control register setting in
 kernel_fpu_begin().

 If unsure, say N.

 Symbol: TEST_FPU [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:2317
   Prompt: Test floating point operations in kernel space
   Depends on: RUNTIME_TESTING_MENU [=y] && X86 [=y] && !KCOV_INSTRUMENT_ALL [=n]
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Runtime Testing (RUNTIME_TESTING_MENU [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:41 -04:00
Fedora Kernel Team b2c8168ac9 [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_GPIO_PCA9570:

 Say yes here to enable the GPO driver for the NXP PCA9570 chip.

 To compile this driver as a module, choose M here: the module will
 be called gpio-pca9570.

 Symbol: GPIO_PCA9570 [=n]
 Type  : tristate
 Defined at drivers/gpio/Kconfig:965
   Prompt: PCA9570 4-Bit I2C GPO expander
   Depends on: GPIOLIB [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> I2C GPIO expanders

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:41 -04:00
Fedora Kernel Team e62970ae97 [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INV_ICM42600_I2C:

 This driver supports the InvenSense ICM-426xx motion tracking
 devices over I2C.

 This driver can be built as a module. The module will be called
 inv-icm42600-i2c.

 Symbol: INV_ICM42600_I2C [=n]
 Type  : tristate
 Defined at drivers/iio/imu/inv_icm42600/Kconfig:7
   Prompt: InvenSense ICM-426xx I2C driver
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Inertial measurement units
 Selects: INV_ICM42600 [=n] && REGMAP_I2C [=m]

---

 CONFIG_INV_ICM42600_SPI:

 This driver supports the InvenSense ICM-426xx motion tracking
 devices over SPI.

 This driver can be built as a module. The module will be called
 inv-icm42600-spi.

 Symbol: INV_ICM42600_SPI [=n]
 Type  : tristate
 Defined at drivers/iio/imu/inv_icm42600/Kconfig:19
   Prompt: InvenSense ICM-426xx SPI driver
   Depends on: IIO [=m] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Inertial measurement units
 Selects: INV_ICM42600 [=n] && REGMAP_SPI [=m]

---

 CONFIG_SCD30_CORE:

 Say Y here to build support for the Sensirion SCD30 sensor with carbon
 dioxide, relative humidity and temperature sensing capabilities.

 To compile this driver as a module, choose M here: the module will
 be called scd30_core.

 Symbol: SCD30_CORE [=n]
 Type  : tristate
 Defined at drivers/iio/chemical/Kconfig:88
   Prompt: SCD30 carbon dioxide sensor driver
   Depends on: IIO [=m]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Chemical Sensors
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:40 -04:00
Fedora Kernel Team 57e4759cd9 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_CORSAIR_CPRO:

 If you say yes here you get support for the Corsair Commander Pro
 controller.

 This driver can also be built as a module. If so, the module
 will be called corsair-cpro.

 Symbol: SENSORS_CORSAIR_CPRO [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:442
   Prompt: Corsair Commander Pro controller
   Depends on: HWMON [=y] && HID [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:40 -04:00
Fedora Kernel Team 4186298d26 [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_CLASS_MULTICOLOR:

 This option enables the multicolor LED sysfs class in /sys/class/leds.
 It wraps LED class and adds multicolor LED specific sysfs attributes
 and kernel internal API to it. You'll need this to provide support
 for multicolor LEDs that are grouped together. This class is not
 intended for single color LEDs. It can be built as a module.

 Symbol: LEDS_CLASS_MULTICOLOR [=n]
 Type  : tristate
 Defined at drivers/leds/Kconfig:33
   Prompt: LED Multicolor Class Support
   Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y]
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])
         -> LED Class Support (LEDS_CLASS [=y])

---

 CONFIG_LEDS_LP55XX_COMMON:

 This option supports common operations for LP5521/5523/55231/5562/8501
 devices.

 Symbol: LEDS_LP55XX_COMMON [=n]
 Type  : tristate
 Defined at drivers/leds/Kconfig:398
   Prompt: Common Driver for TI/National LP5521/5523/55231/5562/8501
   Depends on: NEW_LEDS [=y] && (LEDS_CLASS_MULTICOLOR [=n] || !LEDS_CLASS_MULTICOLOR [=n]) && OF [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])
 Selects: FW_LOADER [=y] && FW_LOADER_USER_HELPER [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:40 -04:00
Fedora Kernel Team 46e09cf416 [redhat] New configs in drivers/media
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CEC_CH7322:

 This is a driver for the Chrontel CH7322 CEC controller. It uses the
 generic CEC framework interface.
 CEC bus is present in the HDMI connector and enables communication
 between compatible devices.

 Symbol: CEC_CH7322 [=n]
 Type  : tristate
 Defined at drivers/media/cec/i2c/Kconfig:5
   Prompt: Chrontel CH7322 CEC controller
   Depends on: MEDIA_CEC_SUPPORT [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> HDMI CEC drivers (MEDIA_CEC_SUPPORT [=y])
 Selects: REGMAP_I2C [=m] && CEC_CORE [=m]

---

 CONFIG_VIDEO_DW9768:

 This is a driver for the DW9768 camera lens voice coil.
 DW9768 is a 10 bit DAC with 100mA output current sink
 capability. This is designed for linear control of
 voice coil motors, controlled via I2C serial interface.

 Symbol: VIDEO_DW9768 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:1283
   Prompt: DW9768 lens voice coil support
   Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m]
   Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Lens drivers
 Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n]

---

 CONFIG_VIDEO_RDACM20:

 This driver supports the IMI RDACM20 GMSL camera, used in
 ADAS systems.

 This camera should be used in conjunction with a GMSL
 deserialiser such as the MAX9286.

 Symbol: VIDEO_RDACM20 [=n]
 Type  : tristate
 Defined at drivers/media/i2c/Kconfig:1174
   Prompt: IMI RDACM20 camera support
   Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y]
   Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y]
   Location:
     -> Device Drivers
       -> Multimedia support (MEDIA_SUPPORT [=m])
         -> Media ancillary drivers
           -> Camera sensor devices
 Selects: V4L2_FWNODE [=n] && VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:40 -04:00
Fedora Kernel Team 5d0a63d330 [redhat] New configs in drivers/net/ethernet/mellanox
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MLX5_IPSEC:

 Build IPsec support for the Connect-X family of network cards by Mellanox
 Technologies.
 Note: If you select this option, the mlx5_core driver will include
 IPsec support for the Connect-X family.

 Symbol: MLX5_IPSEC [=n]
 Type  : bool
 Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:137
   Prompt: Mellanox Technologies IPsec Connect-X support
   Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE_EN [=y] && XFRM_OFFLOAD [=y] && (INET_ESP_OFFLOAD [=m] || INET6_ESP_OFFLOAD [=m])
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Ethernet driver support (ETHERNET [=y])
           -> Mellanox devices (NET_VENDOR_MELLANOX [=y])
 Selects: MLX5_ACCEL [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:40 -04:00
Fedora Kernel Team 892bae2ec8 [redhat] New configs in drivers/pci
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PCI_J721E_HOST:

 Say Y here if you want to support the TI J721E PCIe platform
 controller in host mode. TI J721E PCIe controller uses Cadence PCIe
 core.

 Symbol: PCI_J721E_HOST [=n]
 Type  : bool
 Defined at drivers/pci/controller/cadence/Kconfig:48
   Prompt: TI J721E PCIe platform host controller
   Depends on: PCI [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> PCI support (PCI [=y])
         -> PCI controller drivers
           -> Cadence PCIe controllers support
 Selects: PCIE_CADENCE_HOST [=n] && PCI_J721E [=n]

---

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:40 -04:00
Fedora Kernel Team d5c026e2a3 [redhat] New configs in drivers/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CHARGER_BQ2515X:

 Say Y to enable support for the TI BQ2515X family of battery
 charging integrated circuits. The BQ2515X are highly integrated
 battery charge management ICs that integrate the most common
 functions for wearable devices, namely a charger, an output voltage
 rail, ADC for battery and system monitoring, and push-button
 controller.

 Symbol: CHARGER_BQ2515X [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:613
   Prompt: TI BQ2515X battery charger family
   Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])
 Selects: REGMAP_I2C [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:39 -04:00
Fedora Kernel Team 80cca25c91 [redhat] New configs in drivers/tty
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SERIAL_IMX_EARLYCON:

 If you have enabled the earlycon on the Freescale IMX
 CPU you can make it the earlycon by answering Y to this option.

 Symbol: SERIAL_IMX_EARLYCON [=n]
 Type  : bool
 Defined at drivers/tty/serial/Kconfig:518
   Prompt: Earlycon on IMX serial port
   Depends on: TTY [=y] && HAS_IOMEM [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Enable TTY (TTY [=y])
           -> Serial drivers
 Selects: SERIAL_EARLYCON [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:39 -04:00
Fedora Kernel Team acf70ee918 [redhat] New configs in drivers/usb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_USB_OTG_PRODUCTLIST:

 If you say Y here, the "otg_productlist.h" file will be used as a
 product list, so USB peripherals not listed there will be
 rejected during enumeration.  This behavior is required by the
 USB OTG and EH specification for all devices not on your product's
 "Targeted Peripherals List".  "Embedded Hosts" are likewise
 allowed to support only a limited number of peripherals.

 Symbol: USB_OTG_PRODUCTLIST [=n]
 Type  : bool
 Defined at drivers/usb/core/Kconfig:58
   Prompt: Rely on OTG and EH Targeted Peripherals List
   Depends on: USB_SUPPORT [=y] && USB [=y]
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])

---

Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:39 -04:00
Peter Robinson a9d6559517 Use the configs/generic config for SND_HDA_INTEL everywhere
The SND_HDA_INTEL is actually badly named as it covers HDMI audio in a number
of use cases such as discrete nvidia and amd GPUs on POWER and aarch64. It
may have originally been an Intel only option but now it's basically appears
to be a generic HDMI Audio config option so basically we should enable it
where ever we enable sound, it's enabled as a module already in configs/generic,
so we shouldn't actually need to override it anywhere so remove the other options
they are either the same or do override it.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:39 -04:00
Peter Robinson b78d8aba2b Enable ZSTD compression algorithm on all kernels
The new ZSTD compression algorithm is generally faster/smaller so we want to
support it in all kernels so turn the functionality on universally.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:39 -04:00
Peter Robinson c8d3315c53 Enable ARM_SMCCC_SOC_ID on all aarch64 kernels
We'll need this functionality on all arm kernels so enable it in generic

Cc: Al Stone <ahs3@redhat.com>
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:38 -04:00
Peter Robinson 5e22aff812 iio: enable LTR-559 light and proximity sensor 2021-08-30 10:50:38 -04:00
Peter Robinson 52b95a4a41 iio: chemical: enable some popular chemical and partical sensors
The following two chemical/partical sensors are quite common so enable
them to make them easier to use.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:38 -04:00
Fedora Kernel Team 3248208368 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:38 -04:00
Fedora Kernel Team d232b53554 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:38 -04:00
Justin M. Forbes 1a2ca54dad More mismatches
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:38 -04:00
Justin M. Forbes aecabf4921 Fedora config change due to deps
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:37 -04:00
Justin M. Forbes 0ca9ea6856 CONFIG_SND_SOC_MAX98390 is now selected by SND_SOC_INTEL_DA7219_MAX98357A_GENERIC
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:37 -04:00
Justin M. Forbes 291d2a0d69 Config change required for build part 2
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:37 -04:00
Justin M. Forbes 59edec33b1 Config change required for build
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:37 -04:00
Justin M. Forbes 14036f9bc6 Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:37 -04:00
Fedora Kernel Team 37f5e7b6d1 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:37 -04:00
Fedora Kernel Team 0c2c84a52a [redhat] AUTOMATIC: New configs 2021-08-30 10:50:36 -04:00
Don Zickus 4c32ba75a9 Add ability to sync upstream through Makefile
Currently all the magic to sync upstream with os-build and ark-patches
is done through scripts in redhat/scripts/ci and .gitlab-ci.yml.

Make this easier by enabling this routine through a redhat/Makefile.

This allows:
* gitlab-ci.yml and maintainer to use same script
* allows maintainer to run local test runs before committing
* developers to hack on things a little more easily

This change also adds the ability to 'git push' the changes.  This is
safe because os-build and ark-patches are considered 'protected'
branches meaning only the developers in the 'Maintainers' group can
push to those branches (which is a tiny group right now).

Because I can't atomically commit this change and the change to
kernel-ark-ci's gitlab-ci.yml file, I need this change to go in first.

Then I can modify the gitlab-ci.yml file.

Functionally, this change should be no different than what currently
runs today.
2021-08-30 10:50:36 -04:00
Don Zickus 2e5a34f3b7 Add master merge check
Avoid constantly running the config update scripts when the merge to
master did not update anything.  This means there can be no new
configs to generate.

Same argument for ark-patches.

The only downside I see with this check is if the generate config
scripts fail and this needs to be re-run.  But we should be able
to do that by hand.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:36 -04:00
Don Zickus 6e88461501 Replace hardcoded values 'os-build' and project id with variables
As a step towards switching away from the os-build branch start by
using more variables.

The patch does 2 things:
* adds a use of PROJECT_ID
* replace os-build with BRANCH in the update configs script

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:36 -04:00
Prarit Bhargava 249bf7a2ec redhat/Makefile.common: Fix MARKER
'make setup-source' is failing with, for example,

fatal: Not a valid object name master
BUILDID is "hello". Update '/home/prarit/git-kernel/kernel-ark/localversion' to change.
Gathering new log entries since 2eb3eaedb74aa011774bb95fd6516d6d7858d0f8
fatal: ambiguous argument 'itd3590ebf6f91.1-1-..': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

As of 5.7.0 new tags were added to the tree of the form

	kernel-5.8.0-0.rc7.20200730gitd3590ebf6f91.1

After applying a patch the value of "git describe" is
kernel-5.8.0-0.rc7.20200730gitd3590ebf6f91.1-1-gd76dfb51aa86.  This string
is stored in TAG which is used by MARKER. The value of MARKER is set
using a cut command on 'g' which results in MARKER being set to
"it69119673bd50.1" instead of "d76dfb51aa86"

The problem with continuing to use cut and 'g' is that the tag string
may change again.  It is safer to use awk and '-g'.

Use awk instead of cut to evaluate MARKER.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:36 -04:00
Prarit Bhargava fc368c432f gitattributes: Remove unnecesary export restrictions
Both redhat/ and the makefile are publicly available.  There is no reason
to exclude them from tarballs, etc.

Remove the export restrictions on redhat/ and the makefile.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:35 -04:00
Justin M. Forbes 0c2c82fcdd Add new certs for dual signing with boothole
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:35 -04:00
Justin M. Forbes 50c7e90265 Update secureboot signing for dual keys
As part of the transition for the boothole vulnerability, we are signing
the kernel with both new keys and the old keys.  These are the spec
changes to make that happen.  We have actually been building with this
for some time, but didn't want to push the changes until it was public.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:35 -04:00
Prarit Bhargava 5de9302690 RHMAINTAINERS: Add integrity subsystem entry
Add integrity subsystem entry.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:35 -04:00
Peter Robinson 0d27dfacf8 fedora: enable LEDS_SGM3140 for arm configs
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:35 -04:00
Justin M. Forbes c8e9063b5a Enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:35 -04:00
Prarit Bhargava 415195408e redhat/configs: Fix common CONFIGs
Fixes found with 'evaluate_configs -j'

Verified via

make rh-configs
cp configs/*.config /tmp/rh-orig
evaluate_configs -j
make rh-configs
cp configs/*.config /tmp/rh-new
diff /tmp/rh-orig /tmp/rh-new

which shows no net changes to the final .config files.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:34 -04:00
Prarit Bhargava cbb7cd09bf redhat/configs: General CONFIG cleanups
Fixes found with  './evaluate_configs -p priority.[rhel|fedora] -f'

Verified via

make rh-configs
cp configs/*.config /tmp/rh-orig
evaluate_configs -p priority.rhel -f
make rh-configs
cp configs/*.config /tmp/rh-new
diff /tmp/rh-orig /tmp/rh-new

and

make fedora-configs
cp configs/*.config /tmp/fedora-orig
evaluate_configs -p priority.fedora -f
make fedora-configs
cp configs/*.config /tmp/fedora-new
diff /tmp/fedora-orig /tmp/fedora-new

which shows no net changes to the final .config files.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:34 -04:00
Prarit Bhargava d1f704e248 redhat/configs: Update & generalize evaluate_configs
evaluate_configs is a tool that verifies the CONFIG setting hierarchy for
the kernel.  It can display settings for a specific CONFIG, find and
remove extra CONFIG files and synchronize the CONFIG settings between
the common, ark, and fedora directories.

For example, to view a config,

[prarit@prarit configs]$ ./evaluate_configs -p priority.rhel -c CONFIG_HEADER_TEST
CONFIG_HEADER_TEST
legend                         g  ga1  ga2  d  da1  da2
common-x86_64                  y  -    -    -  X    -
common-ppc64le                 y  -    X    -  -    X
common-s390x                   y  -    X    -  -    X
common-s390x-zfcpdump          y  -    -    X  X    X
common-aarch64                 y  -    -    -  X    -
ark-x86_64                     y  -    -    -  X    -
ark-ppc64le                    y  -    X    -  -    X
ark-s390x                      y  -    X    -  -    X
ark-s390x-zfcpdump             y  -    -    X  X    X
ark-aarch64                    y  -    -    -  X    -
pending-common-x86_64          -  -    -    -  X    -
pending-common-ppc64le         -  -    X    -  -    X
pending-common-s390x           -  -    X    -  -    X
pending-common-s390x-zfcpdump  -  -    -    X  X    X
pending-common-aarch64         -  -    -    -  X    -

The legend row, shows the subdirectory entries.  These can be mapped
back to the priority.rhel entries, for example, for x86_64

x86_64=generic:generic-x86:generic-x86-x86_64
x86_64-debug=generic:generic-x86:generic-x86-x86_64:debug:debug-x86-x86_64

are combined into one entry for x86_64 where

g maps to "generic"
ga1 maps to "generic-x86"
ga2 maps to "generic-x86-x86-64"
d maps to "debug"
da1 maps to nothing (more on this below)
da2 maps to debug-x86-x86_64

The left hand column indicates the directory and config-variant.  For
example, ark-s390x-zfcpdump is the s390x-zfcpdump variant and the
row beside it shows the config settings in the ark directory.

The data contained in the output can have 5 values:

        y = CONFIG is set to 'y'
        m = CONFIG is set to 'm'
        n = CONFIG is set to 'is not set'
        - = CONFIG file does not exist
        X = CONFIG file entry is not in priority file

As can be seen above in the CONFIG_HEADER_TEST output, da1 is not present
in the priority.rhel file and is marked with an 'X'.

The -f option can be used to evaluate all the CONFIGs by executing, for
example

|# evaluate_configs -p priority.rhel -f

or a single CONFIG

|# evaluate_configs -p priority.rhel -f -c CONFIG_HEADER_TEST

and similarily the common, ark and fedora CONFIGs can be verified by
executing

evaluate_configs -j

or

evaluate_configs -j -c CONFIG_HEADER_TEST

The two CONFIG patches in this patchset are runs of

evaluate_configs -p priority.rhel -f
evaluate_configs -p priority.fedora -f

and

evaluate_configs -j

v2: Documentation cleanup (herton)

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:34 -04:00
Peter Robinson 04cf5c56d8 fedora: arm: Update some meson config options 2021-08-30 10:50:34 -04:00
Prarit Bhargava deb935c65e redhat/docs: Add Fedora RPM tagging date
Resending ... no acks.

P.

---8<---

An engineer pinged me this morning trying to figure out how to build
fc32 builds in the ARK tree.  There are no fc32 tags since we didn't
start tagging until very recently.

Add a comment about when we started tagging Fedora RPMs in the ARK tree.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: jforbes@redhat.com
2021-08-30 10:50:34 -04:00
Peter Robinson 86d8cdd505 Update config for renamed panel driver.
The DRM_PANEL_XINGBANGDA_XBD599 panel was in fact a DRM_PANEL_SITRONIX_ST7703 so
it's being renamed upstream.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:33 -04:00
Peter Robinson 7bf47ef33f Enable SERIAL_SC16IS7XX for SPI interfaces
This was enabled in Fedora kenels, except due to the weird KConfig bits
the actual config wasn't enabled in the end kernel build. This fixes is for
SPI which appears in some devices for RS-485 use cases.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-08-30 10:50:33 -04:00
Neal Gompa c8c7ae2484 [redhat] configs/fedora: Enable Btrfs asserts on debug kernels
With Btrfs being used by default, having our debug kernels offer
more debugging information can be helpful for driving improvements
into the filesystem.

Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
2021-08-30 10:50:33 -04:00
Neal Gompa bfbc6907a5 [redhat] configs/fedora: Build Btrfs into the kernel
Now that we are using Btrfs by default on most flavors of Fedora,
let's have the Btrfs filesystem built into the kernel to make
booting without an initramfs work.

Reference: https://fedoraproject.org/wiki/Changes/BtrfsByDefault

Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
2021-08-30 10:50:33 -04:00
Fedora Kernel Team cc9b6bb0e9 [redhat] New configs in drivers/md
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DM_EBS:

 dm-ebs emulates smaller logical block size on backing devices
 with larger ones (e.g. 512 byte sectors on 4K native disks).

 Symbol: DM_EBS [=n]
 Type  : tristate
 Defined at drivers/md/Kconfig:340
   Prompt: Emulated block size target (EXPERIMENTAL)
   Depends on: MD [=y] && BLK_DEV_DM [=m]
   Location:
     -> Device Drivers
       -> Multiple devices driver support (RAID and LVM) (MD [=y])
         -> Device mapper support (BLK_DEV_DM [=m])
 Selects: DM_BUFIO [=m]

---

 CONFIG_DM_MULTIPATH_HST:

 This path selector is a dynamic load balancer which selects
 the path expected to complete the incoming I/O in the shortest
 time by comparing estimated service time (based on historical
 service time).

 If unsure, say N.

 Symbol: DM_MULTIPATH_HST [=n]
 Type  : tristate
 Defined at drivers/md/Kconfig:455
   Prompt: I/O Path Selector based on historical service time
   Depends on: MD [=y] && DM_MULTIPATH [=m]
   Location:
     -> Device Drivers
       -> Multiple devices driver support (RAID and LVM) (MD [=y])
         -> Device mapper support (BLK_DEV_DM [=m])
           -> Multipath target (DM_MULTIPATH [=m])

---

Cc: Nigel Croxon <ncroxon@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:33 -04:00
Don Zickus 2eabb877d9 s390x-zfcpdump: Handle missing Module.symvers file
In 5.8-rc1, a change was made to not always generate a Module.symvers
file if no modules were built.  The s390x zfcpdump variant is a kernel
that is built with no modules enabled.

The kernel.spec file assumes Module.symvers always exists and fails to
build the zfcpdump variant.

Modify the spec file to detect the missing file and 'touch' it as a
workaround.  This file is used utilized by the kabi technology.  There
is probably a better long term fix, but this is the quick and easy fix.

Tested locally using cross-compilers.
2021-08-30 10:50:32 -04:00
Justin M. Forbes c44c507ba8 Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:32 -04:00
Fedora Kernel Team caa1752ba1 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:32 -04:00
Fedora Kernel Team c187d419d7 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:32 -04:00
Prarit Bhargava 3fecec9d7a redhat/configs: Add .tmp files to .gitignore
Looking for reviews ... repost.

P.

---8<---

Config file commands create .tmp files which can be picked up by git
commands.

Add .tmp files to .gitignore.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:32 -04:00
Davide Caratti 8169aafd29 disable uncommon TCP congestion control algorithms
build of cdg in ARK is already disabled: disable hybla, hsctp, illinois,
lp, scalable, vegas, veno and yeah as well.

Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-08-30 10:50:32 -04:00
Jeremy Cline 168a7fa131 [redhat] New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_IQS62X:

 Say Y here if you want to build core support for the Azoteq IQS620A,
 IQS621, IQS622, IQS624 and IQS625 multi-function sensors. Additional
 options must be selected to enable device-specific functions.

 To compile this driver as a module, choose M here: the module will
 be called iqs62x.

 Symbol: MFD_IQS62X [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:645
   Prompt: Azoteq IQS620A/621/622/624/625 core support
   Depends on: HAS_IOMEM [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_CORE [=y] && REGMAP_I2C [=m]

---
2021-08-30 10:50:31 -04:00
Prarit Bhargava 9ce2fd7245 RHMAINTAINERS: Update RHMAINTAINERS
A general update to RHMAINTAINERS.

All people and lists mentioned in this file have agreed to the
Fedora Privacy Policy here:

https://fedoraproject.org/wiki/Legal:PrivacyPolicy#Publicly_Available_Personal_Data

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Brian Masney <bmasney@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Chris Leech <cleech@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Josef Oskera <joskera@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
Cc: Kamal Heib <kheib@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Michal Schmidt <mschmidt@redhat.com>
Cc: Miklos Szeredi <mszeredi@redhat.com>
Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Patrick Talbert <ptalbert@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Richard Guy Briggs <rbriggs@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>
Cc: Toke Høiland-Jørgensen <toke@redhat.com>
Cc: Tom Rix <trix@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Cc: Yauheni Kaliuta <ykaliuta@redhat.com>
2021-08-30 10:50:31 -04:00
Justin M. Forbes bd201a5e9c Add new bpf man pages
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:31 -04:00
Justin M. Forbes a31826f7bd Add default option for CONFIG_ARM64_BTI_KERNEL to pending-common so that eln kernels build
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:31 -04:00
Prarit Bhargava 71da4ea993 redhat/Makefile: Add fedora-configs and rh-configs make targets
There are times when I have to generate both Fedora and RHEL configs.

Add fedora-configs and rh-configs make targets.

v2: Add rh-help entries.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:31 -04:00
Fedora Kernel Team 6677d68329 [redhat] New configs in drivers/i2c
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_I2C_QCOM_CCI:

 If you say yes to this option, support will be included for the
 built-in camera control interface on the Qualcomm SoCs.

 This driver can also be built as a module.  If so, the module
 will be called i2c-qcom-cci.

 Symbol: I2C_QCOM_CCI [=n]
 Type  : tristate
 Defined at drivers/i2c/busses/Kconfig:900
   Prompt: Qualcomm Camera Control Interface
   Depends on: I2C [=y] && HAS_IOMEM [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> I2C support
         -> I2C support (I2C [=y])
           -> I2C Hardware Bus support

---

Cc: Gopal Tiwari <gtiwari@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:30 -04:00
Prarit Bhargava 9ce0ef0922 redhat/configs: Use SHA512 for module signing
kernsec.org recommends using SHA512 [1] for kernel module signing.  There
isn't any reason not to do this and the benefit is a stronger module
hash.

[1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:30 -04:00
Don Zickus a2603c7574 genspec.sh: 'touch' empty Patchlist file for single tarball
I was playing around with SINGLE_TARBALL=1 to workaround an issue and
noticed the patch for breaking out individual patches did not account
for that scenario.

The srpm fails to generate due to the missing Patchlist file, which
is used to track the individual patch files.

Fix this by creating a empty file to use or 'touch $SOURCES/Patchlist'.

This allows the srpm to package all the necessary files.  I tested the
'prep' stage of rpmbuild and this empty file has no side effects.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:30 -04:00
Justin M. Forbes a9f0adf88c Fedora config update for rc1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:30 -04:00
Fedora Kernel Team 58375d360b [redhat] AUTOMATIC: New configs 2021-08-30 10:50:30 -04:00
Justin M. Forbes 83e5189a09 Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:30 -04:00
Fedora Kernel Team fb0f542b3a [redhat] AUTOMATIC: New configs 2021-08-30 10:50:29 -04:00
Fedora Kernel Team c4efeb9db7 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:29 -04:00
Justin M. Forbes a35a313902 Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:29 -04:00
Fedora Kernel Team 57698f428c [redhat] AUTOMATIC: New configs 2021-08-30 10:50:29 -04:00
Fedora Kernel Team 26fa571433 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:29 -04:00
CKI@GitLab 1d4dbb4779 [redhat] New configs in drivers/char
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HW_RANDOM_CCTRNG:

 Say 'Y' to enable the True Random Number Generator driver for the
 Arm TrustZone CryptoCell family of processors.
 Currently the CryptoCell 713 and 703 are supported.
 The driver is supported only in SoC where Trusted Execution
 Environment is not used.
 Choose 'M' to compile this driver as a module. The module
 will be called cctrng.
 If unsure, say 'N'.

 Symbol: HW_RANDOM_CCTRNG [=n]
 Type  : tristate
 Defined at drivers/char/hw_random/Kconfig:477
   Prompt: Arm CryptoCell True Random Number Generator support
   Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Hardware Random Number Generator Core support (HW_RANDOM [=y])

---

Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 10:50:28 -04:00
Jeremy Cline 9175ce5ecd [redhat] New configs in drivers/dma-buf
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DMABUF_HEAPS:

 Choose this option to enable the DMA-BUF userland memory heaps.
 This options creates per heap chardevs in /dev/dma_heap/ which
 allows userspace to allocate dma-bufs that can be shared
 between drivers.

 Symbol: DMABUF_HEAPS [=n]
 Type  : bool
 Defined at drivers/dma-buf/Kconfig:47
   Prompt: DMA-BUF Userland Memory Heaps
   Location:
     -> Device Drivers
       -> DMABUF options
 Selects: DMA_SHARED_BUFFER [=y]

Enabled at the request of Lyude Paul.

---

Cc: Don Dutile <ddutile@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Cc: Lyude Paul <lyude@redhat.com>
2021-08-30 10:50:28 -04:00
CKI@GitLab df140321e2 [redhat] New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_GATEWORKS_GSC:

 Enable support for the Gateworks System Controller (GSC) found
 on Gateworks Single Board Computers supporting system functions
 such as push-button monitor, multiple ADC's for voltage and
 temperature monitoring, fan controller and watchdog monitor.
 This driver provides common support for accessing the device.
 Additional drivers must be enabled in order to use the
 functionality of the device.

 Symbol: MFD_GATEWORKS_GSC [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:410
   Prompt: Gateworks System Controller
   Depends on: HAS_IOMEM [=y] && I2C [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_CORE [=m] && REGMAP_I2C [=m] && REGMAP_IRQ [=n]

---

Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 10:50:28 -04:00
CKI@GitLab ff123756f2 [redhat] New configs in kernel/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HIBERNATION_SNAPSHOT_DEV:

 Device used by the uswsusp tools.

 Say N if no snapshotting from userspace is needed, this also
 reduces the attack surface of the kernel.

 If in doubt, say Y.

 Symbol: HIBERNATION_SNAPSHOT_DEV [=y]
 Type  : bool
 Defined at kernel/power/Kconfig:83
   Prompt: Userspace snapshot device
   Depends on: HIBERNATION [=y]
   Location:
     -> Power management and ACPI options
       -> Hibernation (aka 'suspend to disk') (HIBERNATION [=y])

---

Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 10:50:28 -04:00
CKI@GitLab 691c607819 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TEST_HMM:

 This is a pseudo device driver solely for testing HMM.
 Say M here if you want to build the HMM test module.
 Doing so will allow you to run tools/testing/selftest/vm/hmm-tests.

 If unsure, say N.

 Symbol: TEST_HMM [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:2221
   Prompt: Test HMM (Heterogeneous Memory Management)
   Depends on: RUNTIME_TESTING_MENU [=y] && TRANSPARENT_HUGEPAGE [=y] && DEVICE_PRIVATE [=y]
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Runtime Testing (RUNTIME_TESTING_MENU [=y])
 Selects: HMM_MIRROR [=n] && MMU_NOTIFIER [=y]

---

Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 10:50:28 -04:00
Fedora Kernel Team 29a2b1612b [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_GPIO_AGGREGATOR:

 Say yes here to enable the GPIO Aggregator, which provides a way to
 aggregate existing GPIO lines into a new virtual GPIO chip.
 This can serve the following purposes:
   - Assign permissions for a collection of GPIO lines to a user,
   - Export a collection of GPIO lines to a virtual machine,
   - Provide a generic driver for a GPIO-operated device in an
     industrial control context, to be operated from userspace using
     the GPIO chardev interface.

 Symbol: GPIO_AGGREGATOR [=n]
 Type  : tristate
 Defined at drivers/gpio/Kconfig:1548
   Prompt: GPIO Aggregator
   Depends on: GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])

---

 CONFIG_GPIO_PCA953X_IRQ:

 Say yes here to enable the pca953x to be used as an interrupt
 controller. It requires the driver to be built in the kernel.

 Symbol: GPIO_PCA953X_IRQ [=n]
 Type  : bool
 Defined at drivers/gpio/Kconfig:957
   Prompt: Interrupt controller support for PCA953x
   Depends on: GPIOLIB [=y] && I2C [=y] && GPIO_PCA953X [=m]
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> I2C GPIO expanders
           -> PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports (GPIO_PCA953X [=m])
 Selects: GPIOLIB_IRQCHIP [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:28 -04:00
Fedora Kernel Team 84f20c36e0 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEBUG_INFO_COMPRESSED:

 Compress the debug information using zlib.  Requires GCC 5.0+ or Clang
 5.0+, binutils 2.26+, and zlib.

 Users of dpkg-deb via scripts/package/builddeb may find an increase in
 size of their debug .deb packages with this config set, due to the
 debug info being compressed with zlib, then the object files being
 recompressed with a different compression scheme. But this is still
 preferable to setting $KDEB_COMPRESS to "none" which would be even
 larger.

 Symbol: DEBUG_INFO_COMPRESSED [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:216
   Prompt: Compressed debugging information
   Depends on: DEBUG_INFO [=y]
   Location:
     -> Kernel hacking
       -> Compile-time checks and compiler options
         -> Compile the kernel with debug info (DEBUG_INFO [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:27 -04:00
Fedora Kernel Team d1b6f2ca2d [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AD9467:

 Say yes here to build support for Analog Devices:
 * AD9467 16-Bit, 200 MSPS/250 MSPS Analog-to-Digital Converter

 The driver requires the assistance of the AXI ADC IP core to operate,
 since SPI is used for configuration only, while data has to be
 streamed into memory via DMA.

 To compile this driver as a module, choose M here: the module will be
 called ad9467.

 Symbol: AD9467 [=n]
 Type  : tristate
 Defined at drivers/iio/adc/Kconfig:249
   Prompt: Analog Devices AD9467 High Speed ADC driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters
 Selects: ADI_AXI_ADC [=n]

---

 CONFIG_ADIS16475:

 Say yes here to build support for Analog Devices ADIS16470, ADIS16475,
 ADIS16477, ADIS16465, ADIS16467, ADIS16500, ADIS16505, ADIS16507 inertial
 sensors.

 To compile this driver as a module, choose M here: the module will be
 called adis16475.

 Symbol: ADIS16475 [=n]
 Type  : tristate
 Defined at drivers/iio/imu/Kconfig:32
   Prompt: Analog Devices ADIS16475 and similar IMU driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Inertial measurement units
 Selects: IIO_ADIS_LIB [=n] && IIO_ADIS_LIB_BUFFER [=n]

---

 CONFIG_ADI_AXI_ADC:

 Say yes here to build support for Analog Devices Generic
 AXI ADC IP core. The IP core is used for interfacing with
 analog-to-digital (ADC) converters that require either a high-speed
 serial interface (JESD204B/C) or a source synchronous parallel
 interface (LVDS/CMOS).
 Typically (for such devices) SPI will be used for configuration only,
 while this IP core handles the streaming of data into memory via DMA.

 Link: https://wiki.analog.com/resources/fpga/docs/axi_adc_ip
 If unsure, say N (but it's safe to say "Y").

 To compile this driver as a module, choose M here: the
 module will be called adi-axi-adc.

 Symbol: ADI_AXI_ADC [=n]
 Type  : tristate
 Defined at drivers/iio/adc/Kconfig:264
   Prompt: Analog Devices Generic AXI ADC IP core driver
   Depends on: IIO [=m]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters
 Selects: IIO_BUFFER [=y] && IIO_BUFFER_HW_CONSUMER [=n] && IIO_BUFFER_DMAENGINE [=n]
 Selected by [n]:
   - AD9467 [=n] && IIO [=m] && SPI [=y]

---

 CONFIG_ATLAS_EZO_SENSOR:

 Say Y here to build I2C interface support for the following
 Atlas Scientific EZO sensors
   * CO2 EZO Sensor

 To compile this driver as module, choose M here: the
 module will be called atlas-ezo-sensor.

 Symbol: ATLAS_EZO_SENSOR [=n]
 Type  : tristate
 Defined at drivers/iio/chemical/Kconfig:25
   Prompt: Atlas Scientific EZO sensors
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Chemical Sensors

---

 CONFIG_MAX1241:

 Say yes here to build support for Maxim max1241 12-bit, single-channel
 ADC.

 To compile this driver as a module, choose M here: the module will be
 called max1241.

 Symbol: MAX1241 [=n]
 Type  : tristate
 Defined at drivers/iio/adc/Kconfig:633
   Prompt: Maxim max1241 ADC driver
   Depends on: IIO [=m] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters

---

 CONFIG_SX9310:

 Say Y here to build a driver for Semtech's SX9310/SX9311 capacitive
 proximity/button sensor.

 To compile this driver as a module, choose M here: the
 module will be called sx9310.

 Symbol: SX9310 [=n]
 Type  : tristate
 Defined at drivers/iio/proximity/Kconfig:104
   Prompt: SX9310/SX9311 Semtech proximity sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Proximity and distance sensors
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && REGMAP_I2C [=m]

---

 CONFIG_VCNL3020:

 Say Y here if you want to build a driver for the Vishay VCNL3020
 proximity sensor.

 To compile this driver as a module, choose M here: the
 module will be called vcnl3020.

 Symbol: VCNL3020 [=n]
 Type  : tristate
 Defined at drivers/iio/proximity/Kconfig:143
   Prompt: VCNL3020 proximity sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Proximity and distance sensors
 Selects: REGMAP_I2C [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:27 -04:00
Fedora Kernel Team e7065346b9 [redhat] New configs in drivers/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PHY_CADENCE_SALVO:

 Enable this to support the Cadence SALVO PHY driver,
 this PHY is a legacy PHY, and only are used for USB3
 and USB2.

 Symbol: PHY_CADENCE_SALVO [=n]
 Type  : tristate
 Defined at drivers/phy/cadence/Kconfig:31
   Prompt: Cadence Salvo PHY Driver
   Depends on: OF [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=n]

---

 CONFIG_PHY_QCOM_IPQ4019_USB:

 Support for the USB PHY-s on Qualcomm IPQ40xx SoC-s.

 Symbol: PHY_QCOM_IPQ4019_USB [=n]
 Type  : tristate
 Defined at drivers/phy/qualcomm/Kconfig:21
   Prompt: Qualcomm IPQ4019 USB PHY driver
   Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=y]

---

 CONFIG_PHY_QCOM_USB_SNPS_FEMTO_V2:

 Enable support for the USB high-speed SNPS Femto phy on Qualcomm
 chipsets.  This PHY has differences in the register map compared
 to the V1 variants.  The PHY is paired with a Synopsys DWC3 USB
 controller on Qualcomm SOCs.

 Symbol: PHY_QCOM_USB_SNPS_FEMTO_V2 [=n]
 Type  : tristate
 Defined at drivers/phy/qualcomm/Kconfig:95
   Prompt: Qualcomm SNPS FEMTO USB HS PHY V2 module
   Depends on: OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=y]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:27 -04:00
Ondrej Mosnacek c9ca605f43 redhat/Makefile.common: fix RPMKSUBLEVEL condition
Either both sides need to be quoted or neither, otherwise the condition
won't work as intended.

Fixes: efa3fc15df ("Correctly name tarball for single tarball builds")
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 10:50:27 -04:00
Ondrej Mosnacek e628bbeca4 redhat/Makefile: silence KABI tar output
No need to print all the kabi files to stdout - drop the 'v' flag.

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 10:50:27 -04:00
Justin M. Forbes d6cd464387 [redhat] New configs in drivers/power
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BATTERY_CW2015:

 Say Y here to enable support for the cellwise cw2015
 battery fuel gauge (used in the Pinebook Pro & others)

 This driver can also be built as a module. If so, the module will be
 called cw2015_battery.

 Symbol: BATTERY_CW2015 [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:119
   Prompt: CW2015 Battery driver
   Depends on: POWER_SUPPLY [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])
 Selects: REGMAP_I2C [=m]

---

 CONFIG_CHARGER_BD99954:

 Say Y here to enable support for getting battery and charger
 information and altering charger configurations from the ROHM
 BD99954 charger IC.

 Symbol: CHARGER_BD99954 [=n]
 Type  : tristate
 Defined at drivers/power/supply/Kconfig:724
   Prompt: ROHM bd99954 charger driver
   Depends on: POWER_SUPPLY [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> Power supply class support (POWER_SUPPLY [=y])
 Selects: LINEAR_RANGES [=n]

---

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:26 -04:00
Fedora Kernel Team 70b60201d1 [redhat] New configs in drivers/input
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KEYBOARD_BCM:

 Say Y here if you want to use Broadcom keypad.

 To compile this driver as a module, choose M here: the
 module will be called bcm-keypad.

 Symbol: KEYBOARD_BCM [=n]
 Type  : tristate
 Defined at drivers/input/keyboard/Kconfig:774
   Prompt: Broadcom keypad driver
   Depends on: !UML && INPUT [=y] && INPUT_KEYBOARD [=y] && OF [=y] && HAVE_CLK [=y]
   Location:
     -> Device Drivers
       -> Input device support
         -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
           -> Keyboards (INPUT_KEYBOARD [=y])
 Selects: INPUT_MATRIXKMAP [=n]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:26 -04:00
Fedora Kernel Team 8c8778159a [redhat] New configs in drivers/mmc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MMC_SDHCI_OF_DWCMSHC:

 This selects Synopsys DesignWare Cores Mobile Storage Controller
 support.
 If you have a controller with this interface, say Y or M here.
 If unsure, say N.

 Symbol: MMC_SDHCI_OF_DWCMSHC [=n]
 Type  : tristate
 Defined at drivers/mmc/host/Kconfig:205
   Prompt: SDHCI OF support for the Synopsys DWC MSHC
   Depends on: MMC [=m] && MMC_SDHCI_PLTFM [=m] && OF [=y] && COMMON_CLK [=y]
   Location:
     -> Device Drivers
       -> MMC/SD/SDIO card support (MMC [=m])
         -> Secure Digital Host Controller Interface support (MMC_SDHCI [=m])
           -> SDHCI platform and OF driver helper (MMC_SDHCI_PLTFM [=m])

---

Cc: Gopal Tiwari <gtiwari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:26 -04:00
Justin M. Forbes b8754f37f6 One more Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:26 -04:00
Justin M. Forbes 3409db10cd Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:26 -04:00
Justin M. Forbes 357d8317d8 Fix PATCHLEVEL for merge window
When building during the merge window, we need to bump PATCHLEVEL in the
Makefile because Linus doesn't bump it until rc1. Something similar has
been in the Fedora spec forever.  Using 5.8 as an example, without this
change we build a kernel rpm version
kernel-5.8.0-0.rc0.20200608gitaf7b4801030c.1.fc33 but with a uname of
kernel-5.7.0-0.rc0.20200608gitaf7b4801030c.1.fc33 which places the
modules in the rpm versioned directory where the kernel does not know to
look for them.  With this change, both the rpm and the uname would be
the kernel-5.8 version.

While it might be cleaner to only run this replacement if we are in the
merge window, this is much simpler than making changes across 2
additional Makefiles, and the end result should always be the same.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:26 -04:00
Fedora Kernel Team 056dc9466f [redhat] AUTOMATIC: New configs 2021-08-30 10:50:25 -04:00
Fedora Kernel Team b9479b320b [redhat] AUTOMATIC: New configs 2021-08-30 10:50:25 -04:00
Fedora Kernel Team 0177cf4c18 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:25 -04:00
Fedora Kernel Team 26a8587fdb [redhat] AUTOMATIC: New configs 2021-08-30 10:50:25 -04:00
Justin M. Forbes 863ae38ad6 Change ark CONFIG_COMMON_CLK to yes, it is selected already by other options
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:25 -04:00
Justin M. Forbes e3c9ee7d0d Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:24 -04:00
Justin M. Forbes 5dce84533b [redhat] AUTOMATIC: New configs 2021-08-30 10:50:24 -04:00
Justin M. Forbes c0544a62ff [redhat] AUTOMATIC: New configs 2021-08-30 10:50:24 -04:00
Justin M. Forbes 3d525acdc3 Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:24 -04:00
Fedora Kernel Team 51f59561e6 [redhat] New configs in lib/math
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PRIME_NUMBERS:

 This option provides a simple prime number generator for test
 modules.

 If unsure, say N.

 Symbol: PRIME_NUMBERS [=n]
 Type  : tristate
 Defined at lib/math/Kconfig:8
   Prompt: Simple prime number generator for testing
   Location:
     -> Library routines
 Selected by [n]:
   - DRM_DEBUG_SELFTEST [=n] && HAS_IOMEM [=y] && DRM [=m] && DEBUG_KERNEL [=y]
   - DRM_I915_SELFTEST [=n] && HAS_IOMEM [=y] && EXPERT [=n] && DRM_I915 [=m]

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-08-30 10:50:24 -04:00
Fedora Kernel Team 5a6b56626b [redhat] AUTOMATIC: New configs 2021-08-30 10:50:24 -04:00
Fedora Kernel Team 9927dade23 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:23 -04:00
Justin M. Forbes e67af2bd2b Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:23 -04:00
Fedora Kernel Team 518425461e [redhat] AUTOMATIC: New configs 2021-08-30 10:50:23 -04:00
Jeremy Cline ff3952291c [redhat] New configs in drivers/net/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MDIO_IPQ8064:

 This driver supports the MDIO interface found in the network
 interface units of the IPQ8064 SoC

 Symbol: MDIO_IPQ8064 [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:160
   Prompt: Qualcomm IPQ8064 MDIO interface support
   Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && HAS_IOMEM [=y] && OF_MDIO [=y] && MFD_SYSCON [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> MDIO bus device drivers (MDIO_DEVICE [=y])

---

 CONFIG_MDIO_MVUSB:

 A USB to MDIO converter present on development boards for
 Marvell's Link Street family of Ethernet switches.

 Symbol: MDIO_MVUSB [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:182
   Prompt: Marvell USB to MDIO Adapter
   Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && USB [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> MDIO bus device drivers (MDIO_DEVICE [=y])

---

 CONFIG_MDIO_XPCS:

 This module provides helper functions for Synopsys DesignWare XPCS
 controllers.

 Symbol: MDIO_XPCS [=n]
 Type  : tristate
 Defined at drivers/net/phy/Kconfig:224
   Prompt: Synopsys DesignWare XPCS controller
   Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> MDIO bus device drivers (MDIO_DEVICE [=y])
 Selected by [n]:
   - STMMAC_ETH [=n] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=n] && HAS_IOMEM [=y] && HAS_DMA [=y]

---

Cc: Petr Oros <poros@redhat.com>
2021-08-30 10:50:23 -04:00
Jeremy Cline 4b6355add3 [redhat] New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BPF_LSM:

 Enables instrumentation of the security hooks with eBPF programs for
 implementing dynamic MAC and Audit Policies.

 If you are unsure how to answer this question, answer N.

 Symbol: BPF_LSM [=n]
 Type  : bool
 Defined at init/Kconfig:1623
   Prompt: LSM Instrumentation with BPF
   Depends on: BPF_EVENTS [=y] && BPF_SYSCALL [=y] && SECURITY [=y] && BPF_JIT [=y]
   Location:
     -> General setup

---
2021-08-30 10:50:23 -04:00
Justin M. Forbes 238d51ce49 More module filtering for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:22 -04:00
Justin M. Forbes df7f215262 Update filters for rnbd in Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:22 -04:00
Justin M. Forbes 04a0959d71 Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:22 -04:00
Fedora Kernel Team 600d18b5ef [redhat] AUTOMATIC: New configs 2021-08-30 10:50:22 -04:00
Fedora Kernel Team 1dbf8bce35 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:22 -04:00
Fedora Kernel Team dd1209ff03 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:22 -04:00
Fedora Kernel Team 693a515714 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:21 -04:00
Justin M. Forbes e81510549a Fix up module filtering for 5.8
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:21 -04:00
Justin M. Forbes 6b6e425429 Fedora config updates 2021-08-30 10:50:21 -04:00
Fedora Kernel Team cc24aa9cb2 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:21 -04:00
Fedora Kernel Team 5a6d438515 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:21 -04:00
Justin M. Forbes 520eefead5 More Fedora config work
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:20 -04:00
Fedora Kernel Team 703e787b06 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:20 -04:00
Fedora Kernel Team f18d4d42c3 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:20 -04:00
Justin M. Forbes a66d283053 RTW88BE and CE have been extracted to their own modules
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:20 -04:00
CKI@GitLab 9e8ef22428 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_AMD_ENERGY:

 If you say yes here you get support for core and package energy
 sensors, based on RAPL MSR for AMD family 17h and above CPUs.

 This driver can also be built as a module. If so, the module
 will be called as amd_energy.

 Symbol: SENSORS_AMD_ENERGY [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:327
   Prompt: AMD RAPL MSR based Energy driver
   Depends on: HWMON [=y] && X86 [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

 CONFIG_SENSORS_MAX16601:

 If you say yes here you get hardware monitoring support for Maxim
 MAX16601.

 This driver can also be built as a module. If so, the module will
 be called max16601.

 Symbol: SENSORS_MAX16601 [=n]
 Type  : tristate
 Defined at drivers/hwmon/pmbus/Kconfig:149
   Prompt: Maxim MAX16601
   Depends on: HWMON [=y] && PMBUS [=m]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])

---

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 10:50:20 -04:00
CKI@GitLab 8c0e18c517 [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DRM_CHRONTEL_CH7033:

 Enable support for the Chrontel CH7033 VGA/DVI/HDMI Encoder, as
 found in the Dell Wyse 3020 thin client.

 If in doubt, say "N".

 Symbol: DRM_CHRONTEL_CH7033 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:30
   Prompt: Chrontel CH7033 Video Encoder
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m]

---

 CONFIG_DRM_NWL_MIPI_DSI:

 This enables the Northwest Logic MIPI DSI Host controller as
 for example found on NXP's i.MX8 Processors.

 Symbol: DRM_NWL_MIPI_DSI [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:71
   Prompt: Northwest Logic MIPI DSI Host controller
   Depends on: DRM_BRIDGE [=y] && DRM [=m] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y] && GENERIC_PHY_MIPI_DPHY [=n] && MFD_SYSCON [=y] && MULTIPLEXER [=n] && REGMAP_MMIO [=y]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 10:50:20 -04:00
Justin M. Forbes 33adf484dc [redhat] New configs in net/bridge
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BRIDGE_MRP:

 If you say Y here, then the Ethernet bridge will be able to run MRP
 protocol to detect loops

 Say N to exclude this support and reduce the binary size.

 If unsure, say N.

 Symbol: BRIDGE_MRP [=n]
 Type  : bool
 Defined at net/bridge/Kconfig:65
   Prompt: MRP protocol
   Depends on: NET [=y] && BRIDGE [=m]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> 802.1d Ethernet Bridging (BRIDGE [=m])

---

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:19 -04:00
CKI@GitLab 7087084de6 [redhat] New configs in block/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BLK_INLINE_ENCRYPTION:

 Build the blk-crypto subsystem. Enabling this lets the
 block layer handle encryption, so users can take
 advantage of inline encryption hardware if present.

 Symbol: BLK_INLINE_ENCRYPTION [=n]
 Type  : bool
 Defined at block/Kconfig:189
   Prompt: Enable inline encryption support in block layer
   Depends on: BLOCK [=y]
   Location:
     -> Enable the block layer (BLOCK [=y])

---

Cc: Ming Lei <minlei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: CKI@GitLab <cki-project@redhat.com>
2021-08-30 10:50:19 -04:00
Justin M. Forbes bd533ca06c Set CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:19 -04:00
Justin M. Forbes 288f94223e Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:19 -04:00
Justin M. Forbes e37369a042 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:19 -04:00
Justin M. Forbes 2415f6077b [redhat] AUTOMATIC: New configs 2021-08-30 10:50:18 -04:00
Justin M. Forbes 5441bd79aa Arm64 Use Branch Target Identification for kernel
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:18 -04:00
Justin M. Forbes 4e345a146d Change value of CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE
From https://www.paul-moore.com/blog/d/2020/06/linux_v57.html

"Deprecate setting “/sys/fs/selinux/checkreqprot” to 1. This flag was
originally created to deal with legacy userspace and the READ_IMPLIES_EXEC
personality flag. We changed the default from 1 to 0 back in Linux v4.4 and
now we are taking the next step of deprecating it, at some point in the future
we will take the final step of rejecting 1."

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:18 -04:00
Justin M. Forbes 62a0a36cfc Fedora config updates 2021-08-30 10:50:18 -04:00
CKI@GitLab 6ce3a498eb [redhat] AUTOMATIC: New configs 2021-08-30 10:50:18 -04:00
CKI@GitLab e2ad2f08de [redhat] AUTOMATIC: New configs 2021-08-30 10:50:18 -04:00
Justin M. Forbes fa2c71a60e Fix configs for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:17 -04:00
CKI@GitLab c957e9fd26 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:17 -04:00
CKI@GitLab 6dd4b465e6 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:17 -04:00
Justin M. Forbes a436ab8cb8 Add zero-commit to format-patch options
Because of the way the trees are mangled, the hash for patches
change with each build.  This creates an unnecessary line of diff in
each patch file which is makes a diff in dist-git difficult to read.
Let's zero it to clean it up.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:17 -04:00
Jeremy Cline 37b7e8fdd8 Copy Makefile.rhelver as a source file rather than a patch
Include Makefile.rhelver by treating it as a source file rather than
generating it in a patch. This avoids depending on the tree being
prepared having a reference to the master branch, which should fix the
CKI build failures. It's also simpler.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:17 -04:00
Justin M. Forbes c2eff41bba Move the sed to clear the patch templating outside of conditionals
While we only add broken out patches if we aren't doing a single tarball
we still need to remove the template markers if we are.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:16 -04:00
Justin M. Forbes afa522a3e4 Match template format in kernel.spec.template 2021-08-30 10:50:16 -04:00
Justin M. Forbes f34071fbb8 Break out the Patches into individual files for dist-git 2021-08-30 10:50:16 -04:00
Jeremy Cline 6fa15c1085 Break the Red Hat patch into individual commits
People like to go look at the dist-git instead of a source tree for
patch files and there were complaints about the big diff file. Jump
through some hoops to generate a list of patches from the release branch
so the patches are preserved in dist-git.

Denys Vlasenko <dvlasenk@redhat.com>
Rado Vrbovsky <rvrbovsk@redhat.com>
Clark Williams <williams@redhat.com>
Jan Stancek <jstancek@redhat.com>
Juri Lelli <jlelli@redhat.com>
"Herton R. Krzesinski" <herton@redhat.com>
Frantisek Hrbata <fhrbata@redhat.com>
Luis Claudio Goncalves <lgoncalv@redhat.com>
Jeremy Cline <jcline@redhat.com>
Justin Forbes <jforbes@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:16 -04:00
David Howells 58b65cfdea Fix update_scripts.sh unselective pattern sub
The update_scripts.sh script doesn't correctly strip the suffix from the
end of the pathname, but will substitute for it anywhere in the path.  The
pattern really ought to have been /[.]$TARGET$//.

Fix this by using a special shell expansion to do it instead of invoking a
sed pipeline.

Signed-off-by: David Howells <dhowells@redhat.com>
cc: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:16 -04:00
Jeremy Cline eb3cd0f974 [redhat] New configs in drivers/pwm
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PWM_DEBUG:

 This option enables some additional checks to help lowlevel driver
 authors to get their callbacks implemented correctly.
 It is expected to introduce some runtime overhead and diagnostic
 output to the kernel log, so only enable while working on a driver.

 Symbol: PWM_DEBUG [=n]
 Type  : bool
 Defined at drivers/pwm/Kconfig:36
   Prompt: PWM lowlevel drivers additional checks and debug messages
   Depends on: PWM [=y] && DEBUG_KERNEL [=y]
   Location:
     -> Device Drivers
       -> Pulse-Width Modulation (PWM) Support (PWM [=y])

---
2021-08-30 10:50:16 -04:00
Justin M. Forbes d31903458b Add cec to the filter overrides
If we enable CONFIG_DRM_DP_CEC as is currently enabled in the RHEL
config, and should be enabled in the Fedora config, the build fails
because drm_kms_helper.ko in kernel-core requires symbols from cec.ko
which is filtered to kernel-modules. This brings the cec.ko module into
kernel-core to satisfy this dependency

This change also turns CONFIG_DRM_DP_CEC back on for Fedora.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:15 -04:00
Justin M. Forbes c871dd85ec Add overrides to filter-modules.sh
This adds an overrides list to filter-modules.sh and a section to
process this list.  It is to be used when a specific module which would
be filtered to kernel-modules needs to remain in kernel-core for depmod
reasons.  A current example of this is cec.ko. The drm_kms_helper.ko
module needs symbols from it if we enable CONFIG_DRM_DP_CEC.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:15 -04:00
Jeremy Cline 4fbdc78bfb [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MAGIC_SYSRQ_SERIAL_SEQUENCE:

 Specifies a sequence of characters that can follow BREAK to enable
 SysRq on a serial console.

 If unsure, leave an empty string and the option will not be enabled.

 Symbol: MAGIC_SYSRQ_SERIAL_SEQUENCE [=]
 Type  : string
 Defined at lib/Kconfig.debug:434
   Prompt: Char sequence that enables magic SysRq over serial
   Depends on: MAGIC_SYSRQ_SERIAL [=y]
   Location:
     -> Kernel hacking
       -> Generic Kernel Debugging Instruments
         -> Magic SysRq key (MAGIC_SYSRQ [=y])
           -> Enable magic SysRq key over serial (MAGIC_SYSRQ_SERIAL [=y])

---

 CONFIG_PROVE_RAW_LOCK_NESTING:

 Enable the raw_spinlock vs. spinlock nesting checks which ensure
 that the lock nesting rules for PREEMPT_RT enabled kernels are
 not violated.

 NOTE: There are known nesting problems. So if you enable this
 option expect lockdep splats until these problems have been fully
 addressed which is work in progress. This config switch allows to
 identify and analyze these problems. It will be removed and the
 check permanentely enabled once the main issues have been fixed.

 If unsure, select N.

 Symbol: PROVE_RAW_LOCK_NESTING [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:1099
   Prompt: Enable raw_spinlock - spinlock nesting checks
   Depends on: PROVE_LOCKING [=y]
   Location:
     -> Kernel hacking
       -> Lock Debugging (spinlocks, mutexes, etc...)
         -> Lock debugging: prove locking correctness (PROVE_LOCKING [=y])

---

 CONFIG_TEST_MIN_HEAP:

 Enable this to turn on min heap function tests. This test is
 executed only once during system boot (so affects only boot time),
 or at module load time.

 If unsure, say N.

 Symbol: TEST_MIN_HEAP [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:1799
   Prompt: Min heap test
   Depends on: RUNTIME_TESTING_MENU [=y] && (DEBUG_KERNEL [=y] || m && MODULES [=y])
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Runtime Testing (RUNTIME_TESTING_MENU [=y])

Enabled on debug kernels at the request of Prarit Bhargava

---

Cc: prarit@redhat.com
Cc: clark@redhat.com
2021-08-30 10:50:15 -04:00
Prarit Bhargava ab5ca911fa redhat/configs: Enable CONFIG_SMC91X and disable CONFIG_SMC911X
Bugzilla: http://bugzilla.redhat.com/1722136

Upstream Status: RHEL only

CONFIG_SMC91X requires CONFIG_NET_VENDOR_SMSC and all other SMSC config
options to be disabled.  Even though CONFIG_SMC911X is listed as 'm' it is
currently disabled in the final .config for aarch64.  CONFIG_SMC911X's
config entry should also list the config as disabled.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:15 -04:00
Jeremy Cline c2075e5652 Include bpftool-struct_ops man page in the bpftool package
Upstream has added a new man page, package it.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:15 -04:00
Jeremy Cline 41dc96c683 Add sharedbuffer_configuration.py to the pathfix.py script
The sharedbuffer_configuration.py selftests script uses an ambiguous
Python version, explicitly mangle it to Python 3.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:14 -04:00
Tom Stellard dda30561e7 Use __make macro instead of make
This will make it possible for buildroots to inject their own arguments to
make (e.g. CC=clang) by overriding the __make macro.
2021-08-30 10:50:14 -04:00
Jeremy Cline 8618fe07f5 Sign off generated configuration patches
Have the script sign off the configuration patches it generates.
Although it seems somewhat meaningless to have a script agree to the
terms of the DCO, the authors of the script authoring the patches have
and this makes running a CI job to check all patches for Signed-off-by
tags simpler.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:14 -04:00
Jeremy Cline 9167a53af2 [redhat] New configs in kernel/trace
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TRACE_EVENT_INJECT:

 Allow user-space to inject a specific trace event into the ring
 buffer. This is mainly used for testing purpose.

 If unsure, say N.

 Symbol: TRACE_EVENT_INJECT [=n]
 Type  : bool
 Prompt: Trace event injection
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])
   Defined at kernel/trace/Kconfig:674
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && TRACING [=y]

---
2021-08-30 10:50:14 -04:00
Jeremy Cline 7274dd1ff9 Drop the static path configuration for the Sphinx docs
There are no static files at this time. I don't know the first thing
about CSS and rely on my elders and betters to make the documentation
look presentable. Configuring a static directory also generates a Sphinx
warning when it isn't present (which it isn't on clean checkouts because
it's empty) so just remove it.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:14 -04:00
Prarit Bhargava eeb4d27d58 redhat: Add dummy-module kernel module
For years we've had a useful kernel kernel module, dummy-module, in the
tree.

Add dummy-module to the redhat directory.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:14 -04:00
Jeremy Cline 61c6e4c2ba [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_BCM63XX_I2S_WHISTLER:

 Say Y if you want to add support for ASoC audio on Broadcom
 DSL/PON chips (bcm63158, bcm63178)

 If you don't know what to do here, say N

 Symbol: SND_BCM63XX_I2S_WHISTLER [=n]
 Type  : tristate
 Defined at sound/soc/bcm/Kconfig:21
   Prompt: SoC Audio support for the Broadcom BCM63XX I2S module
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
 Selects: REGMAP_MMIO [=n]

---

 CONFIG_SND_SOC_INTEL_SOF_PCM512x_MACH:

 This adds support for ASoC machine driver for SOF platforms
 with TI PCM512x I2S audio codec.
 Say Y or m if you have such a device.
 If unsure select "N".

 Symbol: SND_SOC_INTEL_SOF_PCM512x_MACH [=n]
 Type  : tristate
 Defined at sound/soc/intel/boards/Kconfig:464
   Prompt: SOF with TI PCM512x codec
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && (SND_SOC_SOF_HDA_LINK [=y] || SND_SOC_SOF_BAYTRAIL [=n]) && I2C [=y] && ACPI [=y] && (SND_SOC_SOF_HDA_AUDIO_CODEC [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n]) || SND_SOC_SOF_BAYTRAIL [=n] && (X86_INTEL_LPSS [=y] || COMPILE_TEST [=n])) && SND_HDA_CODEC_HDMI [=m]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
 Selects: SND_SOC_PCM512x_I2C [=n]

Enabled as a module at the request of Jaroslav Kysela. Note, enabling
this as m enables CONFIG_SND_SOC_PCM512x_I2C, which has been been
included in this commit.

---

 CONFIG_SND_SOC_SOF_DEBUG_PROBES:

 This option enables the data probing feature that can be used to
 gather data directly from specific points of the audio pipeline.
 Say Y if you want to enable probes.
 If unsure, select "N".

 Symbol: SND_SOC_SOF_DEBUG_PROBES [=n]
 Type  : bool
 Defined at sound/soc/sof/Kconfig:44
   Prompt: SOF enable data probing
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
 Selects: SND_SOC_COMPRESS [=y]

Enabled for debug configurations at the request of Jaroslav Kysela.
Note, this exposes the following option:

 CONFIG_SND_SOC_SOF_HDA_PROBES
        bool "SOF enable probes over HDA"
        depends on SND_SOC_SOF_DEBUG_PROBES
        help
          This option enables the data probing for Intel(R).
                  Intel(R) Skylake and newer platforms.
          Say Y if you want to enable probes.
          If unsure, select "N".

---

 CONFIG_SND_SOC_TLV320ADCX140:

 Add support for Texas Instruments tlv320adc3140, tlv320adc5140 and
 tlv320adc6140 quad channel ADCs.

 Symbol: SND_SOC_TLV320ADCX140 [=n]
 Type  : tristate
 Defined at sound/soc/codecs/Kconfig:1345
   Prompt: Texas Instruments TLV320ADCX140 CODEC family
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> CODEC drivers
 Selects: REGMAP_I2C [=m]
 Implied by [n]:
   - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
2021-08-30 10:50:13 -04:00
Jeremy Cline 1f310f7dc0 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TEST_LOCKUP:

 This builds the "test_lockup" module that helps to make sure
 that watchdogs and lockup detectors are working properly.

 Depending on module parameters it could emulate soft or hard
 lockup, "hung task", or locking arbitrary lock for a long time.
 Also it could generate series of lockups with cooling-down periods.

 If unsure, say N.

 Symbol: TEST_LOCKUP [=n]
 Type  : tristate
 Defined at lib/Kconfig.debug:979
   Prompt: Test module to generate lockups
   Location:
     -> Kernel hacking
       -> Debug Oops, Lockups and Hangs

---
2021-08-30 10:50:13 -04:00
Jeremy Cline 7dedf9f79d [redhat] New configs in drivers/mmc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MMC_HSQ:

 This selects the MMC Host Software Queue support. This may increase
 performance, if the host controller and its driver supports it.

 If you have a controller/driver supporting this interface, say Y or M
 here.

 If unsure, say N.

 Symbol: MMC_HSQ [=n]
 Type  : tristate
 Defined at drivers/mmc/host/Kconfig:953
   Prompt: MMC Host Software Queue support
   Depends on: MMC [=m]
   Location:
     -> Device Drivers
       -> MMC/SD/SDIO card support (MMC [=m])
 Selected by [n]:
   - MMC_SDHCI_SPRD [=n] && MMC [=m] && ARCH_SPRD && MMC_SDHCI_PLTFM [=m]

---

Cc: Gopal Tiwari <gtiwari@redhat.com>
2021-08-30 10:50:13 -04:00
Jeremy Cline a6edb1003e [redhat] New configs in drivers/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PHY_CADENCE_TORRENT:

 Support for Cadence Torrent PHY.

 Symbol: PHY_CADENCE_TORRENT [=n]
 Type  : tristate
 Defined at drivers/phy/cadence/Kconfig:6
   Prompt: Cadence Torrent PHY driver
   Depends on: OF [=y] && HAS_IOMEM [=y]
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=n]

---

 CONFIG_PHY_QCOM_USB_HS_28NM:

 Enable this to support the Qualcomm Synopsys DesignWare Core 28nm
 High-Speed PHY driver. This driver supports the Hi-Speed PHY which
 is usually paired with either the ChipIdea or Synopsys DWC3 USB
 IPs on MSM SOCs.

 Symbol: PHY_QCOM_USB_HS_28NM [=n]
 Type  : tristate
 Defined at drivers/phy/qualcomm/Kconfig:95
   Prompt: Qualcomm 28nm High-Speed PHY
   Depends on: (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && (EXTCON [=y] || !EXTCON [=y])
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=y]

---

 CONFIG_PHY_QCOM_USB_SS:

 Enable this to support the Super-Speed USB transceiver on various
 Qualcomm chipsets.

 Symbol: PHY_QCOM_USB_SS [=n]
 Type  : tristate
 Defined at drivers/phy/qualcomm/Kconfig:106
   Prompt: Qualcomm USB Super-Speed PHY driver
   Depends on: (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && (EXTCON [=y] || !EXTCON [=y])
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=y]

---
2021-08-30 10:50:13 -04:00
Jiri Benc c58d57224a redhat: enable CONFIG_LWTUNNEL_BPF
This is enabled in RHEL 8 and should be enabled in ARK, too.

Signed-off-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 10:50:13 -04:00
Justin M. Forbes 2e2e139db3 Remove typoed config file aarch64CONFIG_SM_GCC_8150
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:12 -04:00
Justin M. Forbes 61567f986d Add Documentation back to kernel-devel as it has Kconfig now
This was fixed in Fedora back in January, and then got dropped in the
ARK switch over for some reason.  Kernel-devel needs
Documentation/Kconfig.

rhbz 1789641

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-08-30 10:50:12 -04:00
Jeremy Cline d4873d17f1 Copy distro files rather than moving them
Moving them clobbers them in the dist-git repository. People using the
dist-git to rebuild the SRPM might "fedpkg prep" and then "fedpkg local"
(or similar) which fails because the files got moved.

Cc: jforbes@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:12 -04:00
Brian Masney b37ae5f661 kernel.spec: fix 'make scripts' for kernel-devel package
Upstream status: RHEL only

Running 'make scripts' in /usr/src/kernels/$VERSION triggers the
following error:

    scripts/selinux/genheaders/genheaders.c:19:10: fatal error:
    classmap.h: No such file or directory

Let's fix that by including the necessary two files from the
directory security/selinux/include/ in the kernel-devel package.
Once those files are added, another error is triggered:

    scripts/sortextable.c:31:10: fatal error: tools/be_byteshift.h:
    No such file or directory

Let's correct that error by adding two more files from tools/include/
to the kernel-devel package as well. This will get 'make scripts'
working.

This change adds 20K (before compression) to the kernel-devel package.

Signed-off-by: Brian Masney <bmasney@redhat.com>
2021-08-30 10:50:12 -04:00
Brian Masney aafd175ec0 Makefile: correct help text for dist-cross-<arch>-rpms
Upstream Status: RHEL only

The dist-full-help target shows the target dist-cross-<arch>-rpm,
however it's really dist-cross-<arch>-rpms. Let's go ahead and correct
the help text.

Signed-off-by: Brian Masney <bmasney@redhat.com>
2021-08-30 10:50:12 -04:00
Prarit Bhargava b7d7e0969b redhat/Makefile: Fix RHEL8 python warning
When building on a python2 system the following warning is displayed:

Processing /data/working-repos/kernel-ark/redhat/configs/kernel-x86_64-fedora.config ... done
Processing /data/working-repos/kernel-ark/redhat/configs/kernel-x86_64-rhel.config ... done
Processed config files are in /data/working-repos/kernel-ark/redhat/configs
ERROR: your build environment is not compatible with RHEL8.
To fix this, run:
ln -s /usr/bin/python3 /usr/libexec/platform-python

Change the message to be distribution agnostic.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:12 -04:00
Prarit Bhargava 901683b934 redhat: Change Makefile target names to dist-
The distribution specific Makefile target names begin with rh-.  Switch
them to be use the distro agnostic dist-.

rh-dist-git-test and rh-dist-git are renamed to dist-git-test and
dist-git.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>

v2: Update to include jcline's newly added docs
v3: Clean up rh-help and rh-full-help output.  I made all text conform
to 80 chars.
2021-08-30 10:50:11 -04:00
Prarit Bhargava 076bd8f381 configs: Disable Serial IR driver
This is an old driver and no longer used.  It can be disabled.

Disable the Serial IR driver.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Jeff Bastian <jbastian@redhat.com>
2021-08-30 10:50:11 -04:00
Pablo Greco 619a514757 Fix "multiple %files for package kernel-tools"
When built with_tools on %{cpupowerarchs}, %files for kernel-tools is duplicated, fix it so we use the correct one for each case

Signed-off-by: Pablo Greco <pgreco@centosproject.org>
2021-08-30 10:50:11 -04:00
Jeremy Cline 8f0283847a Introduce a Sphinx documentation project
Although the GitLab wiki is pretty nice for getting started, it doesn't
offer a great way for folks to contribute or provide reviews for
changes. Convert the current Wiki to RST and build it with Sphinx. This
should be nearly identical to the content of the wiki with the exception
of a new section on contributing to the documentation.

When this is accepted, a new CI job can be added to automatically lint,
build, and host the Sphinx documentation on GitLab pages[0].

[0] https://docs.gitlab.com/ee/user/project/pages/

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:11 -04:00
Don Zickus 88ea07d06e Build ARK against ELN
ARK used to build against the RHEL-8 buildroots.  Going forward,
it will build against the ELN buildroot (Fedora space).  Adjust
the spec file to handle these changes.

This change still builds under RHEL-8 as llvm-toolset was a meta
package for clang and llvm.

V2: Remove llvm-toolset

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:11 -04:00
Jeremy Cline fabdb7f0d8 Drop the requirement to have a remote called linus
ARK's master branch tracks Linus's master branch, so drop the check for
a remote named "linus" (which might be wrong anyway) and use the local
master branch to calculate the snapshot.

While this does assume that the local master branch is up-to-date,
that's better than trying to guess the correct remote name and can be
easily scripted.

Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:11 -04:00
Don Zickus 22a8d4f7d1 Rename 'internal' branch to 'os-build'
Developers have mentioned that 'internal' sounds like a branch to avoid
instead of the first branch to merge.  A suggestion by Prarit was to
use os-build.

Straight forward re-name of internal to os-build.  The bulk of the
changes are documentation and script updates.
2021-08-30 10:50:10 -04:00
Jeremy Cline 72fc4676d6 Only include open merge requests with "Include in Releases" label
Without this flag, the release script pulls in any merge request labeled
for inclusion in a release, not just the currently open merge requests.
Applying a patch that already got merged fails, which is why this
morning's release job didn't succeed.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:10 -04:00
Jeremy Cline 7c78026fb8 Package gpio-watch in kernel-tools
A new binary, gpio-watch, was introduced with v5.7. Package it in
-tools.

Clark Williams <williams@redhat.com>
Rado Vrbovsky <rvrbovsk@redhat.com>
Luis Claudio Goncalves <lgoncalv@redhat.com>
"Herton R. Krzesinski" <herton@redhat.com>
Frantisek Hrbata <fhrbata@redhat.com>
Jan Stancek <jstancek@redhat.com>
Jeremy Cline <jcline@redhat.com>
Denys Vlasenko <dvlasenk@redhat.com>
Juri Lelli <jlelli@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:10 -04:00
Jeremy Cline 50779e9b27 Exit non-zero if the tag already exists for a release
The CI job can't determine if the release already exists or not with
the current script, so it fails when it tries to run the follow-up
scripts. This allows us to skip the rest of the job when the tag already
exists so maintainers only see failed jobs when something is actually
wrong.

If the script exits 1 or 2 it's for reasons that require maintainer
intervention. This exits 3 to distinguish between those cases and the
case that there hasn't been an update to upstream.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:10 -04:00
Jeremy Cline 6728f28392 Adjust the changelog update script to not push anything
The other CI scripts don't push branches so they can be easily run
locally. Pushing is left as an exercise to the runner and it's easy for
CI to continue to push changes.

This also moves the script in with the rest of the ARK CI scripts.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:10 -04:00
Jeremy Cline 40ba78f1f4 Drop --target noarch from the rh-rpms make target
The rh-rpms target is described in the help text as the target to use if
you want to "create the binary RPMS for the kernel". However, the
rpmbuild command provided two --target arguments, one for $(MACH) and a
second one for noarch. Apparently rpmbuild just uses whatever is last
because rh-rpms was just building the noarch packages.

While the author believes documentation is critical, it's more useful
when the user has what it documents as well.

Fixes: #26

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:09 -04:00
Bastien Nocera 1671c2c3bb [redhat] Enable Creative SB0540 remote control driver
Signed-off-by: Bastien Nocera <hadess@hadess.net>
2021-08-30 10:50:09 -04:00
Jeremy Cline a832b05117 Add a script to generate release tags and branches
This is intended to be run on a daily schedule to produce release
branches/tags.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:09 -04:00
Justin M. Forbes 3b20d0ecb2 Set CONFIG_VDPA for fedora 2021-08-30 10:50:09 -04:00
Justin M. Forbes c35e8e74e8 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:09 -04:00
Justin M. Forbes bdccf6685a [redhat] AUTOMATIC: New configs 2021-08-30 10:50:09 -04:00
Jeremy Cline b2133c2222 [redhat] New configs in drivers/net/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BAREUDP:

 This adds a bare UDP tunnel module for tunnelling different
 kinds of traffic like MPLS, IP, etc. inside a UDP tunnel.

 To compile this driver as a module, choose M here: the module
 will be called bareudp.

 Symbol: BAREUDP [=n]
 Type  : tristate
 Defined at drivers/net/Kconfig:262
   Prompt: Bare UDP Encapsulation
   Depends on: NETDEVICES [=y] && NET_CORE [=y] && INET [=y] && (IPV6 [=y] || !IPV6 [=y])
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Network core driver support (NET_CORE [=y])
 Selects: NET_UDP_TUNNEL [=m] && GRO_CELLS [=y]

Enabled at the request of Jiri Benc

---

Cc: Jiri Benc <jbenc@redhat.com>
2021-08-30 10:50:08 -04:00
Jeremy Cline 911f44d944 Add a README to the dist-git repository
Fedora users are used to the dist-git repository being a particular way.
Add some documentation so the change is less confusing.

Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Justin Forbes <jforbes@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:08 -04:00
Jeremy Cline 77b4c924e0 Provide defaults in ark-rebase-patches.sh
Like ark-update-configs.sh, provide defaults for the script.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:08 -04:00
Jeremy Cline ed84266ab3 Default ark-rebase-patches.sh to not report issues
Like ark-update-configs.sh, only report bugs if the REPORT_BUGS
environment variable is present. This is only really useful in the CI
environment.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:08 -04:00
Jeremy Cline 2f3843368d [redhat] New configs in fs/exfat
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EXFAT_FS:

 This allows you to mount devices formatted with the exFAT file system.
 exFAT is typically used on SD-Cards or USB sticks.

 To compile this as a module, choose M here: the module will be called
 exfat.

 Symbol: EXFAT_FS [=n]
 Type  : tristate
 Defined at fs/exfat/Kconfig:3
   Prompt: exFAT filesystem support
   Depends on: BLOCK [=y]
   Location:
     -> File systems
       -> DOS/FAT/EXFAT/NT Filesystems
 Selects: NLS [=y]

---
2021-08-30 10:50:08 -04:00
Jeremy Cline dbda3903bb [redhat] New configs in drivers/dma-buf
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DMABUF_MOVE_NOTIFY:

 Don''t pin buffers if the dynamic DMA-buf interface is available on both the
 exporter as well as the importer. This fixes a security problem where
 userspace is able to pin unrestricted amounts of memory through DMA-buf.
 But marked experimental because we don''t jet have a consistent execution
 context and memory management between drivers.

 Symbol: DMABUF_MOVE_NOTIFY [=n]
 Type  : bool
 Defined at drivers/dma-buf/Kconfig:42
   Prompt: Move notify between drivers (EXPERIMENTAL)
   Location:
     -> Device Drivers
       -> DMABUF options

Enabled at the request of Prarit Bhargava to avoid the security issue.

---

Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:07 -04:00
Jeremy Cline a6d925867c [redhat] New configs in mm/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PAGE_REPORTING:

 Free page reporting allows for the incremental acquisition of
 free pages from the buddy allocator for the purpose of reporting
 those pages to another entity, such as a hypervisor, so that the
 memory can be freed within the host for other uses.

 Symbol: PAGE_REPORTING [=n]
 Type  : bool
 Defined at mm/Kconfig:246
   Prompt: Free page reporting
   Location:
     -> Memory Management options
 Selected by [n]:
   - VIRTIO_BALLOON [=n] && VIRTIO_MENU [=y] && VIRTIO [=n]

---

 CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842:

 Use the 842 algorithm as the default compression algorithm.

 Symbol: ZSWAP_COMPRESSOR_DEFAULT_842 [=n]
 Type  : bool
 Defined at mm/Kconfig:586
   Prompt: 842
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default compressor (<choice> [=y])
 Selects: CRYPTO_842 [=n]

---

 CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE:

 Use the Deflate algorithm as the default compression algorithm.

 Symbol: ZSWAP_COMPRESSOR_DEFAULT_DEFLATE [=n]
 Type  : bool
 Defined at mm/Kconfig:574
   Prompt: Deflate
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default compressor (<choice> [=y])
 Selects: CRYPTO_DEFLATE [=y]

---

 CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4:

 Use the LZ4 algorithm as the default compression algorithm.

 Symbol: ZSWAP_COMPRESSOR_DEFAULT_LZ4 [=n]
 Type  : bool
 Defined at mm/Kconfig:592
   Prompt: LZ4
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default compressor (<choice> [=y])
 Selects: CRYPTO_LZ4 [=n]

---

 CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC:

 Use the LZ4HC algorithm as the default compression algorithm.

 Symbol: ZSWAP_COMPRESSOR_DEFAULT_LZ4HC [=n]
 Type  : bool
 Defined at mm/Kconfig:598
   Prompt: LZ4HC
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default compressor (<choice> [=y])
 Selects: CRYPTO_LZ4HC [=n]

---

 CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO:

 Use the LZO algorithm as the default compression algorithm.

 Symbol: ZSWAP_COMPRESSOR_DEFAULT_LZO [=y]
 Type  : bool
 Defined at mm/Kconfig:580
   Prompt: LZO
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default compressor (<choice> [=y])
 Selects: CRYPTO_LZO [=y]

---

 CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD:

 Use the zstd algorithm as the default compression algorithm.
 Symbol: ZSWAP_COMPRESSOR_DEFAULT_ZSTD [=n]
 Type  : bool
 Defined at mm/Kconfig:604
   Prompt: zstd
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default compressor (<choice> [=y])
 Selects: CRYPTO_ZSTD [=n]

---

 CONFIG_ZSWAP_DEFAULT_ON:

 If selected, the compressed cache for swap pages will be enabled
 at boot, otherwise it will be disabled.

 The selection made here can be overridden by using the kernel
 command line 'zswap.enabled=' option.

 Symbol: ZSWAP_DEFAULT_ON [=n]
 Type  : bool
 Defined at mm/Kconfig:663
   Prompt: Enable the compressed cache for swap pages by default
   Depends on: ZSWAP [=y]
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])

---

 CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD:

 Use the z3fold allocator as the default allocator.

 Symbol: ZSWAP_ZPOOL_DEFAULT_Z3FOLD [=n]
 Type  : bool
 Defined at mm/Kconfig:642
   Prompt: z3fold
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default allocator (<choice> [=y])
 Selects: Z3FOLD [=n]

---

 CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD:

 Use the zbud allocator as the default allocator.

 Symbol: ZSWAP_ZPOOL_DEFAULT_ZBUD [=y]
 Type  : bool
 Defined at mm/Kconfig:636
   Prompt: zbud
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default allocator (<choice> [=y])
 Selects: ZBUD [=y]

---

 CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC:

 Use the zsmalloc allocator as the default allocator.
 Symbol: ZSWAP_ZPOOL_DEFAULT_ZSMALLOC [=n]
 Type  : bool
 Defined at mm/Kconfig:648
   Prompt: zsmalloc
   Depends on: <choice>
   Location:
     -> Memory Management options
       -> Compressed cache for swap pages (EXPERIMENTAL) (ZSWAP [=y])
         -> Compressed cache for swap pages default allocator (<choice> [=y])
 Selects: ZSMALLOC [=y]

---

Cc: Larry Woodman <lwoodman@redhat.com>
2021-08-30 10:50:07 -04:00
Jeremy Cline 4ec149f759 Drop DIST from release commits and tags
The dist is defined in the build root. Including it in source tags is
confusing since a source rpm might be built in multiple build roots
(e.g. Fedora Rawhide, stable releases, and ELN).

The tag format for releases is now
kernel-<upstream_version>-<release>.<buildid>. For example, instead of
kernel-5.6.0-1.elrdy, the tag is now kernel-5.6.0-1.

Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:07 -04:00
Jeremy Cline 4ad546c1bc Place the buildid before the dist in the release
Fedora placed the buildid tag before the dist tag.  Match that behavior
here and pipe the buildid into the specfile for users who want to
continue rebuilding from the dist-git repository.

Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:07 -04:00
Jeremy Cline a8b9e532c2 Sync up with Fedora arm configuration prior to merging
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:07 -04:00
Jeremy Cline bbb18690d0 [redhat] Add a script to automatically set new configs
This script merges the latest changes from mainline, creates the default
configs, and creates branches for all the changes. This is intended to
be run on a schedule and can optionally file issues against GitLab to
alert maintainers when manual intervention is required.

Branches are not pushed anywhere so developers can use this script
locally and the CI job can manage when branches are pushed.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:07 -04:00
Jeremy Cline c95476d442 Disable CONFIG_PROTECTED_VIRTUALIZATION_GUEST for zfcpdump
Upstream commit a0f60f8431 ("s390/protvirt: Add sysfs firmware
interface for Ultravisor information") introduces a number of functions
if either CONFIG_KVM or CONFIG_PROTECTED_VIRTUALIZATION_GUEST are
enabled and make reference to uv_info, which is only defined if
CONFIG_KVM is enabled. Since CONFIG_KVM is disabled for the zfcpdump
kernel, disable CONFIG_PROTECTED_VIRTUALIZATION_GUEST.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:06 -04:00
Jeremy Cline 0f71c24087 [redhat] New configs in drivers/s390
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_QETH_OSN:

 This enables the qeth driver to support devices in OSN mode.
 This feature will be removed in 2021.
 If unsure, choose N.

 Symbol: QETH_OSN [=y]
 Type  : bool
 Defined at drivers/s390/net/Kconfig:94
   Prompt: qeth OSN device support
   Depends on: NETDEVICES [=y] && S390 [=y] && QETH [=m]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> S/390 network device drivers
           -> Gigabit Ethernet device support (QETH [=m])

---

 CONFIG_QETH_OSX:

 This enables the qeth driver to support devices in OSX mode.
 If unsure, choose N.

 Symbol: QETH_OSX [=y]
 Type  : bool
 Defined at drivers/s390/net/Kconfig:103
   Prompt: qeth OSX device support
   Depends on: NETDEVICES [=y] && S390 [=y] && QETH [=m]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> S/390 network device drivers
           -> Gigabit Ethernet device support (QETH [=m])

---

Cc: Cornelia Huck <cohuck@redhat.com>
2021-08-30 10:50:06 -04:00
Jeremy Cline 05a9c8b9f5 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:06 -04:00
Jeremy Cline 93179b6923 [redhat] Sync up the Fedora configs for 5.7-rc1
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:06 -04:00
Don Zickus ecf6ad75c3 Add RHMAINTAINERS file and supporting conf
Provide a mapping to the RHEL kernel maintainers in various
subsystem trees.  Useful for generating the right cc's on
patches to ARK/Fedora.

The main motivation is to find the right cc's for reviewing
config changes needed for ARK.

A .get_maintainers.conf file is added as an example usecase
but is currently disabled. I expect kernel development on this
tree will still send patches upstream and not to RHEL
developers.  But when this tree forks for RHEL, the file
will get uncommented.
2021-08-30 10:50:06 -04:00
Jeremy Cline f5f12f9195 [redhat] New configs in drivers/hid
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HID_GLORIOUS:

 Support for Glorious PC Gaming Race mice such as
 the Glorious Model O, O- and D.

 Symbol: HID_GLORIOUS [=n]
 Type  : tristate
 Defined at drivers/hid/Kconfig:365
   Prompt: Glorious PC Gaming Race mice
   Depends on: INPUT [=y] && HID [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> HID bus support (HID [=y])
           -> Special HID drivers

---

 CONFIG_HID_MCP2221:

 Provides I2C and SMBUS host adapter functionality over USB-HID
 through MCP2221 device.

 To compile this driver as a module, choose M here: the module
 will be called hid-mcp2221.ko.

 Symbol: HID_MCP2221 [=n]
 Type  : tristate
 Defined at drivers/hid/Kconfig:1155
   Prompt: Microchip MCP2221 HID USB-to-I2C/SMbus host support
   Depends on: INPUT [=y] && HID [=y] && USB_HID [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> HID support
         -> HID bus support (HID [=y])
           -> Special HID drivers

---

Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
2021-08-30 10:50:05 -04:00
Jeremy Cline 41fd04ecd1 [redhat] New configs in drivers/edac
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EDAC_DMC520:

 Support for error detection and correction on the
 SoCs with ARM DMC-520 DRAM controller.

 Symbol: EDAC_DMC520 [=n]
 Type  : tristate
 Defined at drivers/edac/Kconfig:526
   Prompt: ARM DMC-520 ECC
   Depends on: EDAC [=y] && ARM64 [=y]
   Location:
     -> Device Drivers
       -> EDAC (Error Detection And Correction) reporting (EDAC [=y])

Enabled as a module at the request of Aristeu Rozanski
---

Cc: Aristeu Rozanski <aris@redhat.com>
2021-08-30 10:50:05 -04:00
Jeremy Cline 2c69c6fc3a [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_GPIO_MLXBF2:

 Say Y here if you want GPIO support on Mellanox BlueField 2 SoC.

 Symbol: GPIO_MLXBF2 [=n]
 Type  : tristate
 Defined at drivers/gpio/Kconfig:1402
   Prompt: Mellanox BlueField 2 SoC GPIO
   Depends on: GPIOLIB [=y] && PCI [=y] && (MELLANOX_PLATFORM [=y] && ARM64 [=y] && ACPI [=y] || 64BIT [=y] && COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> PCI GPIO expanders
 Selects: GPIO_GENERIC [=m]

Enabled at the request of Alaa Hleihel

---

Cc: Alaa Hleihel <ahleihel@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:05 -04:00
Jeremy Cline cfeb60a874 [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DRM_DISPLAY_CONNECTOR:

 Driver for display connectors with support for DDC and hot-plug
 detection. Most display controller handle display connectors
 internally and don't need this driver, but the DRM subsystem is
 moving towards separating connector handling from display controllers
 on ARM-based platforms. Saying Y here when this driver is not needed
 will not cause any issue.

 Symbol: DRM_DISPLAY_CONNECTOR [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:30
   Prompt: Display connector support
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges

---

 CONFIG_DRM_PARADE_PS8640:

 Choose this option if you have PS8640 for display
 The PS8640 is a high-performance and low-power
 MIPI DSI to eDP converter

 Symbol: DRM_PARADE_PS8640 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:78
   Prompt: Parade PS8640 MIPI DSI to eDP Converter
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && DRM_MIPI_DSI [=n] && DRM_PANEL [=y]

---

 CONFIG_DRM_SIMPLE_BRIDGE:

 Support for non-programmable DRM bridges, such as ADI ADV7123, TI
 THS8134 and THS8135 or passive resistor ladder DACs.

 Symbol: DRM_SIMPLE_BRIDGE [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:116
   Prompt: Simple DRM bridge support
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m]

---

 CONFIG_DRM_TIDSS:

 The TI Keystone family SoCs introduced a new generation of
 Display SubSystem. There is currently three Keystone family
 SoCs released with DSS. Each with somewhat different version
 of it. The SoCs are 66AK2Gx, AM65x, and J721E. Set this to Y
 or M to add display support for TI Keystone family
 platforms.

 Symbol: DRM_TIDSS [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/tidss/Kconfig:1
   Prompt: DRM Support for TI Keystone
   Depends on: HAS_IOMEM [=y] && DRM [=m] && OF [=y] && (ARM || ARM64 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> Graphics support
 Selects: DRM_KMS_HELPER [=m] && DRM_KMS_CMA_HELPER [=n] && DRM_GEM_CMA_HELPER [=n]

---

 CONFIG_DRM_TI_TPD12S015:

 Texas Instruments TPD12S015 HDMI level shifter and ESD protection
 driver.

 Symbol: DRM_TI_TPD12S015 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:175
   Prompt: TI TPD12S015 HDMI level shifter and ESD protection
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m]

---

 CONFIG_DRM_TOSHIBA_TC358768:

 Toshiba TC358768AXBG/TC358778XBG DSI bridge chip driver.

 Symbol: DRM_TOSHIBA_TC358768 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:148
   Prompt: Toshiba TC358768 MIPI DSI bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]

---

 CONFIG_TINYDRM_ILI9486:

 DRM driver for the following Ilitek ILI9486 panels:
 * PISCREEN 3.5" 320x480 TFT (Ozzmaker 3.5")
 * RPILCD 3.5" 320x480 TFT (Waveshare 3.5")

 If M is selected the module will be called ili9486.

 Symbol: TINYDRM_ILI9486 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/tiny/Kconfig:50
   Prompt: DRM support for ILI9486 display panels
   Depends on: HAS_IOMEM [=y] && DRM [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Graphics support
 Selects: DRM_KMS_HELPER [=m] && DRM_KMS_CMA_HELPER [=n] && DRM_MIPI_DBI [=n] && BACKLIGHT_CLASS_DEVICE [=y]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
2021-08-30 10:50:05 -04:00
Jeremy Cline 92c44c45c3 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_AXI_FAN_CONTROL:

 If you say yes here you get support for the Analog Devices
 AXI HDL FAN monitoring core.

 This driver can also be built as a module. If so, the module
 will be called axi-fan-control

 Symbol: SENSORS_AXI_FAN_CONTROL [=n]
 Type  : tristate
 Defined at drivers/hwmon/Kconfig:283
   Prompt: Analog Devices FAN Control HDL Core driver
   Depends on: HWMON [=y]
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])

---

Cc: Dean Nelson <dnelson@redhat.com>
2021-08-30 10:50:05 -04:00
Jeremy Cline eda398bc51 [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AD5770R:

 Say yes here to build support for Analog Devices AD5770R Digital to
 Analog Converter.

 To compile this driver as a module, choose M here: the
 module will be called ad5770r.

 Symbol: AD5770R [=n]
 Type  : tristate
 Defined at drivers/iio/dac/Kconfig:191
   Prompt: Analog Devices AD5770R IDAC driver
   Depends on: IIO [=m] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Digital to analog converters

---

 CONFIG_AL3010:

 Say Y here if you want to build a driver for the Dyna Image AL3010
 ambient light sensor.

 To compile this driver as a module, choose M here: the
 module will be called al3010.

 Symbol: AL3010 [=n]
 Type  : tristate
 Defined at drivers/iio/light/Kconfig:46
   Prompt: AL3010 ambient light sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Light sensors

---

 CONFIG_GP2AP002:

 Say Y here if you have a Sharp GP2AP002 proximity/ALS combo-chip
 hooked to an I2C bus.

 To compile this driver as a module, choose M here: the
 module will be called gp2ap002.

 Symbol: GP2AP002 [=n]
 Type  : tristate
 Defined at drivers/iio/light/Kconfig:172
   Prompt: Sharp GP2AP002 Proximity/ALS sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Light sensors
 Selects: REGMAP [=y]

---

 CONFIG_HMC425:

 Say yes here to build support for Analog Devices HMC425A and similar
 gain amplifiers or step attenuators.

 To compile this driver as a module, choose M here: the
 module will be called hmc425a.

 Symbol: HMC425 [=n]
 Type  : tristate
 Defined at drivers/iio/amplifiers/Kconfig:25
   Prompt: Analog Devices HMC425A and similar GPIO Gain Amplifiers
   Depends on: IIO [=m] && GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Amplifiers

---

 CONFIG_ICP10100:

 Say yes here to build support for InvenSense ICP-101xx barometric
 pressure and temperature sensor.

 To compile this driver as a module, choose M here: the module
 will be called icp10100.

 Symbol: ICP10100 [=n]
 Type  : tristate
 Defined at drivers/iio/pressure/Kconfig:104
   Prompt: InvenSense ICP-101xx pressure and temperature sensor
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Pressure sensors
 Selects: CRC8 [=m]

---
2021-08-30 10:50:05 -04:00
Jeremy Cline 9804407671 [redhat] New configs in drivers/pci
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PCIE_EDR:

 This option adds Error Disconnect Recover support as specified
 in the Downstream Port Containment Related Enhancements ECN to
 the PCI Firmware Specification r3.2.  Enable this if you want to
 support hybrid DPC model which uses both firmware and OS to
 implement DPC.

 Symbol: PCIE_EDR [=n]
 Type  : bool
 Defined at drivers/pci/pcie/Kconfig:145
   Prompt: PCI Express Error Disconnect Recover support
   Depends on: PCI [=y] && PCIE_DPC [=y] && ACPI [=y]
   Location:
     -> Device Drivers
       -> PCI support (PCI [=y])

Enabled at the request of Myron Stowe.

---

 CONFIG_PCIE_LAYERSCAPE_GEN4:

 Say Y here if you want PCIe Gen4 controller support on
 Layerscape SoCs.
 Symbol: PCIE_LAYERSCAPE_GEN4 [=n]
 Type  : bool
 Defined at drivers/pci/controller/mobiveil/Kconfig:25
   Prompt: Freescale Layerscape PCIe Gen4 controller
   Depends on: PCI [=y] && OF [=y] && (ARM64 [=y] || ARCH_LAYERSCAPE [=n]) && PCI_MSI_IRQ_DOMAIN [=y]
   Location:
     -> Device Drivers
       -> PCI support (PCI [=y])
         -> PCI controller drivers
           -> Mobiveil PCIe Core Support
 Selects: PCIE_MOBIVEIL_HOST [=n]

---

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:04 -04:00
Jeremy Cline cafb122a6a [redhat] New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_IPQ6018:

 This is the pinctrl, pinmux, pinconf and gpiolib driver for
 the Qualcomm Technologies Inc. TLMM block found on the
 Qualcomm Technologies Inc. IPQ6018 platform. Select this for
 IPQ6018.

 Symbol: PINCTRL_IPQ6018 [=n]
 Type  : tristate
 Defined at drivers/pinctrl/qcom/Kconfig:53
   Prompt: Qualcomm Technologies, Inc. IPQ6018 pin controller driver
   Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINCTRL_MSM [=y]

---
2021-08-30 10:50:04 -04:00
Jeremy Cline 5214672b64 [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SURFACE_3_POWER_OPREGION:

 This driver provides support for ACPI operation
 region of the Surface 3 battery platform driver.

 Symbol: SURFACE_3_POWER_OPREGION [=n]
 Type  : tristate
 Defined at drivers/platform/x86/Kconfig:858
   Prompt: Surface 3 battery platform operation region support
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])

---
2021-08-30 10:50:04 -04:00
Jeremy Cline 88f427b6eb [redhat] New configs in drivers/ptp
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PTP_1588_CLOCK_IDT82P33:

 This driver adds support for using the IDT 82P33xxx as a PTP
 clock. This clock is only useful if your time stamping MAC
 is connected to the IDT chip.

 To compile this driver as a module, choose M here: the module
 will be called ptp_idt82p33.

 Symbol: PTP_1588_CLOCK_IDT82P33 [=n]
 Type  : tristate
 Defined at drivers/ptp/Kconfig:118
   Prompt: IDT 82P33xxx PTP clock
   Depends on: PTP_1588_CLOCK [=y] && I2C [=y]
   Location:
     -> Device Drivers
       -> PTP clock support

---

 CONFIG_PTP_1588_CLOCK_VMW:

 This driver adds support for using VMware virtual precision
 clock device as a PTP clock. This is only useful in virtual
 machines running on VMware virtual infrastructure.

 To compile this driver as a module, choose M here: the module
 will be called ptp_vmw.

 Symbol: PTP_1588_CLOCK_VMW [=n]
 Type  : tristate
 Defined at drivers/ptp/Kconfig:142
   Prompt: VMware virtual PTP clock
   Depends on: ACPI [=y] && HYPERVISOR_GUEST [=y] && X86 [=y] && PTP_1588_CLOCK [=y]
   Location:
     -> Device Drivers
       -> PTP clock support

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:50:04 -04:00
Jeremy Cline 7eff3d588f [redhat] New configs in drivers/spi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SPI_MUX:

 This adds support for SPI multiplexers. Each SPI mux will be
 accessible as a SPI controller, the devices behind the mux will appear
 to be chip selects on this controller. It is still necessary to
 select one or more specific mux-controller drivers.

 Symbol: SPI_MUX [=n]
 Type  : tristate
 Defined at drivers/spi/Kconfig:919
   Prompt: SPI multiplexer support
   Depends on: SPI [=y] && SPI_MASTER [=y]
   Location:
     -> Device Drivers
       -> SPI support (SPI [=y])
 Selects: MULTIPLEXER [=n]

---
2021-08-30 10:50:04 -04:00
Jeremy Cline 533320c022 [redhat] New configs in drivers/tty
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SERIAL_SPRD:

 This enables the driver for the Spreadtrum's serial.

 Symbol: SERIAL_SPRD [=n]
 Type  : tristate
 Defined at drivers/tty/serial/Kconfig:1443
   Prompt: Support for Spreadtrum serial
   Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Enable TTY (TTY [=y])
           -> Serial drivers
 Selects: SERIAL_CORE [=y]

---
2021-08-30 10:50:04 -04:00
Jeremy Cline f43478aa48 [redhat] New configs in drivers/usb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_APPLE_MFI_FASTCHARGE:

 Say Y here if you want to control whether iOS devices will
 fast charge from the USB interface, as implemented in "MFi"
 chargers.

 It is safe to say M here.

 Symbol: APPLE_MFI_FASTCHARGE [=n]
 Type  : tristate
 Defined at drivers/usb/misc/Kconfig:140
   Prompt: Fast charge control for iOS devices
   Depends on: USB_SUPPORT [=y] && USB [=y]
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
 Selects: POWER_SUPPLY [=y]

---

Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:03 -04:00
Jeremy Cline 264d37e6f9 [redhat] New configs in net/ipv6
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_IPV6_RPL_LWTUNNEL:

 Support for RFC6554 RPL Source Routing Header using the lightweight
 tunnels mechanism.

 If unsure, say N.

 Symbol: IPV6_RPL_LWTUNNEL [=n]
 Type  : bool
 Defined at net/ipv6/Kconfig:306
   Prompt: IPv6: RPL Source Routing Header support
   Depends on: NET [=y] && INET [=y] && IPV6 [=y]
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> TCP/IP networking (INET [=y])
           -> The IPv6 protocol (IPV6 [=y])
 Selects: LWTUNNEL [=y]

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
2021-08-30 10:50:03 -04:00
Jeremy Cline e5f584c7af [redhat] New configs in drivers/bus
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MHI_BUS:

 Bus driver for MHI protocol. Modem Host Interface (MHI) is a
 communication protocol used by the host processors to control
 and communicate with modem devices over a high speed peripheral
 bus or shared memory.

 Symbol: MHI_BUS [=n]
 Type  : tristate
 Defined at drivers/bus/mhi/Kconfig:8
   Prompt: Modem Host Interface (MHI) bus
   Location:
     -> Device Drivers
       -> Bus devices

---
2021-08-30 10:50:03 -04:00
Jeremy Cline 0f1cb91a42 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM64_AMU_EXTN:

 The activity monitors extension is an optional extension introduced
 by the ARMv8.4 CPU architecture. This enables support for version 1
 of the activity monitors architecture, AMUv1.

 To enable the use of this extension on CPUs that implement it, say Y.

 Note that for architectural reasons, firmware _must_ implement AMU
 support when running on CPUs that present the activity monitors
 extension. The required support is present in:
   * Version 1.5 and later of the ARM Trusted Firmware

 For kernels that have this configuration enabled but boot with broken
 firmware, you may need to say N here until the firmware is fixed.
 Otherwise you may experience firmware panics or lockups when
 accessing the counter registers. Even if you are not observing these
 symptoms, the values returned by the register reads might not
 correctly reflect reality. Most commonly, the value read will be 0,
 indicating that the counter is not enabled.

 Symbol: ARM64_AMU_EXTN [=y]
 Type  : bool
 Defined at arch/arm64/Kconfig:1557
   Prompt: Enable support for the Activity Monitors Unit CPU extension
   Location:
     -> Kernel Features
       -> ARMv8.4 architectural features

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
2021-08-30 10:50:03 -04:00
Jeremy Cline c0c157cc28 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_SOC_INTEL_BDW_RT5650_MACH:

 This adds the ASoC machine driver for Intel Broadwell platforms with
 the RT5650 codec.
 Say Y if you have such a device.
 If unsure select "N".

 Symbol: SND_SOC_INTEL_BDW_RT5650_MACH [=n]
 Type  : tristate
 Prompt: Broadwell with RT5650 codec
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
   Defined at sound/soc/intel/boards/Kconfig:47
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && (SND_SOC_INTEL_HASWELL [=m] || SND_SOC_SOF_BROADWELL [=n]) && I2C [=y] && (I2C_DESIGNWARE_PLATFORM [=m] || COMPILE_TEST [=n]) && (X86_INTEL_LPSS [=y] || COMPILE_TEST [=n])
   Selects: SND_SOC_RT5645 [=m]

This has been set to "m" at the request of Jaroslav Kysela.

---

 CONFIG_SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES:

 Some drivers report the I/O configuration to userspace through the
 soundcard's long card name in the control user space AP. An unfortunate
 side effect is that this long name may also be used by the GUI,
 confusing users with information they don't need.
 This option prevents the long name from being modified, and the I/O
 configuration will be provided through a different component interface.
 Select Y if userspace like UCM (Use Case Manager) uses the component
 interface.
 If unsure select N.

 Symbol: SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES [=n]
 Type  : bool
 Prompt: Use more user friendly long card names
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
   Defined at sound/soc/intel/boards/Kconfig:16
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y]

This has been set to "y" at the request of Jaroslav Kysela.

---

 CONFIG_SND_SOC_MT6660:

 MediaTek MT6660 is a smart power amplifier which contain
 speaker protection, multi-band DRC, equalizer functions.
 Select N if you don't have MT6660 on board.
 Select M to build this as module.

 Symbol: SND_SOC_MT6660 [=n]
 Type  : tristate
 Prompt: Mediatek MT6660 Speaker Amplifier
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> CODEC drivers
   Defined at sound/soc/codecs/Kconfig:1583
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
   Selected by [n]:
   - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n] && I2C [=y]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
2021-08-30 10:50:03 -04:00
Jeremy Cline 345e4ff498 [redhat] New configs in sound/core
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_CTL_VALIDATION:

 Say Y to enable the additional validation of each control element
 access, including sanity-checks like whether the values returned
 from the driver are in the proper ranges or the check of the invalid
 access at out-of-array areas.

 Symbol: SND_CTL_VALIDATION [=n]
 Type  : bool
 Prompt: Perform sanity-checks for each control element access
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> Debug (SND_DEBUG [=y])
   Defined at sound/core/Kconfig:181
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_DEBUG [=y]

---

This setting has been enabled on debug kernels at the request of
Jaroslav Kysela.

Cc: Jaroslav Kysela <jkysela@redhat.com>
2021-08-30 10:50:02 -04:00
Jeremy Cline adad8cd2af [redhat] New configs in drivers/tee
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AMDTEE:

 This implements AMD's Trusted Execution Environment (TEE) driver.

 Symbol: AMDTEE [=m]
 Type  : tristate
 Prompt: AMD-TEE
   Location:
     -> Device Drivers
       -> Trusted Execution Environment support (TEE [=m])
         -> TEE drivers
   Defined at drivers/tee/amdtee/Kconfig:3
   Depends on: TEE [=m] && CRYPTO_DEV_SP_PSP [=y]

This has been disabled at the request of Prarit Bhargava:
"Keep this off for now until we get some confidence that
AMDTEE doesn't lead to any corruption."
---

Cc: Herbert Xu <herbert.xu@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: darcari@redhat.com
2021-08-30 10:50:02 -04:00
Jeremy Cline acc734a73f [redhat] New configs in drivers/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HISI_DMA:

 Support HiSilicon Kunpeng DMA engine.

 Symbol: HISI_DMA [=n]
 Type  : tristate
 Prompt: HiSilicon DMA Engine support
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
   Defined at drivers/dma/Kconfig:242
   Depends on: DMADEVICES [=y] && (ARM64 [=y] || COMPILE_TEST [=n] && PCI_MSI [=y])
   Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=n]

---

 CONFIG_INTEL_IDXD:

 Enable support for the Intel(R) data accelerators present
 in Intel Xeon CPU.

 Say Y if you have such a platform.

 If unsure, say N.

 Symbol: INTEL_IDXD [=n]
 Type  : tristate
 Prompt: Intel Data Accelerators support
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
   Defined at drivers/dma/Kconfig:284
   Depends on: DMADEVICES [=y] && PCI [=y] && X86_64 [=y]
   Selects: DMA_ENGINE [=y] && SBITMAP [=y]

Enabled at the request of Prarit Bhargava <prarit@redhat.com>
---

 CONFIG_PLX_DMA:

 Some PLX ExpressLane PCI Switches support additional DMA engines.
 These are exposed via extra functions on the switch's
 upstream port. Each function exposes one DMA channel.

 Symbol: PLX_DMA [=n]
 Type  : tristate
 Prompt: PLX ExpressLane PEX Switch DMA Engine Support
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
   Defined at drivers/dma/Kconfig:521
   Depends on: DMADEVICES [=y] && PCI [=y]
   Selects: DMA_ENGINE [=y]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
2021-08-30 10:50:02 -04:00
Jeremy Cline b055b7aeb5 Add a script to test if all commits are signed off
Add a CI job to assert every commit in a merge request contains a
signed-off-by tag from the commit author. This is intended to be used
with GitLab's CI. An example job definition would be something like

signed_off_by:
  before_script:
    - pip install --user python-gitlab
  script: ./redhat/scripts/ci/sign_off_check.py
  only:
    refs:
      - merge_requests

Cc: Marcelo Ricardo Leitner <mleitner@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:02 -04:00
Don Zickus 5680bc55d0 Fix make rh-configs-arch
Once upon a time redhat/configs/build_configs.sh was modified to handle another
kernel version release parameter. But redhat/Makefile::rh-configs-arch was
not updated to reflect that.

Later after that change a different approach was taken.  build_configs.sh
does not utilize the KVERREL param no more.  I beleive generate_all_configs.sh
was modified to handle that use case.  This makes the KVERREL param useless
now.

Just remove the param and let 'make rh-configs-arch' work again.

Closes #23

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:02 -04:00
Jeremy Cline d39343fdd6 Drop RH_FEDORA in favor of the now-merged RHEL_DIFFERENCES
RH_FEDORA got introduced to differentiate between Fedora and RHEL. Now
the that the PCI patches finally got merged, we can exchange it for the
RHEL_DIFFERENCES setting that came along with them.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:02 -04:00
Jeremy Cline 5a64dab1d4 [redhat] Add a script to automatically rebase ark-patches
This script rebases the ark-patches against the latest master branch. If
patches cannot be rebased, issues are filed in the GitLab issue tracker.

This script is really only intended to be run in CI on a regular
schedule (nightly, most likely). A sample .gitlab-ci.yml would be:

ark_patches_rebase:
  script:
    - dnf -y install python3-gitlab
    - git config user.name "CKI@GitLab"
    - git config user.email "cki-project@redhat.com"
    - redhat/scripts/ci/ark-rebase-patches.sh "master" $CI_PROJECT_ID
    - git push -f origin ark-patches

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:01 -04:00
Jeremy Cline d441da0160 [redhat] Adjust existing configs for new upstream deps
CONFIG_STRICT_DEVMEM, CONFIG_NODES_SHIFT, and
CONFIG_CPU_FREQ_GOV_SCHEDUTIL all change from their current settings
during the build. Add the configuration they change to into pending for
review.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:01 -04:00
Jeremy Cline de288b8149 [redhat] AUTOMATIC: New configs 2021-08-30 10:50:01 -04:00
Jeremy Cline 5bc35bdf3b Sync up Fedora configs from the first week of the merge window
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:01 -04:00
Don Zickus 2d7e00adca Migrate blacklisting floppy.ko to mod-blacklist.sh
Leftover chunk wasn't included in the initial RHEL blacklist changes.
Convert the final piece.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:50:01 -04:00
Don Zickus 0d5cc92e5a kernel packaging: Combine mod-blacklist.sh and mod-extra-blacklist.sh
commit 6f5cea3de2f10788f05e7f6cb70bb4cca8865b35
Author: Prarit Bhargava <prarit@redhat.com>
Date:   Fri Jun 7 18:00:38 2019 -0400

    [redhat] kernel packaging: Combine mod-blacklist.sh and mod-extra-blacklist.sh

    Message-id: <20190607180038.20685-5-prarit@redhat.com>
    Patchwork-id: 263189
    O-Subject: [RHEL8.1 BZ 1699868 v4 4/4] kernel packaging: Combine mod-blacklist.sh and mod-extra-blacklist.sh
    Bugzilla: 1699868
    RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
    RH-Acked-by: Laura Abbott <labbott@redhat.com>

    Bugzilla: http://bugzilla.redhat.com/1699868

    Combine mod-blacklist.sh and mod-extra-blacklist.sh.  The two scripts
    take the same arguments and are called after one another.

    v4: Fix cat usage in spec file and scripts (jbenc).
    Signed-off-by: Prarit Bhargava <prarit@redhat.com>

    Cc: Herton R. Krzesinski <herton@redhat.com>
    Cc: Jiri Benc <jbenc@redhat.com>
    Cc: Don Zickus <dzickus@redhat.com>
    Cc: Prarit Bhargava <prarit@redhat.com>
    Cc: Philipp Rudo <prudo@redhat.com>
    Cc: Ivan Vecera <ivecera@redhat.com>
    Cc: Denys Vlasenko <dvlasenk@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>

NOTE: redhat/mod-extra.list is removed here because ARK uses that file
differently.  Instead update_scripts.sh is run to include mod-extras.list.rhel
and mod-extras.list.fedora.
2021-08-30 10:50:00 -04:00
Don Zickus a1f2410916 kernel packaging: Fix extra namespace collision
commit b2819ae00d4cd6380e1151dd0628f32e19a85d6f
Author: Prarit Bhargava <prarit@redhat.com>
Date:   Fri Jun 7 18:00:37 2019 -0400

    [rpmspec] kernel packaging: Fix extra namespace collision

    Message-id: <20190607180038.20685-4-prarit@redhat.com>
    Patchwork-id: 263188
    O-Subject: [RHEL8.1 BZ 1699868 v4 3/4] kernel packaging: Fix extra namespace collision
    Bugzilla: 1699868
    RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
    RH-Acked-by: Laura Abbott <labbott@redhat.com>

    Bugzilla: http://bugzilla.redhat.com/1699868

    The kernel-modules-extra package collides with the 3rd party driver
    location, /lib/modules/'uname -r'/extra.  When the kernel-modules-extra
    package has already been installed and a new kernel is installed, the
    result is a significant increase to the install time of a kernel and the
    wrong kernel modules being loaded into the new kernel.

    The /lib/modules/'uname -r'/extra directory is designated as a spot
    where 3rd party vendors can place their out-of-box drivers.  When a new
    kernel is installed (specifically the kernel-core package) a call is
    made to /usr/sbin/weak-modules (from the kmod package) to examine
    drivers in the previously installed kernels' extra directories to bring
    those drivers forward into the new kernel.

    The kernel-modules-extra package installs modules into the /extra
    directory.  As a result, when /usr/sbin/weak-modules is executed it
    brings the modules from kernel-modules-extra forward into the new kernel
    as well.  This is a critical mistake as the wrong modules have now been
    brought forward.  Additionally, /usr/sbin/weak-modules takes longer to
    execute every time a new kernel is installed.  After five kernels are
    installed the time to install the kernel-core package climbs to
    approximately 10 minutes.

    After some code investigation and discussion with the authors of the
    original Fedora code, and input from Herton, this can be avoided by
    installing the kernel-modules-extra modules to their original
    directories in 8.0.z.

    The existing build process copies all the modules into a temporary area
    called restore, and leaving the original modules directory as a work
    area.  The modules listed in mod-extra.list are copied to extra/ and
    removed from the work area, and core.list and modules.list files are
    created.  The restore area is then copied back, and the rpm build
    process continues.

    My changes create a mod-extra.list and a mod-internal.list (similar to
    core.list and modules.list), and remove the files from the work area so
    that the core.list and modules.list can be created.  The list files are
    used later on to create dynamic %files sections for the subpackages.

    Remove the /lib/modules/'uname -r'/extra installation path from
    the kernel-modules-extra package and install the modules in their
    original directories.

    v4: Make modules-internal.list and modules-extra.list use consistent (mleitner).
        Fix cat usage in spec file and scripts (jbenc).

    Signed-off-by: Prarit Bhargava <prarit@redhat.com>

    Cc: Herton R. Krzesinski <herton@redhat.com>
    Cc: Prarit Bhargava <prarit@redhat.com>
    Cc: Marcelo Leitner <mleitner@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 10:50:00 -04:00
Don Zickus 3dbca18c09 mod-extra.sh: Rename to mod-blacklist.sh
commit a211757c739c538c9219d14d7e33e15d43fe706e
Author: Prarit Bhargava <prarit@redhat.com>
Date:   Fri Jun 7 18:00:36 2019 -0400

    [redhat] mod-extra.sh: Rename to mod-blacklist.sh

    Message-id: <20190607180038.20685-3-prarit@redhat.com>
    Patchwork-id: 263191
    O-Subject: [RHEL8.1 BZ 1699868 v4 2/4] mod-extra.sh: Rename to mod-blacklist.sh
    Bugzilla: 1699868
    RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
    RH-Acked-by: Laura Abbott <labbott@redhat.com>

    Bugzilla: http://bugzilla.redhat.com/1699868

    Rename mod-extra.sh to mod-blacklist.sh.  There are no functional changes
    in this patch.

    v4: Fix "mdoules" typo (cera)

    Signed-off-by: Prarit Bhargava <prarit@redhat.com>

    Cc: Herton R. Krzesinski <herton@redhat.com>
    Cc: Jiri Benc <jbenc@redhat.com>
    Cc: Don Zickus <dzickus@redhat.com>
    Cc: Prarit Bhargava <prarit@redhat.com>
    Cc: Denys Vlasenko <dvlasenk@redhat.com>
    Cc: Philipp Rudo <prudo@redhat.com>
    Cc: Petr Oros <poros@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 10:50:00 -04:00
Don Zickus d78c83f2ce mod-extra.sh: Make file generic
commit 6cedee3e761d6cfb73cdb502542ab0ac22761618
Author: Prarit Bhargava <prarit@redhat.com>
Date:   Fri Jun 7 18:00:35 2019 -0400

    [redhat] mod-extra.sh: Make file generic
    
    Message-id: <20190607180038.20685-2-prarit@redhat.com>
    Patchwork-id: 263187
    O-Subject: [RHEL8.1 BZ 1699868 v4 1/4] mod-extra.sh: Make file generic
    Bugzilla: 1699868
    RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
    RH-Acked-by: Laura Abbott <labbott@redhat.com>
    
    Bugzilla: http://bugzilla.redhat.com/1699868
    
    Remove specific mentions of "extra" and make the destination directory the
    third argument.
    
    v4: Switch from chained command to if-then-else (jbenc)
    
    Signed-off-by: Prarit Bhargava <prarit@redhat.com>
    
    Cc: Herton R. Krzesinski <herton@redhat.com>
    Cc: Prarit Bhargava <prarit@redhat.com>
    Cc: Denys Vlasenko <dvlasenk@redhat.com>
    Cc: Ivan Vecera <ivecera@redhat.com>
    Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
2021-08-30 10:50:00 -04:00
Jeremy Cline 3d2e6ec810 Fix a painfully obvious YAML syntax error in .gitlab-ci.yml
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:50:00 -04:00
Don Zickus 647dbb1d36 Add in armv7hl kernel header support
Help bootstrap 32-bit arm effort for enterprise Fedora.
2021-08-30 10:50:00 -04:00
Don Zickus 967538b097 Disable all BuildKernel commands when only building headers
To build only armv7hl kernel headers, all the BuildKernel commands
need to be disabled.  The following macros were still set

with_pae
with_zfcpdump

Make sure they are disabled for nobuildarches.
2021-08-30 10:49:59 -04:00
Jeremy Cline 1b8c7d5d9d [redhat] Include .gitlab-ci.yml from kernel-ark-ci.
Due to our current odd branching strategy, the easiest way to maintain
the CI jobs is externally and including the external definition in each
branch. This way, users who fork the repository get the latest CI
definitions and we do not need to keep the two branches in sync.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:59 -04:00
Jeremy Cline cd220bb793 Drop any gitlab-ci patches from ark-patches
We export the set of patches we carry each time ark-patches is updated
so we can just download a patch bundle and apply it to any old tree.
However, we don't want to export the patches relating to gitlab-ci files
since the target in question might include this file (like, for example,
the internal branch of ARK). Strip any commits relating to gitlab-ci.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:59 -04:00
Jeremy Cline c69c89e4d6 Build the srpm for internal branch CI using the vanilla tree
We've got one oddball setting which we adjust the Kconfig default in a
patch in ark-patches. The setting is, therefore, invalid on vanilla
trees, which led to jumping through hoops to get the downstream patches
applied to the internal branch before testing.

This was painful because we needed to fetch the ark-patches branch to
some depth along with the master branch, figure out the merge base, and
yank all the patches out for application. It's more reasonable to just
set the one setting back to its upstream default and be careful about
further tweaks to Kconfigs in the downstream patch set.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:59 -04:00
Jeremy Cline f6e223d32f Pull in the latest ARM configurations for Fedora
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:59 -04:00
Neil Horman 76ee5e1237 Fix xz memory usage issue
The create-tarball.sh script can occasionally hang non 64 bit systems
due to extreeme memory usage.  Build farms will occasionally use older
32 bit systems to do arch independent work (like assembling
srpms/tarballs/etc), and when xz runs on those systems, it will, given a
sufficiently large input file, allocate more than the available 3G of
memory address space allocated to a user space process, causing swap
storms, and build failures due to resultant job timeouts.

Fix it by detecting if we are on a 64 bit arch or not, and setting the
xz memory usage limit accordingly

Signed-off-by: Neil Horman <nhorman@redhat.com>
2021-08-30 10:49:58 -04:00
Jeremy Cline b1981d5bcb [redhat] Use fedpkg instead of rhpkg when targeting Fedora
Fedora uses the fedpkg binary instead of rhpkg, so conditionally set
RHPKG_BIN based on the target.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:58 -04:00
Jeremy Cline b9240a70bf [redhat] If building for Fedora, default to the master branch
Rawhide in the Fedora dist-git is on the master branch, so use it by
default for the RHPRODUCT which is used to determine the dist-git branch
name.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:58 -04:00
Jeremy Cline 7b4a97dbda [redhat] Make Fedora Rawhide the default dist
With ARK and Fedora about to merge, make Fedora the default dist. ARK
will be built largely by automation, but Fedora will get a lot of
end-user usage, so default to what they'll likely want.

When ARK is forked, the default can be set to a sensible default for
RHEL 9.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:58 -04:00
Jeremy Cline 9379d2dd51 Use ark-latest instead of master for update script
We've switched master to track Linus's tree, so use the ark-latest
branch when updating the changelog in internal.  Also set -e so the next
time something changes the job fails.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:58 -04:00
Jeremy Cline 88bc0cb935 Move the CI jobs back into the ARK repository
Update the CI jobs with the latest definition from the external
repository, including jobs for the ark-patches tree and a job to export
the latest downstream patch set.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:58 -04:00
Jeremy Cline 96cefce1f1 Sync up ARK's Fedora config with the dist-git repository
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:57 -04:00
Jeremy Cline 3b59eeebca [redhat] New configs in kernel/trace
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BOOTTIME_TRACING:

 Enable developer to setup ftrace subsystem via supplemental
 kernel cmdline at boot time for debugging (tracing) driver
 initialization and boot process.

 Symbol: BOOTTIME_TRACING [=y]
 Type  : bool
 Defined at kernel/trace/Kconfig:144
   Prompt: Boot-time Tracing support
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && BOOT_CONFIG [=y] && TRACING [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])

---

 CONFIG_KPROBE_EVENTS_ON_NOTRACE:

 This is only for the developers who want to debug ftrace itself
 using kprobe events.

 If kprobes can use ftrace instead of breakpoint, ftrace related
 functions are protected from kprobe-events to prevent an infinit
 recursion or any unexpected execution path which leads to a kernel
 crash.

 This option disables such protection and allows you to put kprobe
 events on ftrace functions for debugging ftrace by itself.
 Note that this might let you shoot yourself in the foot.

 If unsure, say N.

 Symbol: KPROBE_EVENTS_ON_NOTRACE [=n]
 Type  : bool
 Defined at kernel/trace/Kconfig:550
   Prompt: Do NOT protect notrace function from kprobe events
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && KPROBE_EVENTS [=y] && KPROBES_ON_FTRACE [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])
         -> Enable kprobes-based dynamic events (KPROBE_EVENTS [=y])

---

 CONFIG_KPROBE_EVENT_GEN_TEST:

 This option creates a test module to check the base
 functionality of in-kernel kprobe event definition.

 To test, insert the module, and then check the trace buffer
 for the generated kprobe events.

 If unsure, say N.

 Symbol: KPROBE_EVENT_GEN_TEST [=n]
 Type  : tristate
 Defined at kernel/trace/Kconfig:839
   Prompt: Test module for in-kernel kprobe event generation
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && KPROBE_EVENTS [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])

Enabled for debugging kernels at the request of Jiri Olsa
---

 CONFIG_SYNTH_EVENT_GEN_TEST:

 This option creates a test module to check the base
 functionality of in-kernel synthetic event definition and
 generation.

 To test, insert the module, and then check the trace buffer
 for the generated sample events.

 If unsure, say N.

 Symbol: SYNTH_EVENT_GEN_TEST [=n]
 Type  : tristate
 Defined at kernel/trace/Kconfig:826
   Prompt: Test module for in-kernel synthetic event generation
   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && HIST_TRIGGERS [=y]
   Location:
     -> Kernel hacking
       -> Tracers (FTRACE [=y])

Enabled for debugging kernels at the request of Jiri Olsa
---

Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>
2021-08-30 10:49:57 -04:00
Jeremy Cline a9d00d64b9 [redhat] Sync ARK latest mod-extra-blacklist.sh with Fedora
Fedora includes a blacklist for the floppy driver[0]. Bring this into
ARK.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1789155

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:57 -04:00
Jeremy Cline 4a77339938 [redhat] Include Fedora's merge.pl script
Fedora includes a script in its dist-git that allows users to drop
config settings into the "kernel-local" file which is merged into the
final configuration. This is purely for users and is empty in the
dist-git tree so it has no effect.

A number of folks use this script, so in order to minimize the
disruption of ARK and Fedora this includes it and the associated
specfile changes.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:57 -04:00
Jeremy Cline 7d9cb9ac60 [redhat] Sync aarch64 audio configs
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:57 -04:00
Jeremy Cline 626da662b7 [redhat] Sync up the mod-extra list from Fedora
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:57 -04:00
Jeremy Cline 321678ad6c [redhat] AUTOMATIC: New configs 2021-08-30 10:49:56 -04:00
Jeremy Cline 4d104703a8 [redhat] Drop a number of configurations that are merged
The script that generates the configuration commits appears to have a
bug where it's not deleting the corresponding pending file when it moves
it to common/. This drops any configs already listed in common/ and I'll
track down the script bug later.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:56 -04:00
Jeremy Cline d231a57c71 [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INTEL_UNCORE_FREQ_CONTROL:

 This driver allows control of uncore frequency limits on
 supported server platforms.
 Uncore frequency controls RING/LLC (last-level cache) clocks.

 To compile this driver as a module, choose M here: the module
 will be called intel-uncore-frequency.

 Symbol: INTEL_UNCORE_FREQ_CONTROL [=n]
 Type  : tristate
 Prompt: Intel Uncore frequency control driver
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
   Defined at drivers/platform/x86/Kconfig:1339
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && X86_64 [=y]

Set to m at the request of Prarit.
---

Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:49:56 -04:00
Jeremy Cline 1488e4ca18 [redhat] Enable MPTCP_IPV6 on ARK
This configuration is is exposed by CONFIG_MPTCP which got enabled in
commit b42134757b, but due to a bug in the configuration setting
scripts, the pending configuration was never removed so MPTCP was not
actually on. Help text is:

config MPTCP_IPV6
    bool "MPTCP: IPv6 support for Multipath TCP"
    select IPV6
    default y

This commit enables MPTCP_IPV6 and removes the Fedora-specific config
for it.

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:56 -04:00
Jeremy Cline 2939c0c98f [redhat] Dynamically set the debugbuildsenabled variable
ARK builds weekly, always based of a tag in Linus's tree. Fedora Rawhide
kernels are built daily and the policy is to use the debug
configurations except for RC and final releases.

redhat/Makefile.common determines if HEAD's merge base is a tag, and if
is, SNAPSHOT is set to 0. If HEAD's merge base is not a tag, SNAPSHOT is
1. Invert this and use it to dynamically set the debugbuildsenabled
boolean in the specfile.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:56 -04:00
Jeremy Cline ed9419916a [redhat] Set CONFIG_BUILD_SALT to KVERREL
The build ID is used to link binaries and their debug info. Setting this
option will use the value in the calculation of the build id. This
aligns with Fedora which has been using it since July 2018.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:55 -04:00
Laura Abbott 78d8efe33e [redhat] Be smarter about getting rid of debuginfo
We've been doing a workaround of using a uuid for the build-id for
userspace binaries to let us get parallel debuginfo (the trick we
use for the kernel doesn't extend to userspace binaries). This
works but isn't ideal for reproducibility. Given we don't actually
care about this debuginfo, just remove it from the buildroot completely.

This is a back port of a patch in Fedora's kernel specfile.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:55 -04:00
Jeremy Cline c42ea97b88 [redhat] Include Fedora's HDR_ARCH_LIST
Fedora's HDR_ARCH_LIST differs from ARK since ARM is still a target, so
define the list conditionally.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:55 -04:00
Jeremy Cline 27abdf8ffd [redhat] Fedora has a build requirement on dwarves
If building in a Fedora buildroot, include a build dependency on
dwarves. This aligns with the current Fedora specfile.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:55 -04:00
Jeremy Cline 4e71e5a75c [redhat] Uncomment out the %define with_kabichk macro
It's re-defined as 0 directly below it anyway and this produces a noisy
warning. Fedora's spec has it uncommented as well so this decreases the
diff between the two.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:55 -04:00
Jeremy Cline 888c6bdf78 [redhat] Pull in a short-term fix for GCC 10 build failures
Builds in the Fedora buildroot fail with GCC 10. This adds -fcommon to
the build flags until upstream cleanly builds without it. This is
required to merge ARK with Fedora.

Cc: Don Zickus <dzickus@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:55 -04:00
Jeremy Cline c07a8bf594 Pull in the latest configuration changes from Fedora
Update for the latest changes in Fedora's dist-git. Enables
BACKLIGHT_LED as a module and a number of ARM sound config options.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:54 -04:00
Jeremy Cline a63f00370c [redhat] New configs in drivers/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PHY_INTEL_EMMC:

 Enable this to support the Intel EMMC PHY

 Symbol: PHY_INTEL_EMMC [=n]
 Type  : tristate
 Defined at drivers/phy/intel/Kconfig:5
   Prompt: Intel EMMC PHY driver
   Location:
     -> Device Drivers
       -> PHY Subsystem
 Selects: GENERIC_PHY [=n]

---
2021-08-30 10:49:54 -04:00
Jeremy Cline 7a67d8f236 [redhat] New configs in drivers/mfd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MFD_ROHM_BD71828:

 Select this option to get support for the ROHM BD71828 Power
 Management IC. BD71828GW is a single-chip power management IC for
 battery-powered portable devices. The IC integrates 7 buck
 converters, 7 LDOs, and a 1500 mA single-cell linear charger.
 Also included is a Coulomb counter, a real-time clock (RTC), and
 a 32.768 kHz clock gate.

 Symbol: MFD_ROHM_BD71828 [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:1910
   Prompt: ROHM BD71828 Power Management IC
   Depends on: HAS_IOMEM [=y] && I2C [=y]=y && OF [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: REGMAP_I2C [=m] && REGMAP_IRQ [=n] && MFD_CORE [=m]

---
2021-08-30 10:49:54 -04:00
Jeremy Cline 285049f1c2 [redhat] New configs in net/sched
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NET_SCH_ETS:

 The Enhanced Transmission Selection scheduler is a classful
 queuing discipline that merges functionality of PRIO and DRR
 qdiscs in one scheduler. ETS makes it easy to configure a set of
 strict and bandwidth-sharing bands to implement the transmission
 selection described in 802.1Qaz.

 Say Y here if you want to use the ETS packet scheduling
 algorithm.

 To compile this driver as a module, choose M here: the module
 will be called sch_ets.

 If unsure, say N.

 Symbol: NET_SCH_ETS [=n]
 Type  : tristate
 Prompt: Enhanced transmission selection scheduler (ETS)
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> QoS and/or fair queueing (NET_SCHED [=y])
   Defined at net/sched/Kconfig:425
   Depends on: NET [=y] && NET_SCHED [=y]

This has been enabled as module at the request of Jiri Benc and Marcelo
Ricardo Leitner
---

 CONFIG_NET_SCH_FQ_PIE:

 Say Y here if you want to use the Flow Queue Proportional Integral
 controller Enhanced (FQ-PIE) packet scheduling algorithm.
 For more information, please see https://tools.ietf.org/html/rfc8033

 To compile this driver as a module, choose M here: the module
 will be called sch_fq_pie.

 If unsure, say N.

 Symbol: NET_SCH_FQ_PIE [=n]
 Type  : tristate
 Prompt: Flow Queue Proportional Integral controller Enhanced (FQ-PIE)
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> QoS and/or fair queueing (NET_SCHED [=y])
           -> Proportional Integral controller Enhanced (PIE) scheduler (NET_SCH_PIE [=m])
   Defined at net/sched/Kconfig:369
   Depends on: NET [=y] && NET_SCHED [=y] && NET_SCH_PIE [=m]

This has been disabled at the request of Jiri Benc
---

Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
2021-08-30 10:49:54 -04:00
Jeremy Cline a641693eb7 [redhat] New configs in drivers/iommu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM_SMMU_LEGACY_DT_BINDINGS:

 Support for the badly designed and deprecated "mmu-masters"
 devicetree bindings. This allows some DMA masters to attach
 to the SMMU but does not provide any support via the DMA API.
 If you're lucky, you might be able to get VFIO up and running.

 If you say Y here then you'll make me very sad. Instead, say N
 and move your firmware to the utopian future that was 2016.

 Symbol: ARM_SMMU_LEGACY_DT_BINDINGS [=n]
 Type  : bool
 Defined at drivers/iommu/Kconfig:384
   Prompt: Support the legacy "mmu-masters" devicetree bindings
   Depends on: IOMMU_SUPPORT [=y] && ARM_SMMU [=y]=y && OF [=y]
   Location:
     -> Device Drivers
       -> IOMMU Hardware Support (IOMMU_SUPPORT [=y])
         -> ARM Ltd. System MMU (SMMU) Support (ARM_SMMU [=y])

---

 CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON:

 Selecting this option will enable by default the scalable mode if
 hardware presents the capability. The scalable mode is defined in
 VT-d 3.0. The scalable mode capability could be checked by reading
 /sys/devices/virtual/iommu/dmar*/intel-iommu/ecap. If this option
 is not selected, scalable mode support could also be enabled by
 passing intel_iommu=sm_on to the kernel. If not sure, please use
 the default value.

 Symbol: INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON [=n]
 Type  : bool
 Defined at drivers/iommu/Kconfig:252
   Prompt: Enable Intel IOMMU scalable mode by default
   Depends on: IOMMU_SUPPORT [=y] && INTEL_IOMMU [=y]
   Location:
     -> Device Drivers
       -> IOMMU Hardware Support (IOMMU_SUPPORT [=y])
         -> Support for Intel IOMMU using DMA Remapping Devices (INTEL_IOMMU [=y])

---

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>
Cc: Don Dutile <ddutile@redhat.com>
2021-08-30 10:49:54 -04:00
Jeremy Cline 6b015e0cbd [redhat] New configs in fs/nfsd
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NFSD_V4_2_INTER_SSC:

 This option enables support for NFSv4.2 inter server to
 server copy where the destination server calls the NFSv4.2
 client to read the data to copy from the source server.

 If unsure, say N.

 Symbol: NFSD_V4_2_INTER_SSC [=n]
 Type  : bool
 Defined at fs/nfsd/Kconfig:137
   Prompt: NFSv4.2 inter server to server COPY
   Depends on: NETWORK_FILESYSTEMS [=y] && NFSD_V4 [=y] && NFS_V4_1 [=y] && NFS_V4_2 [=y]
   Location:
     -> File systems
       -> Network File Systems (NETWORK_FILESYSTEMS [=y])

---

Cc: Red Hat NFS Team <nfs-team@redhat.com>
2021-08-30 10:49:53 -04:00
Marcelo Ricardo Leitner bfee0ef9a2 configs: enable CONFIG_NET_SCH_CBS
It was requested on RHEL7 [0], to be enabled on RHEL8, so enable it on
ARK as well.

0.https://bugzilla.redhat.com/show_bug.cgi?id=1642506

Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
2021-08-30 10:49:53 -04:00
Jeremy Cline 6ebe8f3d7e [redhat] New configs in drivers/clocksource
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MICROCHIP_PIT64B:

 This option enables Microchip PIT64B timer for Atmel
 based system. It supports the oneshot, the periodic
 modes and high resolution. It is used as a clocksource
 and a clockevent.

 Symbol: MICROCHIP_PIT64B [=n]
 Type  : bool
 Prompt: Microchip PIT64B support
   Location:
     -> Device Drivers
       -> Clock Source drivers
   Defined at drivers/clocksource/Kconfig:700
   Depends on: GENERIC_CLOCKEVENTS [=y] && (OF [=y] || COMPILE_TEST [=n])
   Selects: CLKSRC_MMIO [=n]

---
2021-08-30 10:49:53 -04:00
Jeremy Cline 54dc030373 [redhat] New configs in net/ipv4
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_INET_ESPINTCP:

 Support for RFC 8229 encapsulation of ESP and IKE over
 TCP/IPv4 sockets.

 If unsure, say N.

 Symbol: INET_ESPINTCP [=n]
 Type  : bool
 Prompt: IP: ESP in TCP encapsulation (RFC 8229)
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> TCP/IP networking (INET [=y])
           -> IP: ESP transformation (INET_ESP [=m])
   Defined at net/ipv4/Kconfig:381
   Depends on: NET [=y] && INET [=y] && XFRM [=y] && INET_ESP [=m]
   Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y]

This has been enabled at the request of Marcelo Ricardo Leitner
<mleitner@redhat.com>
---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
2021-08-30 10:49:53 -04:00
Jeremy Cline 034aa87228 [redhat] New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TIME_NS:

 In this namespace boottime and monotonic clocks can be set.
 The time will keep going with the same pace.

 Symbol: TIME_NS [=y]
 Type  : bool
 Prompt: TIME namespace
   Location:
     -> General setup
       -> Namespaces support (NAMESPACES [=y])
   Defined at init/Kconfig:1084
   Depends on: NAMESPACES [=y] && GENERIC_VDSO_TIME_NS [=y]

---
2021-08-30 10:49:53 -04:00
Jeremy Cline 3909eda96d [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_GPIO_SIFIVE:

 Say yes here to support the GPIO device on SiFive SoCs.

 Symbol: GPIO_SIFIVE [=n]
 Type  : bool
 Prompt: SiFive GPIO support
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> Memory mapped GPIO drivers
   Defined at drivers/gpio/Kconfig:482
   Depends on: GPIOLIB [=y] && HAS_IOMEM [=y] && OF_GPIO [=y] && IRQ_DOMAIN_HIERARCHY [=y]
   Selects: GPIO_GENERIC [=n] && GPIOLIB_IRQCHIP [=y] && REGMAP_MMIO [=n]

---
2021-08-30 10:49:53 -04:00
Jeremy Cline b237937077 [redhat] New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EFI_DISABLE_PCI_DMA:

 Disable the busmaster bit in the control register on all PCI bridges
 while calling ExitBootServices() and passing control to the runtime
 kernel. System firmware may configure the IOMMU to prevent malicious
 PCI devices from being able to attack the OS via DMA. However, since
 firmware can't guarantee that the OS is IOMMU-aware, it will tear
 down IOMMU configuration when ExitBootServices() is called. This
 leaves a window between where a hostile device could still cause
 damage before Linux configures the IOMMU again.

 If you say Y here, the EFI stub will clear the busmaster bit on all
 PCI bridges before ExitBootServices() is called. This will prevent
 any malicious PCI devices from being able to perform DMA until the
 kernel reenables busmastering after configuring the IOMMU.

 This option will cause failures with some poorly behaved hardware
 and should not be enabled without testing. The kernel commandline
 options "efi=disable_early_pci_dma" or "efi=no_disable_early_pci_dma"
 may be used to override this option.

 Symbol: EFI_DISABLE_PCI_DMA [=n]
 Type  : bool
 Prompt: Clear Busmaster bit on PCI bridges during ExitBootServices()
   Location:
     -> Firmware Drivers
       -> EFI (Extensible Firmware Interface) Support
   Defined at drivers/firmware/efi/Kconfig:218
   Depends on: EFI [=y]

---
2021-08-30 10:49:52 -04:00
Jeremy Cline d023855fb1 [redhat] New configs in fs/nfs
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NFS_DISABLE_UDP_SUPPORT:

 Choose Y here to disable the use of NFS over UDP. NFS over UDP
 on modern networks (1Gb+) can lead to data corruption caused by
 fragmentation during high loads.

 Symbol: NFS_DISABLE_UDP_SUPPORT [=y]
 Type  : bool
 Defined at fs/nfs/Kconfig:200
   Prompt: NFS: Disable NFS UDP protocol support
   Depends on: NETWORK_FILESYSTEMS [=y] && NFS_FS [=m]
   Location:
     -> File systems
       -> Network File Systems (NETWORK_FILESYSTEMS [=y])

---

At the request of Benjamin Coddington, this has been disabled pending
the NFS team's decision on whether or not to support UDP in the future.

Cc: Red Hat NFS Team <nfs-team@redhat.com>
2021-08-30 10:49:52 -04:00
Jeremy Cline b573ab3eb2 Drop configuration options in fedora/ that no longer exist
Configuration options come and go, and these have all gone as of
v5.6-rc2. Drop them from the configuration tree. In addition to being
tidy, this helps minimize the difference between the ARK configuration
tree and Fedora's dist-git.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:52 -04:00
Jeremy Cline b2ece4b107 [redhat] Sync up ARK's Fedora config tree with Fedora's dist-git
Pull in the v5.6-rc1 configuration changes in preparation for merging
with Fedora.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:52 -04:00
Jeremy Cline 1e89982bab Set RH_FEDORA for ARK and Fedora 2021-08-30 10:49:52 -04:00
Jeremy Cline 9f4d340367 [redhat] Sync up Fedora module filter rules
Fedora's module filter has changed, so sync up the filters before the
ARK/Fedora merge.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:51 -04:00
Jeremy Cline 8d54df13db [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DRM_ANALOGIX_ANX6345:

 ANX6345 is an ultra-low Full-HD DisplayPort/eDP
 transmitter designed for portable devices. The
 ANX6345 transforms the LVTTL RGB output of an
 application processor to eDP or DisplayPort.

 Symbol: DRM_ANALOGIX_ANX6345 [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/analogix/Kconfig:2
   Prompt: Analogix ANX6345 bridge
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_ANALOGIX_DP [=n] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]

---

 CONFIG_DRM_LVDS_CODEC:

 Support for transparent LVDS encoders and decoders that don't
 require any configuration.

 Symbol: DRM_LVDS_CODEC [=n]
 Type  : tristate
 Defined at drivers/gpu/drm/bridge/Kconfig:38
   Prompt: Transparent LVDS encoders and decoders support
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Interface Bridges
 Selects: DRM_KMS_HELPER [=m] && DRM_PANEL_BRIDGE [=y]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
2021-08-30 10:49:51 -04:00
Jeremy Cline cf48990fe6 redhat/kernel.spec: Include the release in the kernel COPYING file
Whenever upstream changes the COPYING file it leads to an RPM file
conflict because the name is set to, for example, 5.6.0 for the whole
release cycle, but multiple kernel packages need to be installed that
reference that same file. This rarely happens, but it's annoying and the
file is tiny so just have one per installed kernel.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:51 -04:00
Jeremy Cline e3f056de5e [redhat] New configs in drivers/thunderbolt
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_USB4:

 USB4 and Thunderbolt driver. USB4 is the public speficiation
 based on Thunderbolt 3 protocol. This driver is required if
 you want to hotplug Thunderbolt and USB4 compliant devices on
 Apple hardware or on PCs with Intel Falcon Ridge or newer.

 To compile this driver a module, choose M here. The module will be
 called thunderbolt.

 Symbol: USB4 [=n]
 Type  : tristate
 Defined at drivers/thunderbolt/Kconfig:2
   Prompt: Unified support for USB4 and Thunderbolt
   Depends on: PCI [=y] && (X86 [=y] || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
 Selects: APPLE_PROPERTIES [=n] && CRC32 [=y] && CRYPTO [=y] && CRYPTO_HASH [=y] && NVMEM [=y]

---

Jarod requested that CONFIG_USB4=y since it's a direct replacement for
CONFIG_THUNDERBOLT which is currently y. This has exposed a further
configuration:

 CONFIG_USB4_NET:

 Select this if you want to create network between two computers
 over a USB4 and Thunderbolt cables. The driver supports Apple
 ThunderboltIP protocol and allows communication with any host
 supporting the same protocol including Windows and macOS.

 To compile this driver a module, choose M here. The module will be
 called thunderbolt-net.

 Symbol: USB4_NET [=n]
 Type  : tristate
 Defined at drivers/net/Kconfig:535
   Prompt: Networking over USB4 and Thunderbolt cables
   Depends on: NETDEVICES [=y] && USB4 [=m] && INET [=y]
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])

---

USB4_NET is a replacement for THUNDERBOLT_NET and its setting reflects
that.

Cc: Jarod Wilson <jarod@redhat.com>
2021-08-30 10:49:51 -04:00
Jeremy Cline decdc6fcc4 [redhat] New configs in sound/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SND_SOC_ADAU7118_HW:

 Enable support for the Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM
 Converter. In this mode, the device works in standalone mode which
 means that there is no bus to comunicate with it. Stereo mode is not
 supported in this mode.

 To compile this driver as a module, choose M here: the module
 will be called snd-soc-adau7118-hw.

 Symbol: SND_SOC_ADAU7118_HW [=n]
 Type  : tristate
 Prompt: Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM Converter - HW Mode
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> CODEC drivers
   Defined at sound/soc/codecs/Kconfig:405
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
   Selects: SND_SOC_ADAU7118 [=n]
   Selected by [n]:
   - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n]

---

 CONFIG_SND_SOC_ADAU7118_I2C:

 Enable support for the Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM
 Converter over I2C. This gives full support over the device.

 To compile this driver as a module, choose M here: the module
 will be called snd-soc-adau7118-i2c.

 Symbol: SND_SOC_ADAU7118_I2C [=n]
 Type  : tristate
 Prompt: Analog Devices ADAU7118 8 Channel PDM-to-I2S/TDM Converter - I2C
   Location:
     -> Device Drivers
       -> Sound card support (SOUND [=m])
         -> Advanced Linux Sound Architecture (SND [=m])
           -> ALSA for SoC audio support (SND_SOC [=m])
             -> CODEC drivers
   Defined at sound/soc/codecs/Kconfig:417
   Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && I2C [=y]
   Selects: SND_SOC_ADAU7118 [=n] && REGMAP_I2C [=y]
   Selected by [n]:
   - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n] && I2C [=y]

---

Cc: Jaroslav Kysela <jkysela@redhat.com>
2021-08-30 10:49:51 -04:00
Jeremy Cline 4c5ec91e44 [redhat] New configs in drivers/tty
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SERIAL_8250_16550A_VARIANTS:

 The 8250 driver can probe for many variants of the venerable 16550A
 serial port. Doing so takes additional time at boot.

 On modern systems, especially those using serial only for a simple
 console, you can say N here.

 Symbol: SERIAL_8250_16550A_VARIANTS [=n]
 Type  : bool
 Defined at drivers/tty/serial/8250/Kconfig:63
   Prompt: Support for variants of the 16550A serial port
   Depends on: TTY [=y] && HAS_IOMEM [=y] && SERIAL_8250 [=y]
   Location:
     -> Device Drivers
       -> Character devices
         -> Serial drivers
           -> 8250/16550 and compatible serial support (SERIAL_8250 [=y])

---

Prarit Bhargava requested that this be enabled: "Enabling this will make
virt systems boot faster.  We want this to be enabled for RHEL"

Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:49:51 -04:00
Jeremy Cline f273731907 redhat/kernel.spec: add scripts/jobserver-exec to py3_shbang_opts list
scripts/jobserver-exec is used in the documentation Makefile and
needs to be mangled to use Python 3 explicitly.

Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:50 -04:00
Jeremy Cline 1cf7440307 redhat/kernel.spec: package bpftool-gen man page
A new manual page, bpftool-gen, is being built as of v5.6-rc1. Include
it with bpftool.

Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:50 -04:00
Jeremy Cline e0ac8dab07 [redhat] New configs in mm/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PTDUMP_DEBUGFS:

 Say Y here if you want to show the kernel pagetable layout in a
 debugfs file. This information is only useful for kernel developers
 who are working in architecture specific areas of the kernel.
 It is probably not a good idea to enable this feature in a production
 kernel.

 If in doubt, say N.

 Symbol: PTDUMP_DEBUGFS [=n]
 Type  : bool
 Defined at mm/Kconfig.debug:127
   Prompt: Export kernel pagetable layout to userspace via debugfs
   Depends on: DEBUG_KERNEL [=y] && DEBUG_FS [=y] && GENERIC_PTDUMP [=y]
   Location:
     -> Kernel hacking
       -> Memory Debugging
 Selects: PTDUMP_CORE [=y]

---

At the request of Waiman Long, this has been enabled for debug kernels.

Cc: Waiman Long <longman@redhat.com>
Cc: Larry Woodman <lwoodman@redhat.com>
2021-08-30 10:49:50 -04:00
Jeremy Cline f0e2866787 [redhat] New configs in lib/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ZLIB_DFLTCC:

 Enable s390x hardware support for zlib in the kernel.

 Symbol: ZLIB_DFLTCC [=y]
 Type  : bool
 Defined at lib/Kconfig:281
   Prompt: Enable s390x DEFLATE CONVERSION CALL support for kernel zlib
   Depends on: S390 [=y]
   Location:
     -> Library routines

---
2021-08-30 10:49:50 -04:00
Jeremy Cline 12a0bf3d57 [redhat] New configs in init/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BOOT_CONFIG:

 Extra boot config allows system admin to pass a config file as
 complemental extension of kernel cmdline when booting.
 The boot config file must be attached at the end of initramfs
 with checksum and size.
 See <file:Documentation/admin-guide/bootconfig.rst> for details.

 If unsure, say Y.

 Symbol: BOOT_CONFIG [=y]
 Type  : bool
 Defined at init/Kconfig:1227
   Prompt: Boot config support
   Depends on: BLK_DEV_INITRD [=y]
   Location:
     -> General setup
       -> Initial RAM filesystem and RAM disk (initramfs/initrd) support (BLK_DEV_INITRD [=y])
 Selects: LIBXBC [=y]

---
2021-08-30 10:49:50 -04:00
Jeremy Cline 71ccd92399 [redhat] New configs in drivers/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_QUICC_ENGINE:

 The QUICC Engine (QE) is a new generation of communications
 coprocessors on Freescale embedded CPUs (akin to CPM in older chips).
 Selecting this option means that you wish to build a kernel
 for a machine with a QE coprocessor.

 Symbol: QUICC_ENGINE [=n]
 Type  : bool
 Defined at drivers/soc/fsl/qe/Kconfig:6
   Prompt: QUICC Engine (QE) framework support
   Depends on: OF [=y] && HAS_IOMEM [=y] && (PPC [=y] || ARM || ARM64 || COMPILE_TEST [=n])
   Location:
     -> Device Drivers
       -> SOC (System On Chip) specific Drivers
         -> NXP/Freescale QorIQ SoC drivers
 Selects: GENERIC_ALLOCATOR [=y] && CRC32 [=y]
 Selected by [n]:
   - KMETER1 [=n] && PPC_83xx [=n]

---
2021-08-30 10:49:50 -04:00
Jeremy Cline 179b7c4c03 [redhat] New configs in drivers/reset
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_RESET_BRCMSTB_RESCAL:

 This enables the RESCAL reset controller for SATA, PCIe0, or PCIe1 on
 BCM7216.

 Symbol: RESET_BRCMSTB_RESCAL [=n]
 Type  : bool
 Defined at drivers/reset/Kconfig:52
   Prompt: Broadcom STB RESCAL reset controller
   Depends on: RESET_CONTROLLER [=y]
   Location:
     -> Device Drivers
       -> Reset Controller Support (RESET_CONTROLLER [=y])

---

 CONFIG_RESET_INTEL_GW:

 This enables the reset controller driver for Intel Gateway SoCs.
 Say Y to control the reset signals provided by reset controller.
 Otherwise, say N.

 Symbol: RESET_INTEL_GW [=n]
 Type  : bool
 Defined at drivers/reset/Kconfig:74
   Prompt: Intel Reset Controller Driver
   Depends on: RESET_CONTROLLER [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Reset Controller Support (RESET_CONTROLLER [=y])
 Selects: REGMAP_MMIO [=y]

---
2021-08-30 10:49:49 -04:00
Jeremy Cline 765421e820 [redhat] New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_LYNXPOINT:

 Lynxpoint is the PCH of Intel Haswell. This pinctrl driver
 provides an interface that allows configuring of PCH pins and
 using them as GPIOs.

 Symbol: PINCTRL_LYNXPOINT [=n]
 Type  : tristate
 Defined at drivers/pinctrl/intel/Kconfig:34
   Prompt: Intel Lynxpoint pinctrl and GPIO driver
   Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINMUX [=y] && PINCONF [=y] && GENERIC_PINCONF [=y] && GPIOLIB [=y] && GPIOLIB_IRQCHIP [=y]

---
2021-08-30 10:49:49 -04:00
Jeremy Cline 6be7205455 [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AD7091R5:

 Say yes here to build support for Analog Devices AD7091R-5 ADC.

 Symbol: AD7091R5 [=n]
 Type  : tristate
 Defined at drivers/iio/adc/Kconfig:24
   Prompt: Analog Devices AD7091R5 ADC Driver
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters
 Selects: REGMAP_I2C [=m]

---

 CONFIG_BMA400:

 Say Y here if you want to build a driver for the Bosch BMA400
 triaxial acceleration sensor.

 To compile this driver as a module, choose M here: the
 module will be called bma400_core and you will also get
 bma400_i2c if I2C is enabled.

 Symbol: BMA400 [=n]
 Type  : tristate
 Defined at drivers/iio/accel/Kconfig:115
   Prompt: Bosch BMA400 3-Axis Accelerometer Driver
   Depends on: IIO [=m]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Accelerometers
 Selects: REGMAP [=y] && BMA400_I2C [=n]

---

 CONFIG_DLHL60D:

 Say yes here to build support for the All Sensors DLH series
 pressure sensors driver.

 To compile this driver as a module, choose M here: the module
 will be called dlhl60d.

 Symbol: DLHL60D [=n]
 Type  : tristate
 Defined at drivers/iio/pressure/Kconfig:56
   Prompt: All Sensors DLHL60D and DLHL60G low voltage digital pressure sensors
   Depends on: IIO [=m] && I2C [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Pressure sensors
 Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]

---

 CONFIG_LTC2496:

 Say yes here to build support for Linear Technology LTC2496
 16-Bit 8-/16-Channel Delta Sigma ADC.

 To compile this driver as a module, choose M here: the module will be
 called ltc2496.

 Symbol: LTC2496 [=n]
 Type  : tristate
 Defined at drivers/iio/adc/Kconfig:533
   Prompt: Linear Technology LTC2496 ADC driver
   Depends on: IIO [=m] && SPI [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters

---

 CONFIG_PING:

 Say Y here to build a driver for GPIO bitbanged ranger sensors
 with just one GPIO for the trigger and echo. This driver can be
 used to measure the distance of objects.

 Actually supported are:
 - Parallax PING))) (ultrasonic)
 - Parallax LaserPING (time-of-flight)

 To compile this driver as a module, choose M here: the
 module will be called ping.

 Symbol: PING [=n]
 Type  : tristate
 Defined at drivers/iio/proximity/Kconfig:61
   Prompt: Parallax GPIO bitbanged ranger sensors
   Depends on: IIO [=m] && GPIOLIB [=y]
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Proximity and distance sensors

---
2021-08-30 10:49:49 -04:00
Jeremy Cline 1748e0893a [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_GPIO_LOGICVC:

 Say yes here to support GPIO functionality of the Xylon LogiCVC
 programmable logic block.

 Symbol: GPIO_LOGICVC [=n]
 Type  : tristate
 Defined at drivers/gpio/Kconfig:315
   Prompt: Xylon LogiCVC GPIO support
   Depends on: GPIOLIB [=y] && HAS_IOMEM [=y] && MFD_SYSCON [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> Memory mapped GPIO drivers

---
2021-08-30 10:49:49 -04:00
Jeremy Cline 3355da177b [redhat] New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_APPLE_PROPERTIES:

 Retrieve properties from EFI on Apple Macs and assign them to
 devices, allowing for improved support of Apple hardware.
 Properties that would otherwise be missing include the
 Thunderbolt Device ROM and GPU configuration data.

 If unsure, say Y if you have a Mac.  Otherwise N.

 Symbol: APPLE_PROPERTIES [=n]
 Type  : bool
 Defined at drivers/firmware/efi/Kconfig:178
   Prompt: Apple Device Properties
   Depends on: EFI [=y] && EFI_STUB [=y] && X86 [=y]
   Location:
     -> Firmware Drivers
       -> EFI (Extensible Firmware Interface) Support
 Selects: EFI_DEV_PATH_PARSER [=n] && UCS2_STRING [=y]
 Selected by [n]:
   - USB4 [=n] && PCI [=y] && (X86 [=y] || COMPILE_TEST [=n]) && EFI_STUB [=y] && X86 [=y]

---

This is required to be on for CONFIG_USB4=m. As Jarod has requested
that, this has been set to y.

Cc: Jarod Wilson <jarod@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:49:49 -04:00
Jeremy Cline be865152f2 [redhat] New configs in arch/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_STRICT_KERNEL_RWX:

 If this is set, kernel text and rodata memory will be made read-only,
 and non-text memory will be made non-executable. This provides
 protection against certain security exploits (e.g. executing the heap
 or modifying text)

 These features are considered standard security practice these days.
 You should say Y here in almost all cases.

 Symbol: STRICT_KERNEL_RWX [=n]
 Type  : bool
 Defined at arch/Kconfig:865
   Prompt: Make kernel text and rodata read-only
   Depends on: ARCH_HAS_STRICT_KERNEL_RWX [=y]
   Visible if: ARCH_HAS_STRICT_KERNEL_RWX [=y] && ARCH_OPTIONAL_KERNEL_RWX [=y]
   Location:
     -> General architecture-dependent options

---
2021-08-30 10:49:48 -04:00
Jeremy Cline f16465ee08 [redhat] New configs in security/selinux
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE:

 This option defines the size of the internal SID -> context string
 cache, which improves the performance of context to string
 conversion.  Setting this option to 0 disables the cache completely.

 If unsure, keep the default value.

 Symbol: SECURITY_SELINUX_SID2STR_CACHE_SIZE [=256]
 Type  : integer
 Prompt: NSA SELinux SID to context string translation cache size
   Location:
     -> Security options
       -> NSA SELinux Support (SECURITY_SELINUX [=y])
   Defined at security/selinux/Kconfig:105
   Depends on: SECURITY_SELINUX [=y]

---

 CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS:

 This option sets the number of buckets used in the sidtab hashtable
 to 2^SECURITY_SELINUX_SIDTAB_HASH_BITS buckets. The number of hash
 collisions may be viewed at /sys/fs/selinux/ss/sidtab_hash_stats. If
 chain lengths are high (e.g. > 20) then selecting a higher value here
 will ensure that lookups times are short and stable.

 Symbol: SECURITY_SELINUX_SIDTAB_HASH_BITS [=9]
 Type  : integer
 Range : [8 13]
 Prompt: NSA SELinux sidtab hashtable size
   Location:
     -> Security options
       -> NSA SELinux Support (SECURITY_SELINUX [=y])
   Defined at security/selinux/Kconfig:93
   Depends on: SECURITY_SELINUX [=y]

---

Cc: Ondrej Mosnacek <omosnace@redhat.com>
2021-08-30 10:49:48 -04:00
Jeremy Cline 341fcb8bde [redhat] New configs in net/vmw_vsock
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_VSOCKETS_LOOPBACK:

 This module implements a loopback transport for Virtual Sockets,
 using vmw_vsock_virtio_transport_common.

 To compile this driver as a module, choose M here: the module
 will be called vsock_loopback. If unsure, say N.

 Symbol: VSOCKETS_LOOPBACK [=m]
 Type  : tristate
 Prompt: Virtual Sockets loopback transport
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> Virtual Socket protocol (VSOCKETS [=m])
   Defined at net/vmw_vsock/Kconfig:29
   Depends on: NET [=y] && VSOCKETS [=m]
   Selects: VIRTIO_VSOCKETS_COMMON [=m]

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
2021-08-30 10:49:48 -04:00
Jeremy Cline eae3404d25 [redhat] New configs in net/mptcp
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MPTCP:

 Multipath TCP (MPTCP) connections send and receive data over multiple
 subflows in order to utilize multiple network paths. Each subflow
 uses the TCP protocol, and TCP options carry header information for
 MPTCP.

 Symbol: MPTCP [=n]
 Type  : bool
 Prompt: MPTCP: Multipath TCP
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> TCP/IP networking (INET [=y])
   Defined at net/mptcp/Kconfig:2
   Depends on: NET [=y] && INET [=y]
   Selects: SKB_EXTENSIONS [=y] && CRYPTO_LIB_SHA256 [=y]

MPTCP has been enabled at the request of Davide Caratti.

---

 CONFIG_MPTCP_HMAC_TEST:

 This option enable boot time self-test for the HMAC implementation
 used by the MPTCP code

 Say N if you are unsure.

 Symbol: MPTCP_HMAC_TEST [=n]
 Type  : bool
 Prompt: Tests for MPTCP HMAC implementation
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> TCP/IP networking (INET [=y])
   Defined at net/mptcp/Kconfig:19
   Depends on: NET [=y] && INET [=y]

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
2021-08-30 10:49:48 -04:00
Jeremy Cline 137d464a20 [redhat] New configs in net/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ETHTOOL_NETLINK:

 An alternative userspace interface for ethtool based on generic
 netlink. It provides better extensibility and some new features,
 e.g. notification messages.

 Symbol: ETHTOOL_NETLINK [=y]
 Type  : bool
 Prompt: Netlink interface for ethtool
   Location:
     -> Networking support (NET [=y])
   Defined at net/Kconfig:453
   Depends on: NET [=y]

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Davide Caratti <dcaratti@redhat.com>
Cc: Eric Garver <egarver@redhat.com>
Cc: Flavio Leitner <fbl@redhat.com>
Cc: Florian Westphal <fwestpha@redhat.com>
Cc: Guillaume Nault <gnault@redhat.com>
Cc: Hangbin Liu <haliu@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jarod Wilson <jarod@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Marcelo Leitner <mleitner@redhat.com>
Cc: Matteo Croce <mcroce@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Phil Sutter <psutter@redhat.com>
Cc: Sabrina Dubroca <sdubroca@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>
Cc: Xin Long <lxin@redhat.com>
2021-08-30 10:49:48 -04:00
Jeremy Cline 6db9aea3cf [redhat] New configs in drivers/spi
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SPI_HISI_SFC_V3XX:

 This enables support for HiSilicon v3xx SPI-NOR flash controller
 found in hi16xx chipsets.

 Symbol: SPI_HISI_SFC_V3XX [=n]
 Type  : tristate
 Prompt: HiSilicon SPI-NOR Flash Controller for Hi16XX chipsets
   Location:
     -> Device Drivers
       -> SPI support (SPI [=y])
   Defined at drivers/spi/Kconfig:284
   Depends on: SPI [=y] && SPI_MASTER [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) && HAS_IOMEM [=y]
   Selects: CONFIG_MTD_SPI_NOR

---
2021-08-30 10:49:48 -04:00
Jeremy Cline 24d68adeda [redhat] New configs in drivers/ptp
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PTP_1588_CLOCK_INES:

 This driver adds support for using the ZHAW InES 1588 IP
 core.  This clock is only useful if the MII bus of your MAC
 is wired up to the core.

 Symbol: PTP_1588_CLOCK_INES [=n]
 Type  : tristate
 Prompt: ZHAW InES PTP time stamping IP core
   Location:
     -> Device Drivers
       -> PTP clock support
   Defined at drivers/ptp/Kconfig:78
   Depends on: NETWORK_PHY_TIMESTAMPING [=y] && PHYLIB [=y] && PTP_1588_CLOCK [=y]

---

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:49:47 -04:00
Jeremy Cline ca52bd08ff [redhat] New configs in drivers/net/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BCM84881_PHY:

 Support the Broadcom BCM84881 PHY.

 Symbol: BCM84881_PHY [=n]
 Type  : bool
 Prompt: Broadcom BCM84881 PHY
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])
   Defined at drivers/net/phy/Kconfig:328
   Depends on: NETDEVICES [=y] && PHYLIB [=y]=y

---

Cc: Petr Oros <poros@redhat.com>
2021-08-30 10:49:47 -04:00
Jeremy Cline 994ffc2fc0 [redhat] New configs in drivers/net/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_WIREGUARD:

 WireGuard is a secure, fast, and easy to use replacement for IPSec
 that uses modern cryptography and clever networking tricks. It's
 designed to be fairly general purpose and abstract enough to fit most
 use cases, while at the same time remaining extremely simple to
 configure. See www.wireguard.com for more info.

 It's safe to say Y or M here, as the driver is very lightweight and
 is only in use when an administrator chooses to add an interface.

 Symbol: WIREGUARD [=n]
 Type  : tristate
 Prompt: WireGuard secure network tunnel
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> Network core driver support (NET_CORE [=y])
   Defined at drivers/net/Kconfig:74
   Depends on: NETDEVICES [=y] && NET_CORE [=y] && NET [=y] && INET [=y] && (IPV6 [=y] || !IPV6 [=y])
   Selects: NET_UDP_TUNNEL [=m] && DST_CACHE [=y] && CRYPTO [=y] && CRYPTO_LIB_CURVE25519 [=n] && CRYPTO_LIB_CHACHA20POLY1305 [=n] && CRYPTO_LIB_BLAKE2S [=n] && CRYPTO_CHACHA20_X86_64 [=m] && CRYPTO_POLY1305_X86_64 [=m] && CRYPTO_BLAKE2S_X86 [=n] && CRYPTO_CURVE25519_X86 [=n] && ARM_CRYPTO && ARM64_CRYPTO && CRYPTO_CHACHA20_NEON && CRYPTO_POLY1305_NEON && CRYPTO_POLY1305_ARM && CRYPTO_CURVE25519_NEON && CRYPTO_CHACHA_MIPS [=n] && CRYPTO_POLY1305_MIPS [=n]

---
2021-08-30 10:49:47 -04:00
Jeremy Cline f97e6087a4 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_ADM1177:

 If you say yes here you get support for Analog Devices ADM1177
 sensor chips.

 This driver can also be built as a module.  If so, the module
 will be called adm1177.

 Symbol: SENSORS_ADM1177 [=n]
 Type  : tristate
 Prompt: Analog Devices ADM1177 and compatibles
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
   Defined at drivers/hwmon/Kconfig:167
   Depends on: HWMON [=y] && I2C [=y]

---

 CONFIG_SENSORS_DRIVETEMP:

 If you say yes you get support for the temperature sensor on
 hard disk drives.

 This driver can also be built as a module. If so, the module
 will be called satatemp.

 Symbol: SENSORS_DRIVETEMP [=n]
 Type  : tristate
 Prompt: Hard disk drives with temperature sensors
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
   Defined at drivers/hwmon/Kconfig:398
   Depends on: HWMON [=y] && SCSI [=y] && ATA [=m]

---

 CONFIG_SENSORS_MAX20730:

 If you say yes here you get hardware monitoring support for Maxim
 MAX20730, MAX20734, and MAX20743.

 This driver can also be built as a module. If so, the module will
 be called max20730.

 Symbol: SENSORS_MAX20730 [=n]
 Type  : tristate
 Prompt: Maxim MAX20730, MAX20734, MAX20743
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])
   Defined at drivers/hwmon/pmbus/Kconfig:148
   Depends on: HWMON [=y] && PMBUS [=m]

---

 CONFIG_SENSORS_MAX31730:

 Support for the Maxim Integrated MAX31730 3-Channel Remote
 Temperature Sensor.

 This driver can also be built as a module. If so, the module
 will be called max31730.

 Symbol: SENSORS_MAX31730 [=n]
 Type  : tristate
 Prompt: MAX31730 temperature sensor
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
   Defined at drivers/hwmon/Kconfig:921
   Depends on: HWMON [=y] && I2C [=y]

---

 CONFIG_SENSORS_XDPE122:

 If you say yes here you get hardware monitoring support for Infineon
 XDPE12254, XDPE12284, device.

 This driver can also be built as a module. If so, the module will
 be called xdpe12284.

 Symbol: SENSORS_XDPE122 [=n]
 Type  : tristate
 Prompt: Infineon XDPE122 family
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])
   Defined at drivers/hwmon/pmbus/Kconfig:240
   Depends on: HWMON [=y] && PMBUS [=m]

---

Cc: Dean Nelson <dnelson@redhat.com>
2021-08-30 10:49:47 -04:00
Jeremy Cline 1197102adf [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARCH_RANDOM:

 Random number generation (part of the ARMv8.5 Extensions)
 provides a high bandwidth, cryptographically secure
 hardware random number generator.

 Symbol: ARCH_RANDOM [=y]
 Type  : bool
 Prompt: Enable support for random number generation
   Location:
     -> Kernel Features
       -> ARMv8.5 architectural features
   Defined at arch/arm64/Kconfig:1533

---

 CONFIG_ARM64_E0PD:

 E0PD (part of the ARMv8.5 extensions) allows us to ensure
 that EL0 accesses made via TTBR1 always fault in constant time,
 providing similar benefits to KASLR as those provided by KPTI, but
 with lower overhead and without disrupting legitimate access to
 kernel memory such as SPE.

 This option enables E0PD for TTBR1 where available.

 Symbol: ARM64_E0PD [=y]
 Type  : bool
 Prompt: Enable support for E0PD
   Location:
     -> Kernel Features
       -> ARMv8.5 architectural features
   Defined at arch/arm64/Kconfig:1521

---

 CONFIG_ARM64_ERRATUM_1530923:

 This option adds a workaround for ARM Cortex-A55 erratum 1530923.

 Affected Cortex-A55 cores (r0p0, r0p1, r1p0, r2p0) could end-up with
 corrupted TLBs by speculating an AT instruction during a guest
 context switch.

 If unsure, say Y.

 Symbol: ARM64_ERRATUM_1530923 [=y]
 Type  : bool
 Prompt: Cortex-A55: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation
   Location:
     -> Kernel Features
       -> ARM errata workarounds via the alternatives framework
   Defined at arch/arm64/Kconfig:539
   Selects: ARM64_WORKAROUND_SPECULATIVE_AT_VHE [=y]

---

 CONFIG_ARM64_USE_LSE_ATOMICS:

 As part of the Large System Extensions, ARMv8.1 introduces new
 atomic instructions that are designed specifically to scale in
 very large systems.

 Say Y here to make use of these instructions for the in-kernel
 atomic routines. This incurs a small overhead on CPUs that do
 not support these instructions and requires the kernel to be
 built with binutils >= 2.25 in order for the new instructions
 to be used.

 Symbol: ARM64_USE_LSE_ATOMICS [=y]
 Type  : bool
 Prompt: Atomic instructions
   Location:
     -> Kernel Features
       -> ARMv8.1 architectural features
   Defined at arch/arm64/Kconfig:1397
   Depends on: JUMP_LABEL [=y]

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
2021-08-30 10:49:47 -04:00
Jeremy Cline 373f91a9ca [redhat] Fix up some configurations with altered defaults
Several configurations in ARK and Fedora have changed type (tristate <->
bool) or have started being required by other configured modules. Adjust
the Fedora configurations to match the current Rawhide settings and move
ARK settings that have changed back to pending for review.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:46 -04:00
Jeremy Cline 9d1940a550 [redhat] AUTOMATIC: New configs 2021-08-30 10:49:46 -04:00
Jeremy Cline f6ab2aae75 [redhat] AUTOMATIC: New configs 2021-08-30 10:49:46 -04:00
Bruno Meneguele e2a36cfdab distgit-changelog: handle multiple y-stream BZ numbers
RHEL-8 inherited distgit changelog script from RHEL7-alt, which had a bug that
wouldn't pick all bugzilla numbers from a patch in kernel.spec changelog
section in case it was solving multiple ones, but only the first. With that,
many BZs where not being included in distgit's commit "Resolves:" line checked
by distgit server rules.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 10:49:46 -04:00
Bruno Meneguele d9835961c8 redhat/kernel.spec: remove all inline comments
It seems rpmbuild started to complain (warn) about any inline comment in
kernel.spec.template file in new versions, like used in Fedora 31:

warning: extra tokens at the end of %else directive in line 439:  %else # released_kernel
...

Place this commentaries before rpmspec real token in a single line, muting the
warnings.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 10:49:46 -04:00
Bruno Meneguele 6cf062014f redhat/genspec: awk unknown whitespace regex pattern
New versions of awk (i.e. those present in Fedora) started warning about "\ "
not being a regex pattern for whitespaces. Although it still works fine,
upstream may get rid of it soon.

awk: cmd. line:72: warning: regexp escape sequence `\ ' is not a known regexp operator

awk is used in redhat/genspec.sh to generate rpm's changelogs from kernel
source git commits, and the specific file line is responsible to handle
multiline subjects, where it's bigger than 78 chars. Without it working
properly we'll see cropped subjects as changelog lines.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-08-30 10:49:46 -04:00
Jeremy Cline b41b77604e Improve the readability of gen_config_patches.sh
This performs a number of refactors to the script that should not impact
behavior. It:

* Resolves all ShellCheck errors and warnings

* Moves cleanup into a function registered with trap

* Simplifies a few expressions to more idiomatic equivalents

* Moves temporary working files out of /tmp/ and into a dedicated
  directory created by mktemp.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:45 -04:00
Jeremy Cline 9164cd81f8 Fix some awkward edge cases in gen_config_patches.sh
This refactors the awk script that sorts new configuration symbols by
subsystem. There were two awkward edge cases.

The first was in the handling of the drivers/{net,net/ethernet} that
failed to strip the trailing ":<linenumber>" from new configuration
symbols in drivers/net/{Kconfig,ethernet/Kconfig}. This led to branch
names that included the ":<linenumber>" which aren't valid branch names
and caused the script to create commits in incorrect branches.

The second edge case was that it replaced "/" with "_" in the filename
it created. The problem with this is that some subsystem directories
have "_" in the name (e.g. net/vmw_vsock) When it turned the filename
back into a kernel tree path it would mangle the name and fail to find
any maintainers for it. The new placeholder character is ":" which is
not currently in any kernel directory name and seems unlikely to appear
in one.

Additionally, there are some changes for readability.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:45 -04:00
Jeremy Cline 4516cac010 [redhat] Explicitly disable GGC_PLUGINS for ARK
It was reported that ARK started to fail to build in some build
environments starting with v5.5-rc5 because CONFIG_GCC_PLUGINS was being
changed from unset to y. This is likely due to upstream commit
a5b0dc5a46 ("gcc-plugins: make it possible to disable
CONFIG_GCC_PLUGINS again"), but regardless we want to explicitly set
GGC_PLUGINS one way or the other because it's one of those annoying
Kconfig symbols that depends on the environment you prepare the
configuration in.

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:45 -04:00
Jeremy Cline 33275a2cba [redhat] Add new dependencies to pending-common for review
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:45 -04:00
Jeremy Cline 520344f53e [redhat] AUTOMATIC: New configs for Fedora 2021-08-30 10:49:45 -04:00
Jeremy Cline 9372dd8fa4 [redhat] Introduce a pending-fedora config directory tree
ARK plans to merge with Fedora and has therefore begun building the
Fedora configuration files.

The current ARK process generates defaults for new configuration options
in the redhat/configs/pending/ directory, and then generates commits
moving these configs to the redhat/configs/common/ directory which are
sent out for review. This is necessary because rebases are largely
automated, there needs to be a place to set defaults for new
configuration options that indicate they need human review.

This is problematic for Fedora because it enables a super-set of
ARK options, which in turn lead to options being exposed during rebases
that are not exposed for ARK. Thus, this adds a
redhat/configs/pending-fedora/ configuration directory where new options
for Fedora rebases are stored. This also renames the current pending/
directory to be pending-common/ in order to make the final destination
of configuration options clearer. Fedora still inherits configuration
options from common/ and pending-common/ so only settings specific to
Fedora are placed here.

There is no pending-ark/ directory at the moment because if, during
review, ARK needs a setting that differs from Fedora, the setting is
changed and manually moved into the ark/ directory.

Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:45 -04:00
Jeremy Cline ad906070b5 [redhat] AUTOMATIC: New configs 2021-08-30 10:49:44 -04:00
Jeremy Cline 62ee20c0d7 Update the CI environment to use Fedora 31
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:44 -04:00
Laura Abbott ac2f107101 [redhat] configs: Adjust CONFIG_STM and CONFIG_INTEL_TH
Match RHEL8

Cc: Jiri Olsa <jolsa@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:44 -04:00
Laura Abbott 799b242d88 [redhat] configs: Adjust SoF support
Match RHEL8

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:44 -04:00
Laura Abbott 7e386f9cc7 [redhat] configs: CONFIG_PCI_PF_STUB
Match RHEL8

Cc: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:44 -04:00
Laura Abbott c6b5298800 [redhat] configs: CONFIG_XEN_BALLOON
Match RHEL8

Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:43 -04:00
Laura Abbott 2be0fcefbe [redhat] configs: Adjust CONFIG_PSI_DEFAULT_DISABLED
Match RHEL8

Cc: Waiman Long <longman@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:43 -04:00
Laura Abbott 54a3e12dbd [redhat] configs: Adjust CONFIG_DMA_TEST
Match RHEL8

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:43 -04:00
Laura Abbott 984067426d [redhat] config: Adjust DRM configs
Match RHEL8

Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:43 -04:00
Laura Abbott c208de3bfa [redhat] configs: Adjust SERIAL_8250_NR_UARTS
This file was merged incorrectly with the new configuration
layout.

Cc: prarit@redhat.com
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:43 -04:00
Laura Abbott 9fefe3b4a4 [redhat] configs: Adjust CONFIG_BPF_STREAM_PARSER
Match RHEL8

Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:43 -04:00
Laura Abbott dfea11a8ef [redhat] configs: Adjust CONFIG_NVME_TCP and CONFIG_NVME_TARGET_TCP
Match RHEL8

Cc: Chris Leech <cleech@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:42 -04:00
Laura Abbott 870995056d [redhat] configs: Adjust USB typec options
Match with RHEL8

Cc: Torez Smith <torez@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:42 -04:00
Laura Abbott 1f29b3082d [redhat] configs: Adjust some sound configs
Match with RHEL8

Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:42 -04:00
Laura Abbott c1b6ed1c05 [redhat] configs: Turn off CONFIG_AGP
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:42 -04:00
Jeremy Cline 0ebe356196 [redhat] New configs in arch/powerpc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PPC_UV:

 This option paravirtualizes the kernel to run in POWER platforms that
 supports the Protected Execution Facility (PEF). On such platforms,
 the ultravisor firmware runs at a privilege level above the
 hypervisor.

 If unsure, say "N".

 Symbol: PPC_UV [=n]
 Type  : bool
 Prompt: Ultravisor support
   Location:
     -> Kernel options
   Defined at arch/powerpc/Kconfig:455
   Depends on: KVM_BOOK3S_HV_POSSIBLE [=y]
   Selects: ZONE_DEVICE [=y] && DEV_PAGEMAP_OPS [=y] && DEVICE_PRIVATE [=y] && MEMORY_HOTPLUG [=y] && MEMORY_HOTREMOVE [=y]

---

Cc: Thomas Huth <thuth@redhat.com>
Cc: David Gibson <dgibson@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>
2021-08-30 10:49:42 -04:00
Jeremy Cline aeb9155ad4 [redhat] Explicitly use python3 for building the htmldocs
In the never-ending slow-motion train wreck that is the Python
ecosystem, we need to explicitly specify Python 3 because the build root
does not have /usr/bin/python which causes the documentation build to
fail. Even if it did, the Python 3 version of Sphinx is being used to
build the documentation so unless /usr/bin/python was Python 3 it'd
still break.

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Herton R. Krzesinski <herton@redhat.com>
Cc: Bruno Meneguele <bmeneg@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:41 -04:00
Jeremy Cline 8296df451a [redhat] New configs in drivers/base
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FW_CACHE:

 Because firmware caching generates uevent messages that are sent
 over a netlink socket, it can prevent suspend on many platforms.
 It is also not always useful, so on such platforms we have the
 option.

 If unsure, say Y.

 Symbol: FW_CACHE [=y]
 Type  : bool
 Prompt: Enable firmware caching during suspend
   Location:
     -> Device Drivers
       -> Generic Driver Options
         -> Firmware loader
           -> Firmware loading facility (FW_LOADER [=y])
   Defined at drivers/base/firmware_loader/Kconfig:172
   Depends on: FW_LOADER [=y] && PM_SLEEP [=y]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
2021-08-30 10:49:41 -04:00
Laura Abbott e2ac7373df [redhat] kernel.spec.template: Pick up ldflags/cflags for tools
We weren't building with these flags because thing were broken for a while.
It's now fixed so let's pick it up.

Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:41 -04:00
Laura Abbott bc752cce8e [redhat] kernel.spec.template: package intel-speed-select
Add the intel-speed-select utility to the x86 kernel-tools rpm.

Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:41 -04:00
Jeremy Cline 2deda29207 [redhat] New configs in drivers/pinctrl
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PINCTRL_EQUILIBRIUM:

 Equilibrium pinctrl driver is a pinctrl & GPIO driver for Intel Lightning
 Mountain network processor SoC that supports both the linux GPIO and pin
 control frameworks. It provides interfaces to setup pinmux, assign desired
 pin functions, configure GPIO attributes for LGM SoC pins. Pinmux and
 pinconf settings are retrieved from device tree.

 Symbol: PINCTRL_EQUILIBRIUM [=n]
 Type  : tristate
 Prompt: Generic pinctrl and GPIO driver for Intel Lightning Mountain SoC
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
   Defined at drivers/pinctrl/Kconfig:423
   Depends on: PINCTRL [=y]
   Selects: PINMUX [=y] && PINCONF [=y] && GPIOLIB [=y] && GPIO_GENERIC [=m] && GPIOLIB_IRQCHIP [=y] && GENERIC_PINCONF [=y] && GENERIC_PINCTRL_GROUPS [=n] && GENERIC_PINMUX_FUNCTIONS [=n]

---

 CONFIG_PINCTRL_MSM8976:

 This is the pinctrl, pinmux, pinconf and gpiolib driver for the
 Qualcomm TLMM block found on the Qualcomm MSM8976 platform.
 The Qualcomm MSM8956, APQ8056, APQ8076 platforms are also
 supported by this driver.

 Symbol: PINCTRL_MSM8976 [=n]
 Type  : tristate
 Prompt: Qualcomm 8976 pin controller driver
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
   Defined at drivers/pinctrl/qcom/Kconfig:93
   Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
   Selects: PINCTRL_MSM [=y]

---

 CONFIG_PINCTRL_TIGERLAKE:

 This pinctrl driver provides an interface that allows configuring
 of Intel Tiger Lake PCH pins and using them as GPIOs.
 Symbol: PINCTRL_TIGERLAKE [=n]
 Type  : tristate
 Prompt: Intel Tiger Lake pinctrl and GPIO driver
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
   Defined at drivers/pinctrl/intel/Kconfig:118
   Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
   Selects: PINCTRL_INTEL [=m]

---

Cc: John W. Linville <linville@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
2021-08-30 10:49:41 -04:00
Jeremy Cline ccebe52134 [redhat] New configs in lib/Kconfig.kasan
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KASAN_VMALLOC:

 By default, the shadow region for vmalloc space is the read-only
 zero page. This means that KASAN cannot detect errors involving
 vmalloc space.

 Enabling this option will hook in to vmap/vmalloc and back those
 mappings with real shadow memory allocated on demand. This allows
 for KASAN to detect more sorts of errors (and to support vmapped
 stacks), but at the cost of higher memory usage.

 Symbol: KASAN_VMALLOC [=n]
 Type  : bool
 Prompt: Back mappings in vmalloc space with real shadow memory
   Location:
     -> Kernel hacking
       -> Memory Debugging
   Defined at lib/Kconfig.kasan:148
   Depends on: KASAN [=y] && HAVE_ARCH_KASAN_VMALLOC [=y]

---

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Laura Abbott <labbott@redhat.com>
Cc: Marcelo Ricardo Leitner <mleitner@redhat.com>
2021-08-30 10:49:41 -04:00
Jeremy Cline bb53bc1b2b [redhat] New configs in arch/s390
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_S390_UNWIND_SELFTEST:

 This option enables s390 specific stack unwinder testing kernel
 module. This option is not useful for distributions or general
 kernels, but only for kernel developers working on architecture code.

 Say N if you are unsure.

 Symbol: S390_UNWIND_SELFTEST [=n]
 Type  : tristate
 Prompt: Test unwind functions
   Location:
     -> Selftests
   Defined at arch/s390/Kconfig:1022

---

Cc: Thomas Huth <thuth@redhat.com>
2021-08-30 10:49:40 -04:00
Jan Stancek 4e4535d460 redhat: drop whitespace from with_gcov macro
Bugzilla: INTERNAL
Upstream: RHEL only

When I introduced rh-srpm-gcov target I missed that with_gcov macro
will pass extra white space to make:
  make -s ARCH=x86_64 V=1 -j8 KCFLAGS= 'WITH_GCOV= 1 ' bzImage
which can break ifeq/ifneq conditions.

ARK is currently not making use of this flag, but for sake of consistency,
mirror the change from RHEL.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
2021-08-30 10:49:40 -04:00
Ondrej Mosnacek 88e80eea03 configs: Enable CONFIG_KEY_DH_OPERATIONS on ARK
This is a manual import of a patch that got horribly mangled in
Patchwork. The original commit message is below:

Message-id: <20191115130108.257757-1-omosnace@redhat.com>
Patchwork-id: 287415
O-Subject: [ARK INTERNAL PATCH] configs: Enable CONFIG_KEY_DH_OPERATIONS on ARK
Bugzilla:
RH-Acked-by: Herbert Xu <herbert.xu@redhat.com>
RH-Acked-by: Neil Horman <nhorman@redhat.com>

Bugzilla: INTERNAL
Upstream status: RHEL only
Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=24725630
Tested: booted on x86_64 and selinux-testuite "keys" subtest now passes

We need CONFIG_KEY_DH_OPERATIONS enabled on ARK for testing SELinux.
Fedora already enables it, so just move the config to common.

We also need to make CONFIG_CRYPTO_DH builtin now on all arches. Again
just adopt the config from Fedora.

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:40 -04:00
Jeremy Cline 6e6050e87d [redhat] New configs in drivers/iio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_AD7292:

 Say yes here to build support for Analog Devices AD7292
 8 Channel ADC with temperature sensor.

 To compile this driver as a module, choose M here: the
 module will be called ad7292.

 Symbol: AD7292 [=n]
 Type  : tristate
 Prompt: Analog Devices AD7292 ADC driver
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Analog to digital converters
   Defined at drivers/iio/adc/Kconfig:58
   Depends on: IIO [=m] && SPI [=y]

---

 CONFIG_ADUX1020:

 Say Y here if you want to build a driver for the Analog Devices
 ADUX1020 photometric sensor.

 To compile this driver as a module, choose M here: the
 module will be called adux1020.

 Symbol: ADUX1020 [=n]
 Type  : tristate
 Prompt: ADUX1020 photometric sensor
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Light sensors
   Defined at drivers/iio/light/Kconfig:35
   Depends on: IIO [=m] && I2C [=y]
   Selects: REGMAP_I2C [=y]

---

 CONFIG_FXOS8700_I2C:

 Say yes here to build support for the NXP FXOS8700 m+g combo
 sensor on I2C.

 This driver can also be built as a module. If so, the module will be
 called fxos8700_i2c.

 Symbol: FXOS8700_I2C [=n]
 Type  : tristate
 Prompt: NXP FXOS8700 I2C driver
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Inertial measurement units
   Defined at drivers/iio/imu/Kconfig:46
   Depends on: IIO [=m] && I2C [=y]
   Selects: FXOS8700 [=n] && REGMAP_I2C [=y]

---

 CONFIG_FXOS8700_SPI:

 Say yes here to build support for the NXP FXOS8700 m+g combo
 sensor on SPI.

 This driver can also be built as a module. If so, the module will be
 called fxos8700_spi.

 Symbol: FXOS8700_SPI [=n]
 Type  : tristate
 Prompt: NXP FXOS8700 SPI driver
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Inertial measurement units
   Defined at drivers/iio/imu/Kconfig:58
   Depends on: IIO [=m] && SPI [=y]
   Selects: FXOS8700 [=n] && REGMAP_SPI [=y]

---

 CONFIG_LTC2983:

 Say yes here to build support for the LTC2983 Multi-Sensor
 high accuracy digital temperature measurement system.

 To compile this driver as a module, choose M here: the module
 will be called ltc2983.

 Symbol: LTC2983 [=n]
 Type  : tristate
 Prompt: Analog Devices Multi-Sensor Digital Temperature Measurement System
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Temperature sensors
   Defined at drivers/iio/temperature/Kconfig:7
   Depends on: IIO [=m] && SPI [=y]
   Selects: REGMAP_SPI [=y]

---

 CONFIG_VEML6030:

 Say Y here if you want to build a driver for the Vishay VEML6030
 ambient light sensor (ALS).

 To compile this driver as a module, choose M here: the
 module will be called veml6030.

 Symbol: VEML6030 [=n]
 Type  : tristate
 Prompt: VEML6030 ambient light sensor
   Location:
     -> Device Drivers
       -> Industrial I/O support (IIO [=m])
         -> Light sensors
   Defined at drivers/iio/light/Kconfig:510
   Depends on: IIO [=m] && I2C [=y]
   Selects: REGMAP_I2C [=y]

---
2021-08-30 10:49:40 -04:00
Jeremy Cline 31cef41adf [redhat] New configs in drivers/gpio
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_GPIO_BCM_XGS_IPROC:

 Say yes here to enable GPIO support for Broadcom XGS iProc SoCs.

 Symbol: GPIO_BCM_XGS_IPROC [=y]
 Type  : tristate
 Prompt: BRCM XGS iProc GPIO support
   Location:
     -> Device Drivers
       -> GPIO Support (GPIOLIB [=y])
         -> Memory mapped GPIO drivers
   Defined at drivers/gpio/Kconfig:158
   Depends on: GPIOLIB [=y] && HAS_IOMEM [=y] && OF_GPIO [=y] && (ARCH_BCM_IPROC [=y] || COMPILE_TEST [=n])
   Selects: GPIO_GENERIC [=y] && GPIOLIB_IRQCHIP [=y]

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
2021-08-30 10:49:40 -04:00
Laura Abbott 80d9c555eb configs: Adjust CONFIG_MPLS_ROUTING and CONFIG_MPLS_IPTUNNEL
Match RHEL8

Cc: Hangbin Liu <haliu@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:39 -04:00
Jeremy Cline 3c9ca4eaf4 New configs in lib/crypto
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CRYPTO_LIB_BLAKE2S:

 Enable the Blake2s library interface. This interface may be fulfilled
 by either the generic implementation or an arch-specific one, if one
 is available and enabled.

 Symbol: CRYPTO_LIB_BLAKE2S [=n]
 Type  : tristate
 Prompt: BLAKE2s hash function library
   Location:
     -> Cryptographic API (CRYPTO [=y])
   Defined at lib/crypto/Kconfig:27
   Depends on: CRYPTO [=y] && (CRYPTO_ARCH_HAVE_LIB_BLAKE2S [=n] || !CRYPTO_ARCH_HAVE_LIB_BLAKE2S [=n])
   Selects: CRYPTO_LIB_BLAKE2S_GENERIC [=n]
2021-08-30 10:49:39 -04:00
Jeremy Cline 5115b693a6 New configs in drivers/char
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HW_RANDOM_HISI_V2:

 This driver provides kernel-side support for the True Random Number
 Generator V2 hardware found on HiSilicon Hi1620 SoC.

 To compile this driver as a module, choose M here: the
 module will be called hisi-trng-v2.

 If unsure, say Y.

 Symbol: HW_RANDOM_HISI_V2 [=y]
 Type  : tristate
 Prompt: HiSilicon True Random Number Generator V2 support
   Location:
     -> Device Drivers
       -> Character devices
         -> Hardware Random Number Generator Core support (HW_RANDOM [=y])
   Defined at drivers/char/hw_random/Kconfig:311
   Depends on: HW_RANDOM [=y] && ARM64 [=y] && ACPI [=y]
2021-08-30 10:49:39 -04:00
Jeremy Cline 9fe57376d8 Turn on BLAKE2B for Fedora
Fedora Rawhide has this turned on as a module and it is being
automatically selected based on the current Fedora configuration. This
fixes the build failure CI detected.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:39 -04:00
Laura Abbott 782334a9c2 kernel.spec.template: Clean up stray *.h.s files
The various header testing options (e.g. CONFIG_KERNEL_HEADER_TEST)
generate stray *.s files as part of the testing. We want to be
running these tests but we don't actually care about the files.
Make sure these files get cleaned up so they don't end up packaged
and causing an excessively big kernel-devel.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:39 -04:00
Jeremy Cline 38f9e62619 [redhat] New configs in arch/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_COMPAT_32BIT_TIME:

 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

 Symbol: COMPAT_32BIT_TIME [=y]
 Type  : bool
 Prompt: Provide system calls for 32-bit time_t
   Location:
     -> General architecture-dependent options
   Defined at arch/Kconfig:799

---
2021-08-30 10:49:39 -04:00
Jeremy Cline df0985a461 [redhat] New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARCH_S32:

 This enables support for the NXP S32 family of processors.

 Symbol: ARCH_S32 [=n]
 Type  : bool
 Prompt: NXP S32 SoC Family
   Location:
     -> Platform selection
   Defined at arch/arm64/Kconfig.platforms:217

---

Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
2021-08-30 10:49:38 -04:00
Jeremy Cline 577c0f02e1 [redhat] New configs in arch/x86
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_X86_IOPL_IOPERM:

 This enables the ioperm() and iopl() syscalls which are necessary
 for legacy applications.

 Legacy IOPL support is an overbroad mechanism which allows user
 space aside of accessing all 65536 I/O ports also to disable
 interrupts. To gain this access the caller needs CAP_SYS_RAWIO
 capabilities and permission from potentially active security
 modules.

 The emulation restricts the functionality of the syscall to
 only allowing the full range I/O port access, but prevents the
 ability to disable interrupts from user space which would be
 granted if the hardware IOPL mechanism would be used.

 Symbol: X86_IOPL_IOPERM [=y]
 Type  : bool
 Prompt: IOPERM and IOPL Emulation
   Location:
     -> Processor type and features
   Defined at arch/x86/Kconfig:1227

---

Cc: David Arcari <darcari@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:49:38 -04:00
Jeremy Cline 66ff6a2d93 [redhat] New configs in drivers/dax
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DEV_DAX_HMEM:

 EFI 2.8 platforms, and others, may advertise 'specific purpose'
 memory. For example, a high bandwidth memory pool. The
 indication from platform firmware is meant to reserve the
 memory from typical usage by default. This driver creates
 device-dax instances for these memory ranges, and that also
 enables the possibility to assign them to the DEV_DAX_KMEM
 driver to override the reservation and add them to kernel
 "System RAM" pool.

 Say M if unsure.

 Symbol: DEV_DAX_HMEM [=m]
 Type  : tristate
 Prompt: HMEM DAX: direct access to 'specific purpose' memory
   Location:
     -> Device Drivers
       -> DAX: direct access to differentiated memory (DAX [=y])
   Defined at drivers/dax/Kconfig:35
   Depends on: DAX [=y] && EFI_SOFT_RESERVE [=y]

---

Cc: Jeff Moyer <jmoyer@redhat.com>
2021-08-30 10:49:38 -04:00
Jeremy Cline f2e80f1451 [redhat] New configs in drivers/dma
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SF_PDMA:

 Support the SiFive PDMA controller.

 Symbol: SF_PDMA [=n]
 Type  : tristate
 Prompt: Sifive PDMA controller driver
   Location:
     -> Device Drivers
       -> DMA Engine support (DMADEVICES [=y])
   Defined at drivers/dma/sf-pdma/Kconfig:1
   Depends on: DMADEVICES [=y]
   Selects: DMA_ENGINE [=y] && DMA_VIRTUAL_CHANNELS [=y]

---
2021-08-30 10:49:38 -04:00
Jeremy Cline 767e8edcef [redhat] New configs in drivers/firmware
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_EFI_SOFT_RESERVE:

 On systems that have mixed performance classes of memory EFI
 may indicate specific purpose memory with an attribute (See
 EFI_MEMORY_SP in UEFI 2.8). A memory range tagged with this
 attribute may have unique performance characteristics compared
 to the system's general purpose "System RAM" pool. On the
 expectation that such memory has application specific usage,
 and its base EFI memory type is "conventional" answer Y to
 arrange for the kernel to reserve it as a "Soft Reserved"
 resource, and set aside for direct-access (device-dax) by
 default. The memory range can later be optionally assigned to
 the page allocator by system administrator policy via the
 device-dax kmem facility. Say N to have the kernel treat this
 memory as "System RAM" by default.

 If unsure, say Y.

 Symbol: EFI_SOFT_RESERVE [=y]
 Type  : bool
 Prompt: Reserve EFI Specific Purpose Memory
   Location:
     -> Firmware Drivers
       -> EFI (Extensible Firmware Interface) Support
   Defined at drivers/firmware/efi/Kconfig:78
   Depends on: EFI [=y] && EFI_STUB [=y] && ACPI_HMAT [=y]

---
2021-08-30 10:49:38 -04:00
Jeremy Cline b8d3994247 [redhat] New configs in drivers/gpu
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DRM_AMD_DC_HDCP:

 Choose this option
 if you want to support
 HDCP authentication

 Symbol: DRM_AMD_DC_HDCP [=n]
 Type  : bool
 Prompt: Enable HDCP support in DC
   Location:
     -> Device Drivers
       -> Graphics support
         -> Display Engine Configuration
   Defined at drivers/gpu/drm/amd/display/Kconfig:47
   Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m] && DRM_AMD_DC [=y]

---

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Cc: Rob Clark <rclark@redhat.com>
2021-08-30 10:49:37 -04:00
Jeremy Cline 2b446f6b35 [redhat] New configs in drivers/hwmon
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SENSORS_BEL_PFE:

 If you say yes here you get hardware monitoring support for BEL
 PFE1100 and PFE3000 Power Supplies.

 This driver can also be built as a module. If so, the module will
 be called bel-pfe.

 Symbol: SENSORS_BEL_PFE [=n]
 Type  : tristate
 Prompt: Bel PFE Compatible Power Supplies
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
         -> PMBus support (PMBUS [=m])
   Defined at drivers/hwmon/pmbus/Kconfig:39
   Depends on: HWMON [=y] && PMBUS [=m]

---

 CONFIG_SENSORS_LTC2947_I2C:

 If you say yes here you get support for Linear Technology LTC2947
 I2C High Precision Power and Energy Monitor

 This driver can also be built as a module. If so, the module will
 be called ltc2947-i2c.

 Symbol: SENSORS_LTC2947_I2C [=n]
 Type  : tristate
 Prompt: Analog Devices LTC2947 High Precision Power and Energy Monitor over I2C
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
   Defined at drivers/hwmon/Kconfig:733
   Depends on: HWMON [=y] && I2C [=y]
   Selects: REGMAP_I2C [=y] && SENSORS_LTC2947 [=n]

---

 CONFIG_SENSORS_LTC2947_SPI:

 If you say yes here you get support for Linear Technology LTC2947
 SPI High Precision Power and Energy Monitor

 This driver can also be built as a module. If so, the module will
 be called ltc2947-spi.

 Symbol: SENSORS_LTC2947_SPI [=n]
 Type  : tristate
 Prompt: Analog Devices LTC2947 High Precision Power and Energy Monitor over SPI
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
   Defined at drivers/hwmon/Kconfig:745
   Depends on: HWMON [=y] && SPI_MASTER [=y]
   Selects: REGMAP_SPI [=y] && SENSORS_LTC2947 [=n]

---

 CONFIG_SENSORS_TMP513:

 If you say yes here you get support for Texas Instruments TMP512,
 and TMP513 temperature and power supply sensor chips.

 This driver can also be built as a module. If so, the module
 will be called tmp513.

 Symbol: SENSORS_TMP513 [=n]
 Type  : tristate
 Prompt: Texas Instruments TMP513 and compatibles
   Location:
     -> Device Drivers
       -> Hardware Monitoring support (HWMON [=y])
   Defined at drivers/hwmon/Kconfig:1739
   Depends on: HWMON [=y] && I2C [=y]

---

Cc: Dean Nelson <dnelson@redhat.com>
2021-08-30 10:49:37 -04:00
Jeremy Cline 27fff652f2 [redhat] New configs in drivers/leds
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_LEDS_EL15203000:

 This option enables support for EL15203000 LED Board
 (aka RED LED board) which is widely used in coffee vending
 machines produced by Crane Merchandising Systems.

 To compile this driver as a module, choose M here: the module
 will be called leds-el15203000.

 Symbol: LEDS_EL15203000 [=n]
 Type  : tristate
 Prompt: LED Support for Crane EL15203000
   Location:
     -> Device Drivers
       -> LED Support (NEW_LEDS [=y])
   Defined at drivers/leds/Kconfig:135
   Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y] && SPI [=y] && OF [=y]

---
2021-08-30 10:49:37 -04:00
Jeremy Cline d7a2d946ec [redhat] New configs in drivers/mmc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MMC_SDHCI_MILBEAUT:

 This selects the Secure Digital Host Controller Interface (SDHCI)
 Needed by Milbeaut SoC for MMC / SD / SDIO support.
 If you have a controller with this interface, say Y or M here.

 If unsure, say N.

 Symbol: MMC_SDHCI_MILBEAUT [=n]
 Type  : tristate
 Prompt: SDHCI support for Socionext Milbeaut Serieas using F_SDH30
   Location:
     -> Device Drivers
       -> MMC/SD/SDIO card support (MMC [=m])
   Defined at drivers/mmc/host/Kconfig:372
   Depends on: MMC [=m] && MMC_SDHCI_PLTFM [=m] && OF [=y]

---
2021-08-30 10:49:37 -04:00
Jeremy Cline e44811a957 [redhat] New configs in drivers/pci
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PCIE_CADENCE_PLAT_HOST:

 Say Y here if you want to support the Cadence PCIe platform controller in
 host mode. This PCIe controller may be embedded into many different
 vendors SoCs.

 Symbol: PCIE_CADENCE_PLAT_HOST [=n]
 Type  : bool
 Prompt: Cadence PCIe platform host controller
   Location:
     -> Device Drivers
       -> PCI support (PCI [=y])
         -> PCI controller drivers
           -> Cadence PCIe controllers support
   Defined at drivers/pci/controller/cadence/Kconfig:24
   Depends on: PCI [=y] && OF [=y]
   Selects: PCIE_CADENCE_HOST [=n] && PCIE_CADENCE_PLAT [=n]

---

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:49:37 -04:00
Jeremy Cline 8f3ffb5895 [redhat] New configs in drivers/platform
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_MLXBF_BOOTCTL:

 The Mellanox BlueField firmware implements functionality to
 request swapping the primary and alternate eMMC boot partition,
 and to set up a watchdog that can undo that swap if the system
 does not boot up correctly. This driver provides sysfs access
 to the userspace tools, to be used in conjunction with the eMMC
 device driver to do necessary initial swap of the boot partition.

 Symbol: MLXBF_BOOTCTL [=n]
 Type  : tristate
 Prompt: Mellanox BlueField Firmware Boot Control driver
   Location:
     -> Device Drivers
       -> Platform support for Mellanox hardware (MELLANOX_PLATFORM [=y])
   Defined at drivers/platform/mellanox/Kconfig:47
   Depends on: MELLANOX_PLATFORM [=y] && ARM64 [=y] && ACPI [=y]

---

 CONFIG_SYSTEM76_ACPI:

 This is a driver for System76 laptops running open firmware. It adds
 support for Fn-Fx key combinations, keyboard backlight, and airplane mode
 LEDs.

 If you have a System76 laptop running open firmware, say Y or M here.

 Symbol: SYSTEM76_ACPI [=n]
 Type  : tristate
 Prompt: System76 ACPI Driver
   Location:
     -> Device Drivers
       -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
   Defined at drivers/platform/x86/Kconfig:1342
   Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y]
   Selects: NEW_LEDS [=y] && LEDS_CLASS [=y] && LEDS_TRIGGERS [=y]

---
2021-08-30 10:49:37 -04:00
Jeremy Cline 47f9a708a1 [redhat] New configs in drivers/soc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_FSL_RCPM:

 The NXP QorIQ Processors based on ARM Core have RCPM module
 (Run Control and Power Management), which performs all device-level
 tasks associated with power management, such as wakeup source control.
 Note that currently this driver will not support PowerPC based
 QorIQ processor.
 Symbol: FSL_RCPM [=n]
 Type  : bool
 Prompt: Freescale RCPM support
   Location:
     -> Device Drivers
       -> SOC (System On Chip) specific Drivers
         -> NXP/Freescale QorIQ SoC drivers
   Defined at drivers/soc/fsl/Kconfig:44
   Depends on: PM_SLEEP [=y] && (ARM || ARM64 [=y])

---
2021-08-30 10:49:36 -04:00
Jeremy Cline b5cfbe955e [redhat] New configs in drivers/usb
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TYPEC_HD3SS3220:

 Say Y or M here if your system has TI HD3SS3220 Type-C DRP Port
 controller driver.

 If you choose to build this driver as a dynamically linked module, the
 module will be called hd3ss3220.ko.

 Symbol: TYPEC_HD3SS3220 [=n]
 Type  : tristate
 Prompt: TI HD3SS3220 Type-C DRP Port controller driver
   Location:
     -> Device Drivers
       -> USB support (USB_SUPPORT [=y])
         -> USB Type-C Support (TYPEC [=y])
   Defined at drivers/usb/typec/Kconfig:53
   Depends on: USB_SUPPORT [=y] && TYPEC [=y] && I2C [=y] && USB_ROLE_SWITCH [=m]

---

Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
2021-08-30 10:49:36 -04:00
Jeremy Cline 1b175feeec [redhat] New configs in drivers/video
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_BACKLIGHT_QCOM_WLED:

 If you have the Qualcomm PMIC, say Y to enable a driver for the
 WLED block. Currently it supports PM8941 and PMI8998.

 Symbol: BACKLIGHT_QCOM_WLED [=n]
 Type  : tristate
 Prompt: Qualcomm PMIC WLED Driver
   Location:
     -> Device Drivers
       -> Graphics support
         -> Backlight & LCD device support
           -> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])
   Defined at drivers/video/backlight/Kconfig:285
   Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y]
   Selects: REGMAP [=y]

---
2021-08-30 10:49:36 -04:00
Jeremy Cline f7b5d74cd5 [redhat] New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_HYPERV_TESTING:

 Select this option to enable Hyper-V vmbus testing.

 Symbol: HYPERV_TESTING [=n]
 Type  : bool
 Prompt: Microsoft Hyper-V driver testing
   Location:
     -> Kernel hacking
   Defined at lib/Kconfig.debug:2159
   Depends on: HYPERV [=m] && DEBUG_FS [=y]

---
2021-08-30 10:49:36 -04:00
Jeremy Cline 8cbbfc1624 Build the SRPM in the CI job
Building the SRPM finds more errors than just building the configs
(which finds unset values) such as configurations that switch values,
missing files, etc.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:36 -04:00
Jeremy Cline 23d8ea29c1 New configs in net/tls
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TLS_TOE:

 Enable kernel support for legacy HW offload of the TLS protocol,
 which is incompatible with the Linux networking stack semantics.

 If unsure, say N.

 Symbol: TLS_TOE [=n]
 Type  : bool
 Prompt: Transport Layer Security TCP stack bypass
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> Transport Layer Security support (TLS [=m])
   Defined at net/tls/Kconfig:30
   Depends on: NET [=y] && TLS [=m]
2021-08-30 10:49:35 -04:00
Jeremy Cline ff2258fb6f New configs in net/tipc
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_TIPC_CRYPTO:

 Saying Y here will enable support for TIPC encryption.
 All TIPC messages will be encrypted/decrypted by using the currently most
 advanced algorithm: AEAD AES-GCM (like IPSec or TLS) before leaving/
 entering the TIPC stack.
 Key setting from user-space is performed via netlink by a user program
 (e.g. the iproute2 'tipc' tool).

 Symbol: TIPC_CRYPTO [=y]
 Type  : bool
 Prompt: TIPC encryption support
   Location:
     -> Networking support (NET [=y])
       -> Networking options
         -> The TIPC Protocol (TIPC [=m])
   Defined at net/tipc/Kconfig:38
   Depends on: NET [=y] && TIPC [=m]
   Selects: CRYPTO [=y] && CRYPTO_AES [=y] && CRYPTO_GCM [=y]
2021-08-30 10:49:35 -04:00
Jeremy Cline 4e0e6a47a6 New configs in lib/kunit
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_KUNIT:

 Enables support for kernel unit tests (KUnit), a lightweight unit
 testing and mocking framework for the Linux kernel. These tests are
 able to be run locally on a developer's workstation without a VM or
 special hardware when using UML. Can also be used on most other
 architectures. For more information, please see
 Documentation/dev-tools/kunit/.

 Symbol: KUNIT [=n]
 Type  : bool
 Prompt: KUnit - Enable support for unit tests
   Location:
     -> Kernel hacking
   Defined at lib/kunit/Kconfig:5
2021-08-30 10:49:35 -04:00
Laura Abbott c9a99bd929 Fix up released_kernel case
We missed adding the release keys for a the released_kernel case.
Add them as well as fixing up a duplicate Source numbering.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:35 -04:00
Jeremy Cline 5ac7164527 New configs in lib/Kconfig.debug
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_SYMBOLIC_ERRNAME:

 If you say Y here, the kernel's printf implementation will
 be able to print symbolic error names such as ENOSPC instead
 of the number 28. It makes the kernel image slightly larger
 (about 3KB), but can make the kernel logs easier to read.

 Symbol: SYMBOLIC_ERRNAME [=y]
 Type  : bool
 Prompt: Support symbolic error names in printf
   Location:
     -> Kernel hacking
       -> printk and dmesg options
   Defined at lib/Kconfig.debug:167
2021-08-30 10:49:35 -04:00
Jeremy Cline 4fb981544d [redhat] New configs in arch/x86
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

CONFIG_X86_INTEL_TSX_MODE_OFF:

TSX is disabled if possible - equals to tsx=off command line parameter.

Symbol: X86_INTEL_TSX_MODE_OFF [=y]
Type  : bool
Prompt: off
  Location:
    -> Processor type and features
      -> TSX enable mode (<choice> [=y])
  Defined at arch/x86/Kconfig:1970
  Depends on: <choice>

---

CONFIG_X86_INTEL_TSX_MODE_ON:

TSX is always enabled on TSX capable HW - equals the tsx=on command
line parameter.

Symbol: X86_INTEL_TSX_MODE_ON [=n]
Type  : bool
Prompt: on
  Location:
    -> Processor type and features
      -> TSX enable mode (<choice> [=y])
  Defined at arch/x86/Kconfig:1975
  Depends on: <choice>

---

CONFIG_X86_INTEL_TSX_MODE_AUTO:

TSX is enabled on TSX capable HW that is believed to be safe against
side channel attacks- equals the tsx=auto command line parameter.
Symbol: X86_INTEL_TSX_MODE_AUTO [=n]
Type  : bool
Prompt: auto
  Location:
    -> Processor type and features
      -> TSX enable mode (<choice> [=y])
  Defined at arch/x86/Kconfig:1981
  Depends on: <choice>

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:35 -04:00
Jeremy Cline ccd9d2bee8 New configs in drivers/ptp
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_PTP_1588_CLOCK_IDTCM:

 This driver adds support for using IDT CLOCKMATRIX(TM) as a PTP
 clock. This clock is only useful if your time stamping MAC
 is connected to the IDT chip.

 To compile this driver as a module, choose M here: the module
 will be called ptp_clockmatrix.

 Symbol: PTP_1588_CLOCK_IDTCM [=n]
 Type  : tristate
 Prompt: IDT CLOCKMATRIX as PTP clock
   Location:
     -> Device Drivers
       -> PTP clock support
   Defined at drivers/ptp/Kconfig:122
   Depends on: PTP_1588_CLOCK [=y]
2021-08-30 10:49:34 -04:00
Jeremy Cline 7b267f42ab New configs in drivers/nvme
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_NVME_HWMON:

 This provides support for NVMe hardware monitoring. If enabled,
 a hardware monitoring device will be created for each NVMe drive
 in the system.

 If unsure, say N.

 Symbol: NVME_HWMON [=n]
 Type  : bool
 Prompt: NVMe hardware monitoring
   Location:
     -> Device Drivers
       -> NVME Support
   Defined at drivers/nvme/host/Kconfig:26
   Depends on: NVME_CORE [=m]=y && HWMON [=y]=y || NVME_CORE [=m]=m && HWMON [=y]
2021-08-30 10:49:34 -04:00
Jeremy Cline d5a4b12e9f New configs in drivers/net/phy
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_DP83869_PHY:

 Currently supports the DP83869 PHY.  This PHY supports copper and
 fiber connections.

 Symbol: DP83869_PHY [=n]
 Type  : tristate
 Prompt: Texas Instruments DP83869 Gigabit PHY
   Location:
     -> Device Drivers
       -> Network device support (NETDEVICES [=y])
         -> PHY Device support and infrastructure (PHYLIB [=y])
   Defined at drivers/net/phy/Kconfig:362
   Depends on: NETDEVICES [=y] && PHYLIB [=y]
2021-08-30 10:49:34 -04:00
Jeremy Cline 603828c8db New configs in arch/arm64
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_ARM64_ERRATUM_1319367:

 This option adds work arounds for ARM Cortex-A57 erratum 1319537
 and A72 erratum 1319367

 Cortex-A57 and A72 cores could end-up with corrupted TLBs by
 speculating an AT instruction during a guest context switch.

 If unsure, say Y.

 Symbol: ARM64_ERRATUM_1319367 [=y]
 Type  : bool
 Prompt: Cortex-A57/A72: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation
   Location:
     -> Kernel Features
       -> ARM errata workarounds via the alternatives framework
   Defined at arch/arm64/Kconfig:547
2021-08-30 10:49:34 -04:00
Jeremy Cline ec84ba0756 New configs in drivers/crypto
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CRYPTO_DEV_AMLOGIC_GXL:

 Select y here to have support for the cryptographic offloader
 available on Amlogic GXL SoC.
 This hardware handles AES ciphers in ECB/CBC mode.

 To compile this driver as a module, choose M here: the module
 will be called amlogic-gxl-crypto.

 Symbol: CRYPTO_DEV_AMLOGIC_GXL [=n]
 Type  : tristate
 Prompt: Support for amlogic cryptographic offloader
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Hardware crypto devices (CRYPTO_HW [=y])
   Defined at drivers/crypto/amlogic/Kconfig:1
   Depends on: CRYPTO [=y] && CRYPTO_HW [=y]
   Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_ENGINE [=n] && CRYPTO_ECB [=y] && CRYPTO_CBC [=y] && CRYPTO_AES [=y]
2021-08-30 10:49:34 -04:00
Jeremy Cline 25b1b757f9 New configs in crypto/Kconfig
Hi,

As part of the ongoing rebase effort, the following configuration
options need to be reviewed.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

 CONFIG_CRYPTO_BLAKE2B:

 Implementation of cryptographic hash function BLAKE2b (or just BLAKE2),
 optimized for 64bit platforms and can produce digests of any size
 between 1 to 64.  The keyed hash is also implemented.

 This module provides the following algorithms:

 - blake2b-160
 - blake2b-256
 - blake2b-384
 - blake2b-512

 See https://blake2.net for further information.

 Symbol: CRYPTO_BLAKE2B [=n]
 Type  : tristate
 Prompt: BLAKE2b digest algorithm
   Location:
     -> Cryptographic API (CRYPTO [=y])
   Defined at crypto/Kconfig:653
   Depends on: CRYPTO [=y]
   Selects: CRYPTO_HASH [=y]
2021-08-30 10:49:34 -04:00
Jeremy Cline 150fd04d3f Add label so the Gitlab to email bridge ignores the changelog
Emailing the automated changelog generation patch to a list would be
pointless so mark the merge request as ignored.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:33 -04:00
Laura Abbott a44f2a495f [redhat] configs: Sync Fedora configs
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:33 -04:00
Jeremy Cline 9937e91803 Temporarily switch TUNE_DEFAULT to y
Upstream added a dependency on an s390x compiler in the configuration
environment. Adjust the config to not break when prepped on x86 until
upstream discusses what to do.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:33 -04:00
Jeremy Cline b2c8bee975 Run config test for merge requests and internal
This alters the CI job that checks that the configuration is valid to
only trigger when a merge request is made or a push to
internal occurs.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:33 -04:00
Jeremy Cline f2c759831d [redhat] AUTOMATIC: New configs 2021-08-30 10:49:33 -04:00
Jeremy Cline 5d16d011ed [redhat] AUTOMATIC: New configs 2021-08-30 10:49:32 -04:00
Laura Abbott 5b6720524f Add missing licensedir line
This got deleted during some cleanup

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:32 -04:00
Jeremy Cline 9793bea594 [redhat] AUTOMATIC: New configs 2021-08-30 10:49:32 -04:00
Prarit Bhargava 3c3cfdc112 redhat/scripts: Remove redhat/scripts/rh_get_maintainer.pl
Message-id: <20190917154218.29293-1-prarit@redhat.com>
Patchwork-id: 272312
O-Subject: [ARK INTERNAL] redhat/scripts: Remove redhat/scripts/rh_get_maintainer.pl
Bugzilla:
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

rh_get_maintainer.pl is a lightly modified version of get_maintainer.pl
from 3.10.0-ish.  The script should be dropped in favor of using
the upstream version, and also dropped from being forward ported.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>

Cc: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Augusto Caringi <acaringi@redhat.com>
Cc: Luis Claudio Goncalves <lgoncalv@redhat.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Laura Abbott <labbott@redhat.com>
Cc: Jeremy Cline <jcline@redhat.com>
Cc: Rado Vrbovsky <rvrbovsk@redhat.com>
Cc: Phillip Lougher <plougher@redhat.com>
Cc: Juri Lelli <jlelli@redhat.com>
Cc: Jan Stancek <jstancek@redhat.com>
Cc: "Bruno E. O. Meneguele" <bmeneg@redhat.com>
Cc: "Herton R. Krzesinski" <herton@redhat.com>

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:32 -04:00
Laura Abbott f6ddc6c9d7 configs: Take CONFIG_DEFAULT_MMAP_MIN_ADDR from Fedra
Message-id: <20191121190831.8942-1-labbott@redhat.com>
Patchwork-id: 287873
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Take CONFIG_DEFAULT_MMAP_MIN_ADDR from Fedra
Bugzilla:
RH-Acked-by: Rafael Aquini <aquini@redhat.com>

Fedora has had a bigger CONFIG_DEFAULT_MMAP_MIN_ADDR value for
a number of years now. Use the suggested values in the help text
for arm and x86_64.

Cc: Prarit Bhargava <prarit@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Cc: Mark Salter <msalter@redhat.com>
Cc: Larry Woodman <lwoodman@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
This is exactly what Fedora was using although I realize this doesn't
include powerpc or s390x.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:32 -04:00
Laura Abbott f4dd97c57f configs: Turn off ISDN
Message-id: <20191121191829.30226-1-labbott@redhat.com>
Patchwork-id: 287874
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Turn off ISDN
Bugzilla:
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: John Linville <linville@redhat.com>

This is slowly going away upstream. Nobody seems to want it so just
turn it off.

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: John W. Linville <linville@redhat.com>
Signed-off-by: Laura Abbott <labbott@redhat.com>
---
I know we're still waiting to hear back from the BU but if there's
general agreement this is what we want let's just turn it off. It's
really cheap to turn it back on later.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:31 -04:00
Laura Abbott 198c2edc7b Add a script to generate configuration patches
After generating an initial set of commits in the pending directory,
we need to split that out into individual commits for review. Add
a script to do so. This script is designed to be run from the
root of the kernel tree so we can run get_maintainers.pl if the
appropriate maintainers file is available.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:31 -04:00
Laura Abbott 560d9806d0 Introduce rh-configs-commit
One of the tasks that comes with maintaining ARK is dealing with new
configuration options that come in. We need to set an initial value
for building a kernel and then allow for a final review of the options.
This has been managed by out of tree scripts for a while but to make
automation easier, bring part of this in tree.

Introduce the rh-configs-commit make target. This runs 'make helpnewconfig'
(like listnewconfig execpt it shows the help text) and puts all
the new configuration options in the pending directory. Moving those
options out of the pending directory will be a separate step.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:31 -04:00
Prarit Bhargava 3fa5132db0 kernel-packaging: Remove kernel files from kernel-modules-extra package
This fixup was missed.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:31 -04:00
Laura Abbott d0dcd7f865 configs: Enable CONFIG_DEBUG_WX
Message-id: <20191120193123.19432-1-labbott@redhat.com>
Patchwork-id: 287796
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Enable CONFIG_DEBUG_WX
Bugzilla:
RH-Acked-by: Rafael Aquini <aquini@redhat.com>

The purpose of CONFIG_DEBUG_WX is to check for pages that are both
writable and executable. This is a one time check that happens at
bootup. Given this is an important check to catch either bad patches
or occasionally bad firmware, enable this on all arches.

Signed-off-by: Laura Abbott <labbott@redhat.com>
---
This is an option that's been on in Fedora without a problem. It
has definitely caught problems in the past. Given it's a onetime
cost, I think it would be safe to keep on but I also don't know
if it's been evaluated on large memory systems since it does
walk all mapped pages.

As a counter proposal, it might be appropriate for the debug
kernel.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:30 -04:00
Laura Abbott 39fbf10499 configs: Disable wireless USB
Message-id: <20191120162742.14094-1-labbott@redhat.com>
Patchwork-id: 287792
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: Disable wireless USB
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>

Fedora disabled this earlier this year because it's being
deprecated (and hardware doesn't actually exist):

commit 559debe56a8b286d8484b0b45e910ca5592ce6ad
Author: Peter Robinson <pbrobinson@gmail.com>
Date:   Sun Jun 16 11:59:22 2019 +0100

    disable WUSB (Wireless USB) as HW doesn't exist

    It's soon to move to staging in preparation for removal:
    https://www.spinics.net/lists/linux-crypto/msg39327.html

Upstream is still telling people not to bother fixing issues
so let's just turn it off.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:30 -04:00
Laura Abbott 4b751e9fb7 Clean up some temporary config files
Message-id: <20191119210034.4019-1-labbott@redhat.com>
Patchwork-id: 287761
O-Subject: [ARK INTERNAL PATCHv2] [redhat] Clean up some temporary config files
Bugzilla:
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>

As part of running process_configs.sh, we generate some temporary files
for processing. If we find an error somewhere (unset configs, mismatch),
the temporary files don't get cleaned up. Make sure these do get removed.

Signed-off-by: Laura Abbott <labbott@redhat.com>
---
v2: Use a single rm call instead of multiple
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:30 -04:00
Jeremy Cline 12151f2be8 configs: New config in drivers/gpu for v5.4-rc1
Message-id: <20191113152525.107866-1-jcline@redhat.com>
Patchwork-id: 286082
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in drivers/gpu for v5.4-rc1
Bugzilla:
RH-Acked-by: Dave Airlie <airlied@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/gpu/drm/amd/display/Kconfig (help): DRM_AMD_DC_DCN2_1 (bool)
    Choose this option if you want to have
    Renoir support for display engine
* drivers/gpu/drm/tiny/Kconfig (help): DRM_GM12U320 (tristate)
    This is a KMS driver for projectors which use the GM12U320 chipset
    for video transfer over USB2/3, such as the Acer C120 mini projector.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_LG_LB035Q02 (tristate)
    Say Y here if you want to enable support for the LB035Q02 RGB panel
    (found on the Gumstix Overo Palo35 board). To compile this driver as
    a module, choose M here.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_NEC_NL8048HL11 (tristate)
    Say Y here if you want to enable support for the NEC NL8048HL11 RGB
    panel (found on the Zoom2/3/3630 SDP boards). To compile this driver
    as a module, choose M here.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_NOVATEK_NT39016 (tristate)
    Say Y here if you want to enable support for the panels built
    around the Novatek NT39016 display controller.
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_SONY_ACX565AKM (tristate)
    Say Y here if you want to enable support for the Sony ACX565AKM
    800x600 3.5" panel (found on the Nokia N900).
* drivers/gpu/drm/panel/Kconfig (help): DRM_PANEL_TPO_TD028TTEC1 (tristate)
    Say Y here if you want to enable support for TPO TD028TTEC1 480x640
    2.8" panel (found on the OpenMoko Neo FreeRunner and Neo 1973).
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_HX8357D (tristate)
    DRM driver for the following HX8357D panels:
    * YX350HV15-T 3.5" 340x350 TFT (Adafruit 3.5")

    If M is selected the module will be called hx8357d.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ILI9225 (tristate)
    DRM driver for the following Ilitek ILI9225 panels:
    * No-name 2.2" color screen module

    If M is selected the module will be called ili9225.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ILI9341 (tristate)
    DRM driver for the following Ilitek ILI9341 panels:
    * YX240QV29-T 2.4" 240x320 TFT (Adafruit 2.4")

    If M is selected the module will be called ili9341.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_MI0283QT (tristate)
    DRM driver for the Multi-Inno MI0283QT display panel
    If M is selected the module will be called mi0283qt.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_REPAPER (tristate)
    DRM driver for the following Pervasive Displays panels:
    1.44" TFT EPD Panel (E1144CS021)
    1.90" TFT EPD Panel (E1190CS021)
    2.00" TFT EPD Panel (E2200CS021)
    2.71" TFT EPD Panel (E2271CS021)

    If M is selected the module will be called repaper.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ST7586 (tristate)
    DRM driver for the following Sitronix ST7586 panels:
    * LEGO MINDSTORMS EV3

    If M is selected the module will be called st7586.
* drivers/gpu/drm/tiny/Kconfig (help): TINYDRM_ST7735R (tristate)
    DRM driver Sitronix ST7735R with one of the following LCDs:
    * JD-T18003-T01 1.8" 128x160 TFT

    If M is selected the module will be called st7735r.

Cc: David Airlie <airlied@redhat.com>
Cc: Adam Jackson <ajax@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
---
Changes in v2:
  - DRM_GM12U320 is now m
  - DRM_AMD_DC_DCN2_1 is  y for x86

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:30 -04:00
Jeremy Cline cf640faf09 configs: New config in arch/powerpc for v5.4-rc1
Message-id: <20191021163940.28422-1-jcline@redhat.com>
Patchwork-id: 280558
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in arch/powerpc for v5.4-rc1
Bugzilla:
RH-Acked-by: Steve Best <sbest@redhat.com>
RH-Acked-by: Laurent Vivier <lvivier@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* arch/powerpc/platforms/pseries/Kconfig (help): PPC_SVM (bool)
    There are certain POWER platforms which support secure guests using
    the Protected Execution Facility, with the help of an Ultravisor
    executing below the hypervisor layer. This enables support for
    those guests.

    If unsure, say "N".
* arch/powerpc/Kconfig (help): OPAL_CORE (bool)
    This option uses the MPIPL support in firmware to provide an
    ELF core of OPAL memory after a crash. The ELF core is exported
    as /sys/firmware/opal/core file which is helpful in debugging
    OPAL crashes using GDB.

Cc: David Gibson <dgibson@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:30 -04:00
Jeremy Cline 915d5d3f74 configs: New config in crypto for v5.4-rc1
Message-id: <20191014162300.16308-3-jcline@redhat.com>
Patchwork-id: 278876
O-Subject: [ARK INTERNAL PATCH] configs: New config in crypto for v5.4-rc1
Bugzilla:
RH-Acked-by: Ondrej Mosnacek <omosnace@redhat.com>
RH-Acked-by: Herbert Xu <herbert.xu@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* crypto/Kconfig (help): CRYPTO_ESSIV (tristate)
    Encrypted salt-sector initialization vector (ESSIV) is an IV
    generation method that is used in some cases by fscrypt and/or
    dm-crypt. It uses the hash of the block encryption key as the
    symmetric key for a block encryption pass applied to the input
    IV, making low entropy IV sources more suitable for block
    encryption.

    This driver implements a crypto API template that can be
    instantiated either as a skcipher or as a aead (depending on the
    type of the first template argument), and which defers encryption
    and decryption requests to the encapsulated cipher after applying
    ESSIV to the input IV. Note that in the aead case, it is assumed
    that the keys are presented in the same format used by the authenc
    template, and that the IV appears at the end of the authenticated
    associated data (AAD) region (which is how dm-crypt uses it.)

    Note that the use of ESSIV is not recommended for new deployments,
    and so this only needs to be enabled when interoperability with
    existing encrypted volumes of filesystems is required, or when
    building for a particular system that requires it (e.g., when
    the SoC in question has accelerated CBC but not XTS, making CBC
    combined with ESSIV the only feasible mode for h/w accelerated
    block encryption)

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:29 -04:00
Jeremy Cline eef96d75fd configs: New config in drivers/usb for v5.4-rc1
Message-id: <20190918194258.8325-1-jcline@redhat.com>
Patchwork-id: 272492
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/usb for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/usb/cdns3/Kconfig (help): USB_CDNS3 (tristate)
    Say Y here if your system has a Cadence USB3 dual-role controller.
    It supports: dual-role switch, Host-only, and Peripheral-only.

    If you choose to build this driver is a dynamically linked
    as module, the module will be called cdns3.ko.
* drivers/usb/common/Kconfig (help): USB_CONN_GPIO (tristate)
    The driver supports USB role switch between host and device via GPIO
    based USB cable detection, used typically if an input GPIO is used
    to detect USB ID pin, and another input GPIO may be also used to detect
    Vbus pin at the same time, it also can be used to enable/disable
    device if an input GPIO is only used to detect Vbus pin.

    To compile the driver as a module, choose M here: the module will
    be called usb-conn-gpio.ko

Cc: Torez Smith <torez@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:29 -04:00
Jeremy Cline 8b6d288195 AUTOMATIC: New configs 2021-08-30 10:49:29 -04:00
Laura Abbott 8055b9589b [redhat] Align some configs for Fedora
Because of the nature of keeping two sets of configs, the
Fedora configs in this tree are out of sync with work
that's happening in the official Fedora dist-git repo.
Bring this back in sync.

As part of this work, prune a bunch of dead configuration
options. None of the changes meaningfully affect the generated
config output for ARK as compared against the full configs in the
srpms.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:29 -04:00
Jeremy Cline 8d14fb7bba Skip ksamples for bpf, they are broken
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:26 -04:00
Laura Abbott 901bd16ad5 [redhat] Make sure aarch64 picks up the arm directory
In addition to picking up the aarch64 directory, pick up
the base arm directory for sharing.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:25 -04:00
Jeremy Cline 965c615e9f configs: New config in fs/erofs for v5.4-rc1
Message-id: <20190918194309.8503-1-jcline@redhat.com>
Patchwork-id: 272491
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in fs/erofs for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* fs/erofs/Kconfig (help): EROFS_FS (tristate)
    EROFS (Enhanced Read-Only File System) is a lightweight
    read-only file system with modern designs (eg. page-sized
    blocks, inline xattrs/data, etc.) for scenarios which need
    high-performance read-only requirements, e.g. Android OS
    for mobile phones and LIVECDs.

    It also provides fixed-sized output compression support,
    which improves storage density, keeps relatively higher
    compression ratios, which is more useful to achieve high
    performance for embedded devices with limited memory.

    If unsure, say N.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:25 -04:00
Jeremy Cline fbc9cdfa60 configs: New config in mm for v5.4-rc1
Message-id: <20191014162300.16308-21-jcline@redhat.com>
Patchwork-id: 278886
O-Subject: [ARK INTERNAL PATCH] configs: New config in mm for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* mm/Kconfig (help): READ_ONLY_THP_FOR_FS (bool)
    Allow khugepaged to put read-only file-backed pages in THP.

    This is marked experimental because it is a new feature. Write
    support of file THPs will be developed in the next few release
    cycles.

Cc: Larry Woodman <lwoodman@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Dean Nelson <dnelson@redhat.com>
Cc: Steve Best <sbest@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:25 -04:00
Jeremy Cline e630beabe6 configs: New config in drivers/md for v5.4-rc1
Message-id: <20191111151627.73663-1-jcline@redhat.com>
Patchwork-id: 285197
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in drivers/md for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/md/Kconfig (help): DM_CLONE (tristate)
    dm-clone produces a one-to-one copy of an existing, read-only source
    device into a writable destination device. The cloned device is
    visible/mountable immediately and the copy of the source device to the
    destination device happens in the background, in parallel with user
    I/O.

    If unsure, say N.
* drivers/md/Kconfig (help): DM_VERITY_VERIFY_ROOTHASH_SIG (bool)
    Add ability for dm-verity device to be validated if the
    pre-generated tree of cryptographic checksums passed has a pkcs#7
    signature file that can validate the roothash of the tree.

    If unsure, say N.

Cc: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>
Cc: Jonathan Brassow <jbrassow@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:25 -04:00
Jeremy Cline 35ccac2b3d configs: New config in init for v5.4-rc1
Message-id: <20191014162300.16308-19-jcline@redhat.com>
Patchwork-id: 278894
O-Subject: [ARK INTERNAL PATCH] configs: New config in init for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* init/Kconfig (help): MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS (bool)
    Symbols exported with EXPORT_SYMBOL_NS*() are considered exported in
    a namespace. A module that makes use of a symbol exported with such a
    namespace is required to import the namespace via MODULE_IMPORT_NS().
    There is no technical reason to enforce correct namespace imports,
    but it creates consistency between symbols defining namespaces and
    users importing namespaces they make use of. This option relaxes this
    requirement and lifts the enforcement when loading a module.

    If unsure, say N.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:25 -04:00
Laura Abbott 1d681c6151 [redhat] configs: Set appropriate values for CONFIG_RH_DISABLE_DEPRECATED
Message-id: <20191113144431.9403-3-labbott@redhat.com>
Patchwork-id: 286077
O-Subject: [ARK INTERNAL PATCHv2 2/4] [redhat] configs: Set appropriate values for CONFIG_RH_DISABLE_DEPRECATED
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

Allow ARK to use the various deprecation interace but let Fedora
work as normal.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:25 -04:00
Jeremy Cline 45c5a4727f configs: New config in fs/fuse for v5.4-rc1
Message-id: <20191104195711.611286-1-jcline@redhat.com>
RH-Acked-by: Vivek Goyal <vgoyal@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* fs/fuse/Kconfig (help): VIRTIO_FS (tristate)
    The Virtio Filesystem allows guests to mount file systems from the
    host.

    If you want to share files between guests or with the host, answer Y
    or M.

Cc: Brian Foster <bfoster@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:24 -04:00
Don Zickus edff599cce merge.pl: Avoid comments but do not skip them
In RHEL-8, we needed to handle a config comment that had a config name inside
the comment.  For example:

 # Please do not use CONFIG_FOO=y because it breaks things

This comment caused merge.pl to set CONFIG_FOO equal to 'y' in the output
accidentally.  To avoid this, the easy solution was to skip all comments
in the merged output.  However, this breaks Fedora's trick to apply last
minute configs with kernel-local.

By dropping the comments, the '# <arch>' header goes missing, confusing the
tools about which arch to apply the configs for.

Modify the original solution from dropping comments to avoiding the
accidental processing of the CONFIG_FOO=y line.  This is accomplished by
checking for a comment and falling through thus avoiding the '=' check
in the next else statement (and the source of the problem).

Tested by building a srpm using a kernel-local file.
Acked-by: Prarit Bhargava <prarit@redhat.com>
Acked-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:24 -04:00
Jeremy Cline 91dd94a35e configs: New config in drivers/net/ethernet/pensando for v5.4-rc1
Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/net/ethernet/pensando/Kconfig (help): IONIC (tristate)
    This enables the support for the Pensando family of Ethernet
    adapters.  More specific information on this driver can be
    found in
    <file:Documentation/networking/device_drivers/pensando/ionic.rst>.

    To compile this driver as a module, choose M here. The module
    will be called ionic.
* drivers/net/ethernet/pensando/Kconfig (help): NET_VENDOR_PENSANDO (bool)
    If you have a network (Ethernet) card belonging to this class, say Y.

    Note that the answer to this question doesn't directly affect the
    kernel: saying N will just cause the configurator to skip all
    the questions about Pensando cards. If you say Y, you will be asked
    for your specific card in the following questions.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Neil Horman <nhorman@redhat.com>
2021-08-30 10:49:24 -04:00
Laura Abbott 18b960646b Update a comment about what released kernel means
Add a definition that makes sense for both Fedora and RHEL.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:24 -04:00
Laura Abbott f28f383104 Provide both Fedora and RHEL files in the SRPM
Currently, we've been switching between copying Fedora and RHEL files
based on dist-tag. Long term, we want to have a single tree to manage
both Fedora and RHEL. Move towards this by shipping both RHEL and
Fedora files in a single RPM. The choice of which set of files to use
gets decided at build time based on the buildroot.

This series is a big large but it's not easy to break up simply because
making one change requires making all the other changes to avoid breaking
anything. The big changes:

- Move some files and scripts to have the .fedora or .rhel extension
- Tweak some of the config scripts to accont for a fedora/rhel extension
- spec file changes to account for these changes

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:24 -04:00
Laura Abbott 468d9c6ff1 kernel.spec.template: Trim EXTRAVERSION in the Makefile
As per the Fedora commit:

    The CI build currently adds the full git commit hash to the release of
    the RPM it builds. This breaks the kernel build as the EXTRAVERSION
    cannot exceed 64 characters.

    This sets the EXTRAVERSION to whatever the release was minus
    ".pr.<hash>".

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:23 -04:00
Laura Abbott b771a658a0 kernel.spec.template: Add macros for building with nopatches
Fedora has an option to build without any extra patches. Bring in
this option to ARK as well.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:23 -04:00
Laura Abbott 1500d37ea9 kernel.spec.template: Add some macros for Fedora differences
For various reasons usually releated to architectures, Fedora builds
some things slightly differently. Adjust accordingly.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:23 -04:00
Laura Abbott f4bf02b6ff kernel.spec.template: Consolodate the options
In the interest of making things easier to read, consolodate all the
make options into a single location in the file. Also switch to
using the standard cflags and ldflags options.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:23 -04:00
Laura Abbott 4781cb3f8d configs: Add pending direcory to Fedora
The original design for the common set of configs had Fedora
not using the pending directory. The goal now is to have both
Fedora + RHEL configs in the same tree. With that goal in mind,
let Fedora use the pending directory as well. At the same time,
fixup some other Fedora configuration options that are broken
(once we build for both Fedora and RHEL this will stop being
broken so much)

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:23 -04:00
Laura Abbott 3447b77fab kernel.spec.template: Don't run hardlink if rpm-ostree is in use
>From the people on the OSTree side:

    OSTree is a far, far more sophisticated wrapper around the `link()`
    system call than the `hardlink` package - it supports using
    as a mechanism for transactional offline updates, fetching over
    HTTP with GPG signatures and deltas, etc.  rpm-ostree uses it
    for everything.

    Having the `kernel-devel` package run `hardlink` just adds
    latency to `rpm-ostree compose tree` unnecessarily.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Acked-by: Don Zickus <dzickus@redhat.com>
2021-08-30 10:49:23 -04:00
Jeremy Cline c7dbfb9297 configs: New config in net/can for v5.4-rc1
Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* net/can/j1939/Kconfig (help): CAN_J1939 (tristate)
    SAE J1939
    Say Y to have in-kernel support for j1939 socket type. This
    allows communication according to SAE j1939.
    The relevant parts in kernel are
    SAE j1939-21 (datalink & transport protocol)
    & SAE j1939-81 (network management).

Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 10:49:22 -04:00
Jeremy Cline 3aa7890e60 configs: New config in drivers/net/phy for v5.4-rc1
Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/net/phy/Kconfig (help): ADIN_PHY (tristate)
    Adds support for the Analog Devices Industrial Ethernet PHYs.
    Currently supports the:
    - ADIN1200 - Robust,Industrial, Low Power 10/100 Ethernet PHY
    - ADIN1300 - Robust,Industrial, Low Latency 10/100/1000 Gigabit
      Ethernet PHY

Cc: Petr Oros <poros@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Jiri Benc <jbenc@redhat.com>
2021-08-30 10:49:22 -04:00
Prarit Bhargava 57cb925178 configs: Increase x86_64 NR_UARTS to 64
Bugzilla: http://bugzilla.redhat.com/1730649

Upstream Status: RHEL only

We have a long time customer that requires 64 UARTS.

Increase the number of UARTS to 64 on x86_64, and add a comment to the
config file.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-08-30 10:49:22 -04:00
Laura Abbott 4f5a541bfe [redhat] Update CI to bring changelog back to internal
Because of the way ARK flows, the changelog only gets committed
to the master branch. Since master gets overwritten each rebase,
we lose the history we need. Automate bringing the information
for the changelog back to internal.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:22 -04:00
Jeremy Cline ac99a0a9f7 configs: turn on ARM64_FORCE_52BIT for debug builds
Message-id: <20191001181211.19739-1-jcline@redhat.com>
Patchwork-id: 275497
O-Subject: [ARK INTERNAL PATCH] configs: turn on ARM64_FORCE_52BIT for debug builds
Bugzilla:
RH-Acked-by: Mark Salter <msalter@redhat.com>

Turn on ARM64_FORCE_52BIT on the debug kernel in order to turn up 52-bit
bugs.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
Acked-by: Mark Salter <msalter@redhat.com>
2021-08-30 10:49:22 -04:00
Laura Abbott 496ea68bef kernel.spec.template: Tweak the python3 mangling
Message-id: <20191022125201.32538-3-labbott@redhat.com>
Patchwork-id: 280638
O-Subject: [ARK INTERNAL PATCH 2/8] [redhat] kernel.spec.template: Tweak the python3 mangling
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

Tweak the python3 mangling message to be a bit clearer about what
exactly we are doing and remove referneces to RHEL8. Also pick up
other python3 environment flags.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:21 -04:00
Laura Abbott 64d893dcab kernel.spec.template: Add --with verbose option
Message-id: <20191022125201.32538-9-labbott@redhat.com>
Patchwork-id: 280635
O-Subject: [ARK INTERNAL PATCH 8/8] [redhat] kernel.spec.template: Add --with verbose option
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

By default the kernel builds are silent because otherwise there
would be too much noise. Sometimes it's useful to see the full
output. Add a --with verbose option to build without -s.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:21 -04:00
Laura Abbott a67c7e5a07 kernel.spec.template: Switch to using %install instead of %__install
Message-id: <20191022125201.32538-8-labbott@redhat.com>
Patchwork-id: 280634
O-Subject: [ARK INTERNAL PATCH 7/8] [redhat] kernel.spec.template: Switch to using %install instead of %__install
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

This matches what Fedora has and there's no reason to use the
internal one.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:21 -04:00
Laura Abbott 511bae6e8f kernel.spec.template: Make the kernel.org URL https
Message-id: <20191022125201.32538-7-labbott@redhat.com>
Patchwork-id: 280637
O-Subject: [ARK INTERNAL PATCH 6/8] [redhat] kernel.spec.template: Make the kernel.org URL https
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

It's 2019 and everyone should be running https. Match what Fedora uses
and use the https URL.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:21 -04:00
Laura Abbott a81729b2c1 kernel.spec.template: Update message about secure boot signing
Message-id: <20191022125201.32538-6-labbott@redhat.com>
Patchwork-id: 280636
O-Subject: [ARK INTERNAL PATCH 5/8] [redhat] kernel.spec.template: Update message about secure boot signing
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

We now sign on multiple arches besides x86_64. Update the message to
be agnostic.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:21 -04:00
Laura Abbott e4337e4741 kernel.spec.template: Move some with flags definitions up
Message-id: <20191022125201.32538-2-labbott@redhat.com>
Patchwork-id: 280631
O-Subject: [ARK INTERNAL PATCH 1/8] [redhat] kernel.spec.template: Move some with flags definitions up
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

Move gcov and ipaclones to be with the reset of the with flag
defintions for ease of review.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:21 -04:00
Laura Abbott 957f5ba2cf kernel.spec.template: Update some BuildRequires
Message-id: <20191022125201.32538-5-labbott@redhat.com>
Patchwork-id: 280633
O-Subject: [ARK INTERNAL PATCH 4/8] [redhat] kernel.spec.template: Update some BuildRequires
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

Re-arrange a few build requires to sync up with Fedora. The only
real change is git -> git-core.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:20 -04:00
Laura Abbott b58d6c9b62 kernel.spec.template: Get rid of %clean
Message-id: <20191022125201.32538-4-labbott@redhat.com>
Patchwork-id: 280632
O-Subject: [ARK INTERNAL PATCH 3/8] [redhat] kernel.spec.template: Get rid of %clean
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

The basic clean is already defined so there's no need to redefine it
again. Just remove it.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:20 -04:00
Jeremy Cline 0bb0ebe3da configs: New config in drivers/char for v5.4-rc1
Message-id: <20190918194048.6650-1-jcline@redhat.com>
Patchwork-id: 272483
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/char for v5.4-rc1
Bugzilla:
RH-Acked-by: Jerry Snitselaar <jsnitsel@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/char/Kconfig (help): RANDOM_TRUST_BOOTLOADER (bool)
    Some bootloaders can provide entropy to increase the kernel's initial
    device randomness. Say Y here to assume the entropy provided by the
    booloader is trustworthy so it will be added to the kernel's entropy
    pool. Otherwise, say N here so it will be regarded as device input that
    only mixes the entropy pool.

Cc: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: George Beshers <gbeshers@redhat.com>
Cc: Frank Ramsay <framsay@redhat.com>
Cc: Russ Anderson <randerso@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:20 -04:00
Jeremy Cline b24c4b9984 configs: New config in net/sched for v5.4-rc1
Message-id: <20191021170608.8971-1-jcline@redhat.com>
Patchwork-id: 280561
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in net/sched for v5.4-rc1
Bugzilla:
RH-Acked-by: Jiri Benc <jbenc@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* net/sched/Kconfig (help): NET_TC_SKB_EXT (bool)
    Say Y here to allow tc chain misses to continue in OvS datapath in
    the correct recirc_id, and hardware chain misses to continue in
    the correct chain in tc software datapath.

    Say N here if you won't be using tc<->ovs offload or tc chains offload.

Cc: Ivan Vecera <ivecera@redhat.com>
Cc: Jiri Benc <jbenc@redhat.com>
Cc: Rashid Khan <rkhan@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:20 -04:00
Jeremy Cline 3995f1394b configs: New config in lib for v5.4-rc1
Message-id: <20191021170136.3374-1-jcline@redhat.com>
Patchwork-id: 280560
O-Subject: [ARK INTERNAL PATCHv2] configs: New config in lib for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* lib/Kconfig.debug (help): DEBUG_KMEMLEAK_MEM_POOL_SIZE (int)
    Kmemleak must track all the memory allocations to avoid
    reporting false positives. Since memory may be allocated or
    freed before kmemleak is fully initialised, use a static pool
    of metadata objects to track such callbacks. After kmemleak is
    fully initialised, this memory pool acts as an emergency one
    if slab allocations fail.

Note: this configuration is a rename of DEBUG_KMEMLEAK_EARLY_LOG_SIZE
done in commit c566586818 ("mm: kmemleak: use the memory pool for
early allocations")

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:20 -04:00
Jeremy Cline 84d3cbc67e configs: New config in fs/verity for v5.4-rc1
Message-id: <20191014162300.16308-18-jcline@redhat.com>
Patchwork-id: 278893
O-Subject: [ARK INTERNAL PATCH] configs: New config in fs/verity for v5.4-rc1
Bugzilla:
RH-Acked-by: Eric Sandeen <esandeen@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* fs/verity/Kconfig (help): FS_VERITY (bool)
    This option enables fs-verity.  fs-verity is the dm-verity
    mechanism implemented at the file level.  On supported
    filesystems (currently EXT4 and F2FS), userspace can use an
    ioctl to enable verity for a file, which causes the filesystem
    to build a Merkle tree for the file.  The filesystem will then
    transparently verify any data read from the file against the
    Merkle tree.  The file is also made read-only.

    This serves as an integrity check, but the availability of the
    Merkle tree root hash also allows efficiently supporting
    various use cases where normally the whole file would need to
    be hashed at once, such as: (a) auditing (logging the file's
    hash), or (b) authenticity verification (comparing the hash
    against a known good value, e.g. from a digital signature).

    fs-verity is especially useful on large files where not all
    the contents may actually be needed.  Also, fs-verity verifies
    data each time it is paged back in, which provides better
    protection against malicious disks vs. an ahead-of-time hash.

    If unsure, say N.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:20 -04:00
Jeremy Cline 2876be8c65 configs: New config in arch/aarch64 for v5.4-rc4
Message-id: <20191021163129.22377-1-jcline@redhat.com>
Patchwork-id: 280557
O-Subject: [ARK INTERNAL PATCH] configs: New config in arch/aarch64 for v5.4-rc4
Bugzilla:
RH-Acked-by: Mark Salter <msalter@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc4, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* config CAVIUM_TX2_ERRATUM_219
    bool "Cavium ThunderX2 erratum 219: PRFM between TTBR change and ISB fails"
    default y
    help
        On Cavium ThunderX2, a load, store or prefetch instruction between a
        TTBR update and the corresponding context synchronizing operation can
        cause a spurious Data Abort to be delivered to any hardware thread in
        the CPU core.

        Work around the issue by avoiding the problematic code sequence and
        trapping KVM guest TTBRx_EL1 writes to EL2 when SMT is enabled. The
        trap handler performs the corresponding register access, skips the
        instruction and ensures context synchronization by virtue of the
        exception return.

        If unsure, say Y.

Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:19 -04:00
Jeremy Cline 1177bac981 configs: New config in arch/arm64 for v5.4-rc1
Message-id: <20190923141122.1264-1-jcline@redhat.com>
Patchwork-id: 272788
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in arch/arm64 for v5.4-rc1
Bugzilla:
RH-Acked-by: Jeremy Linton <jlinton@redhat.com>
RH-Acked-by: Mark Salter <msalter@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* arch/arm64/Kconfig (help): ARM64_TAGGED_ADDR_ABI (bool)
    When this option is enabled, user applications can opt in to a
    relaxed ABI via prctl() allowing tagged addresses to be passed
    to system calls as pointer arguments. For details, see
    Documentation/arm64/tagged-address-abi.txt.
* arch/arm64/Kconfig (help): ARM64_VA_BITS_52 (bool)
    Enable 52-bit virtual addressing for userspace when explicitly
    requested via a hint to mmap(). The kernel will also use 52-bit
    virtual addresses for its own mappings (provided HW support for
    this feature is available, otherwise it reverts to 48-bit).

    NOTE: Enabling 52-bit virtual addressing in conjunction with
    ARMv8.3 Pointer Authentication will result in the PAC being
    reduced from 7 bits to 3 bits, which may have a significant
    impact on its susceptibility to brute-force attacks.

    If unsure, select 48-bit virtual addressing instead.

Cc: Mark Salter <msalter@redhat.com>
Cc: Jeremy Linton <jlinton@redhat.com>
Cc: Neil Horman <nhorman@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>
Cc: Wei Huang <wei@redhat.com>
Cc: Eric Auger <eric.auger@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:19 -04:00
Jeremy Cline a070a08c29 Flip off CONFIG_ARM64_VA_BITS_52 so the bundle that turns it on applies
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:19 -04:00
Laura Abbott 4634dd87cd [redhat] Actually commit marker
The change to update the changelog missed actually adding
the marker in the commit. Fix this.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:19 -04:00
Jeremy Cline e65d178228 New configuration options for v5.4-rc4
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:19 -04:00
Laura Abbott b17972bf9b Correctly name tarball for single tarball builds
Message-id: <20191015212339.32515-1-labbott@redhat.com>
Patchwork-id: 279322
O-Subject: [ARK INTERNAL PATCH] [redhat] Correctly name tarball for single tarball builds
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Jan Stancek <jstancek@redhat.com>

The intention with single tarball builds is to have a separation
between upstream sources and introduced changes. This means the name
of the tarball that's generated should roughly match upstream. Adjust
the generation of this appropriately.

Signed-off-by: Laura Abbott <labbott@redhat.com>
---
After this change, Source0 is now named linux-5.3-rc2.tar.xz and the
folder is also named appropriately. I think this better represents
something like what Fedora is looking for sources.

Note this is based on top of my change for the changelog scine this
conflicts.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:18 -04:00
Jeremy Cline 285f58c0cc configs: New config in drivers/pci for v5.4-rc1
Message-id: <20191014162300.16308-14-jcline@redhat.com>
Patchwork-id: 278875
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/pci for v5.4-rc1
Bugzilla:
RH-Acked-by: Myron Stowe <mstowe@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/pci/controller/dwc/Kconfig (help): PCIE_AL (bool)
    Say Y here to enable support of the Amazon's Annapurna Labs PCIe
    controller IP on Amazon SoCs. The PCIe controller uses the DesignWare
    core plus Annapurna Labs proprietary hardware wrappers. This is
    required only for DT-based platforms. ACPI platforms with the
    Annapurna Labs PCIe controller don't need to enable this.

Cc: Myron Stowe <myron.stowe@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:18 -04:00
Laura Abbott bddc5c884b Allow overriding the dist tag on the command line
Message-id: <20191011183603.21725-4-labbott@redhat.com>
Patchwork-id: 278729
O-Subject: [ARK INTERNAL PATCH 3/3] [redhat] Allow overriding the dist tag on the command line
Bugzilla:
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>

Similar to the branch target for building, only set the
dist tag if it's not already been set on the command line.
This allows for easier creation of rpms intended for
other buildroots.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:18 -04:00
Laura Abbott 801cb13a8c Allow scratch branch target to be overridden
Message-id: <20191011183603.21725-3-labbott@redhat.com>
Patchwork-id: 278728
O-Subject: [ARK INTERNAL PATCH 2/3] [redhat] Allow scratch branch target to be overridden
Bugzilla:
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>

The scratch branch target is currently hard coded to what's
expected (i.e. the branch for the particular release). It's
useful to be able to change branches easily though. Allow
the scratch target to be overridden on the command line to
make it easy to do tasks like 'BUILD_SCRATCH_TARGET=f32 make rh-koji'.
Do this by only setting the branch target if it's not already
set (?=). While we're doing this, move the default
BUILD_SCRATCH_TARGET into Makefile.common which is where
most of the other per branch settings are.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:18 -04:00
Laura Abbott 3e1f3c921b Remove long dead BUILD_DEFAULT_TARGET
Message-id: <20191011183603.21725-2-labbott@redhat.com>
Patchwork-id: 278727
O-Subject: [ARK INTERNAL PATCH 1/3] [redhat] Remove long dead BUILD_DEFAULT_TARGET
Bugzilla:
RH-Acked-by: Jan Stancek <jstancek@redhat.com>
RH-Acked-by: Don Zickus <dzickus@redhat.com>
RH-Acked-by: Herton R. Krzesinski <herton@redhat.com>

This variable seems to have been commented out since at least
RHEL6. Let's assume it's not coming back and just remove it.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:18 -04:00
Laura Abbott f229bed551 Amend the changelog when rebasing
Message-id: <20191014215001.22274-1-labbott@redhat.com>
Patchwork-id: 278907
O-Subject: [ARK INTERNAL PATCH] [redhat] Amend the changelog when rebasing
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>

Currently for ARK, we don't generate an incremental changelog. Each
release dumps the same patch information into the rpm changelog. Make
this more useful by generating a running rpm changelog when rebasing.
Use the same trick we do to generate a changelog with the marker we
use to generate a base for patches. This lets us detect a rebase and
handle that case separately.

Signed-off-by: Laura Abbott <labbott@redhat.com>
---
This has been a long running quirk of ARK. This is also necessary for us
to get closer to Fedora + ARK. We could potentially run into problems if
there are identical subject lines across patches but that should be
fixable.

Because we're bootstrapping, this needs to be properly synced up to be
used with the next release. I talked to Jeremy and this should be picked
up for -rc3 but if something needs to be fixed I'll get it set up to be
used with -rc4.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:18 -04:00
Jeremy Cline ed1a8b4eea configs: New config in drivers/platform for v5.4-rc1
Message-id: <20191014162300.16308-16-jcline@redhat.com>
Patchwork-id: 278883
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/platform for v5.4-rc1
Bugzilla:
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/platform/chrome/Kconfig (help): CROS_EC (tristate)
    If you say Y here you get support for the ChromeOS Embedded
    Controller (EC) providing keyboard, battery and power services.
    You also need to enable the driver for the bus you are using. The
    protocol for talking to the EC is defined by the bus driver.

    To compile this driver as a module, choose M here: the
    module will be called cros_ec.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:17 -04:00
Jeremy Cline e6c6c5f7db configs: New config in drivers/pinctrl for v5.4-rc1
Message-id: <20191014162300.16308-15-jcline@redhat.com>
Patchwork-id: 278885
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/pinctrl for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/pinctrl/qcom/Kconfig (help): PINCTRL_SC7180 (tristate)
    This is the pinctrl, pinmux, pinconf and gpiolib driver for the
    Qualcomm Technologies Inc TLMM block found on the Qualcomm
    Technologies Inc SC7180 platform.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:17 -04:00
Jeremy Cline 9930e033e3 configs: New config in drivers/net/wireless for v5.4-rc1
Message-id: <20191014162300.16308-13-jcline@redhat.com>
Patchwork-id: 278880
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/net/wireless for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/net/wireless/ath/ath9k/Kconfig (help): ATH9K_PCI_NO_EEPROM (tristate)
    This separate driver provides a loader in order to support the
    AR500X to AR92XX-generation of ath9k PCI(e) WiFi chips, which have
    their initialization data (which contains the real PCI Device ID
    that ath9k will need) stored together with the calibration data out
    of reach for the ath9k chip.

    These devices are usually various network appliances, routers or
    access Points and such.

    If unsure say N.

Cc: Jarod Wilson <jarod@redhat.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:17 -04:00
Jeremy Cline 5d0f93bc8e configs: New config in drivers/net/ethernet/mellanox for v5.4-rc1
Message-id: <20191014162300.16308-10-jcline@redhat.com>
Patchwork-id: 278881
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/net/ethernet/mellanox for v5.4-rc1
Bugzilla:
RH-Acked-by: Marcelo Leitner <mleitner@redhat.com>
RH-Acked-by: Neil Horman <nhorman@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/net/ethernet/mellanox/mlx5/core/Kconfig (help): MLX5_SW_STEERING (bool)
    Build support for software-managed steering in the NIC.

Cc: Erez Alfasi <ealfasi@redhat.com>
Cc: Alaa Hleihel <ahleihel@redhat.com>
Cc: Slava Shwartsman <sshwarts@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:17 -04:00
Jeremy Cline 693b903457 configs: New config in drivers/net/can for v5.4-rc1
Message-id: <20191014162300.16308-9-jcline@redhat.com>
Patchwork-id: 278874
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/net/can for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/net/can/sja1000/Kconfig (help): CAN_F81601 (tristate)
    This driver adds support for Fintek F81601 PCIE to 2 CAN
    Controller. It had internal 24MHz clock source, but it can
    be changed by manufacturer. Use modinfo to get usage for
    parameters. Visit http://www.fintek.com.tw to get more
    information.
* drivers/net/can/Kconfig (help): CAN_KVASER_PCIEFD (tristate)
    This is a driver for the Kvaser PCI Express CAN FD family.

    Supported devices:
      Kvaser PCIEcan 4xHS
      Kvaser PCIEcan 2xHS v2
      Kvaser PCIEcan HS v2
      Kvaser Mini PCI Express HS v2
      Kvaser Mini PCI Express 2xHS v2

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:17 -04:00
Jeremy Cline 7ad12d9876 configs: New config in drivers/hid for v5.4-rc1
Message-id: <20191014162300.16308-7-jcline@redhat.com>
Patchwork-id: 278891
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/hid for v5.4-rc1
Bugzilla:
RH-Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/hid/Kconfig (help): HID_CREATIVE_SB0540 (tristate)
    Support for Creative infrared SB0540-compatible remote controls, such
    as the RM-1500 and RM-1800 remotes.

    Say Y here if you want support for Creative SB0540 infrared receiver.

Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Cathy Avery <cavery@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:16 -04:00
Jeremy Cline e104cc76bf configs: New config in drivers/dma-buf for v5.4-rc1
Message-id: <20191014162300.16308-5-jcline@redhat.com>
Patchwork-id: 278884
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/dma-buf for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/dma-buf/Kconfig (help): DMABUF_SELFTESTS (tristate)
    (no helpstring found)

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:16 -04:00
Jeremy Cline a41a76735d configs: New config in drivers/crypto for v5.4-rc1
Message-id: <20191014162300.16308-4-jcline@redhat.com>
Patchwork-id: 278888
O-Subject: [ARK INTERNAL PATCH] configs: New config in drivers/crypto for v5.4-rc1
Bugzilla:
RH-Acked-by: Neil Horman <nhorman@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/crypto/ccp/Kconfig (help): CRYPTO_DEV_CCP_DEBUGFS (bool)
    Expose CCP device information such as operation statistics, feature
    information, and descriptor queue contents.
* drivers/crypto/hisilicon/Kconfig (help): CRYPTO_DEV_HISI_ZIP (tristate)
    Support for HiSilicon ZIP Driver
* drivers/crypto/Kconfig (help): CRYPTO_DEV_SAFEXCEL (tristate)
    This driver interfaces with the SafeXcel EIP-97 and EIP-197 cryptographic
    engines designed by Inside Secure. It currently accelerates DES, 3DES and
    AES block ciphers in ECB and CBC mode, as well as SHA1, SHA224, SHA256,
    SHA384 and SHA512 hash algorithms for both basic hash and HMAC.
    Additionally, it accelerates combined AES-CBC/HMAC-SHA AEAD operations.

Cc: Neil Horman <nhorman@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:16 -04:00
Jeremy Cline 4cfe62d9e6 configs: New config in arch/s390 for v5.4-rc1
Message-id: <20191014162300.16308-2-jcline@redhat.com>
Patchwork-id: 278872
O-Subject: [ARK INTERNAL PATCH] configs: New config in arch/s390 for v5.4-rc1
Bugzilla:
RH-Acked-by: Cornelia Huck <cohuck@redhat.com>
RH-Acked-by: Thomas Huth <thuth@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* arch/s390/Kconfig (help): KEXEC_SIG (bool)
    This option makes kernel signature verification mandatory for
    the kexec_file_load() syscall.

    In addition to that option, you need to enable signature
    verification for the corresponding kernel image type being
    loaded in order for this to work.

Cc: Thomas Huth <thuth@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:16 -04:00
Jeremy Cline 110009dfd8 configs: New config in block for v5.4-rc1
Message-id: <20190918194018.6258-1-jcline@redhat.com>
Patchwork-id: 272479
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in block for v5.4-rc1
Bugzilla:
RH-Acked-by: Jeff Moyer <jmoyer@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* block/Kconfig (help): BLK_CGROUP_IOCOST (bool)
    Enabling this option enables the .weight interface for cost
    model based proportional IO control.  The IO controller
    distributes IO capacity between different groups based on
    their share of the overall weight distribution.

Cc: Ming Lei <minlei@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:16 -04:00
Jeremy Cline ac00456723 configs: New config in drivers/cpuidle for v5.4-rc1
Message-id: <20190923140215.26145-1-jcline@redhat.com>
Patchwork-id: 272761
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in drivers/cpuidle for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
RH-Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/cpuidle/Kconfig.arm (help): ARM_PSCI_CPUIDLE (bool)
    Select this to enable PSCI firmware based CPUidle driver for ARM.
    It provides an idle driver that is capable of detecting and
    managing idle states through the PSCI firmware interface.
* drivers/cpuidle/Kconfig (help): CPU_IDLE_GOV_HALTPOLL (bool)
    This governor implements haltpoll idle state selection, to be
    used in conjunction with the haltpoll cpuidle driver, allowing
    for polling for a certain amount of time before entering idle
    state.

    Some virtualized workloads benefit from using it.
* drivers/cpuidle/Kconfig (help): HALTPOLL_CPUIDLE (tristate)
    This option enables halt poll cpuidle driver, which allows to poll
    before halting in the guest (more efficient than polling in the
    host via halt_poll_ns for some scenarios).

Cc: John Linville <linville@redhat.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:16 -04:00
Laura Abbott f3c528da2b redhat: configs: Split CONFIG_CRYPTO_SHA512
Due to some encryption options Fedora enables, this now needs
to be built in. Split it out to Fedora and ARK separately.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:15 -04:00
Laura Abbott f58576bd79 redhat: Set Fedora options
These are the new Fedora optiosn for 5.4-rc1

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:15 -04:00
Jeremy Cline 664a10f977 Set CRYPTO_SHA3_*_S390 to builtin on zfcpdump
Build in these configs in as they cannot be modules.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:15 -04:00
Jeremy Cline 66188a68f2 configs: New config in drivers/edac for v5.4-rc1
Message-id: <20191001153139.14526-1-jcline@redhat.com>
Patchwork-id: 275492
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in drivers/edac for v5.4-rc1
Bugzilla:
RH-Acked-by: Aristeu Rozanski <aris@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/edac/Kconfig (help): EDAC_BLUEFIELD (tristate)
    Support for error detection and correction on the
    Mellanox BlueField SoCs.

Cc: Aristeu Rozanski <aris@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:15 -04:00
Jeremy Cline 6cf27f5b3f configs: New config in drivers/firmware for v5.4-rc1
Message-id: <20191001174534.14040-1-jcline@redhat.com>
Patchwork-id: 275495
O-Subject: [ARK INTERNAL PATCHv3] [redhat] configs: New config in drivers/firmware for v5.4-rc1
Bugzilla:
RH-Acked-by: Al Stone <ahs3@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/firmware/efi/Kconfig (help): EFI_RCI2_TABLE (bool)
    Displays the content of the Runtime Configuration Interface
    Table version 2 on Dell EMC PowerEdge systems as a binary
    attribute 'rci2' under /sys/firmware/efi/tables directory.

    RCI2 table contains BIOS HII in XML format and is used to populate
    BIOS setup page in Dell EMC OpenManage Server Administrator tool.
    The BIOS setup page contains BIOS tokens which can be configured.

    Say Y here for Dell EMC PowerEdge systems.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:15 -04:00
Jeremy Cline 3c21640d16 configs: New config in drivers/hwmon for v5.4-rc1
Message-id: <20190918194207.7637-1-jcline@redhat.com>
Patchwork-id: 272487
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/hwmon for v5.4-rc1
Bugzilla:
RH-Acked-by: Dean Nelson <dnelson@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/hwmon/Kconfig (help): SENSORS_AS370 (tristate)
    If you say yes here you get support for the PVT sensors of
    the Synaptics AS370 SoC

    This driver can also be built as a module. If so, the module
    will be called as370-hwmon.
* drivers/hwmon/pmbus/Kconfig (help): SENSORS_INSPUR_IPSPS (tristate)
    If you say yes here you get hardware monitoring support for the INSPUR
    Power System power supply.

    This driver can also be built as a module. If so, the module will
    be called inspur-ipsps.

Cc: Dean Nelson <dnelson@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:14 -04:00
Jeremy Cline 17b5add940 configs: New config in drivers/iio for v5.4-rc1
Message-id: <20190918194220.7803-1-jcline@redhat.com>
Patchwork-id: 272488
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/iio for v5.4-rc1
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/iio/imu/Kconfig (help): ADIS16460 (tristate)
    Say yes here to build support for Analog Devices ADIS16460 inertial
    sensor.

    To compile this driver as a module, choose M here: the module will be
    called adis16460.
* drivers/iio/potentiometer/Kconfig (help): MAX5432 (tristate)
    Say yes here to build support for the Maxim
    MAX5432, MAX5433, MAX5434 and MAX5435 digital
    potentiometer chips.

    To compile this driver as a module, choose M here: the
    module will be called max5432.
* drivers/iio/light/Kconfig (help): NOA1305 (tristate)
    Say Y here if you want to build support for the ON Semiconductor
    NOA1305 ambient light sensor.

    To compile this driver as a module, choose M here:
    The module will be called noa1305.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:14 -04:00
Jeremy Cline 30a6f5a2a5 configs: New config in drivers/mmc for v5.4-rc1
Message-id: <20190918194237.7993-1-jcline@redhat.com>
Patchwork-id: 272489
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/mmc for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/mmc/host/Kconfig (help): MMC_SDHCI_OF_ASPEED (tristate)
    This selects the ASPEED Secure Digital Host Controller Interface.

    If you have a controller with this interface, say Y or M here. You
    also need to enable an appropriate bus interface.

    If unsure, say N.

Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:14 -04:00
Jeremy Cline a28dfd9db7 configs: New config in drivers/tty for v5.4-rc1
Message-id: <20190918194246.8171-1-jcline@redhat.com>
Patchwork-id: 272490
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/tty for v5.4-rc1
Bugzilla:
RH-Acked-by: Prarit Bhargava <prarit@redhat.com>
RH-Acked-by: Laura Abbott <labbott@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/tty/serial/Kconfig (help): SERIAL_FSL_LINFLEXUART (tristate)
    Support for the on-chip linflexuart on some Freescale SOCs.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:14 -04:00
Jeremy Cline d65950965f configs: New config in arch/s390 for v5.4-rc1
Message-id: <20190923135800.25646-1-jcline@redhat.com>
Patchwork-id: 272760
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in arch/s390 for v5.4-rc1
Bugzilla:
RH-Acked-by: Thomas Huth <thuth@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* arch/s390/Kconfig (help): MARCH_Z15 (bool)
    Select this to enable optimizations for IBM z15 (8562
    and 8561 series). The kernel will be slightly faster but will not
    work on older machines.
* arch/s390/Kconfig (help): TUNE_Z15 (bool)
    (no helpstring found)

Cc: Neil Horman <nhorman@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:14 -04:00
Jeremy Cline 95b9afd4b9 configs: New config in drivers/bus for v5.4-rc1
Message-id: <20190918194030.6474-1-jcline@redhat.com>
Patchwork-id: 272480
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in drivers/bus for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/bus/Kconfig (help): MOXTET (tristate)
    Say yes here to add support for the module configuration bus found
    on CZ.NIC's Turris Mox. This is needed for the ability to discover
    the order in which the modules are connected and to get/set some of
    their settings. For example the GPIOs on Mox SFP module are
    configured through this bus.

Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:14 -04:00
Laura Abbott cdbc3abc71 Add option to allow mismatched configs on the command line
Message-id: <20190919183528.15814-1-labbott@redhat.com>
Patchwork-id: 272583
O-Subject: [ARK INTERNAL PATCH] [redhat] Add option to allow mismatched configs on the command line
Bugzilla:
RH-Acked-by: Don Zickus <dzickus@redhat.com>

We added checks for configuration options to make sure everything
gets set properly and reviewed. Sometimes for testing it's useful to
just be able to ignore those warnings for development or other testing.
Add an option to ignore the checks on the command line
(NO_CONFIGCHECKS=1 make rh-srpm) so developers don't have to
hack this out manually.

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:13 -04:00
Jeremy Cline fb69f98295 configs: New config in drivers/crypto for v5.4-rc1
Message-id: <20190923140408.26331-1-jcline@redhat.com>
Patchwork-id: 272762
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in drivers/crypto for v5.4-rc1
Bugzilla:
RH-Acked-by: Neil Horman <nhorman@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* drivers/crypto/Kconfig (help): CRYPTO_SHA3_256_S390 (tristate)
    This is the s390 hardware accelerated implementation of the
    SHA3_256 secure hash standard.

    It is available as of z14.
* drivers/crypto/Kconfig (help): CRYPTO_SHA3_512_S390 (tristate)
    This is the s390 hardware accelerated implementation of the
    SHA3_512 secure hash standard.

    It is available as of z14.

Cc: Neil Horman <nhorman@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: rhvirt-patches@redhat.com
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:13 -04:00
Jeremy Cline e6f38a3254 configs: New config in sound/pci for v5.4-rc1
Message-id: <20190923144238.420-1-jcline@redhat.com>
Patchwork-id: 272831
O-Subject: [ARK INTERNAL PATCHv2] [redhat] configs: New config in sound/pci for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>
RH-Acked-by: Jaroslav Kysela <jkysela@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* sound/pci/hda/Kconfig (help): SND_HDA_INTEL_DETECT_DMIC (bool)
    Say Y to detect digital microphones on SKL+ devices. DMICs
    cannot be handled by the HDaudio legacy driver and are
    currently only supported by the SOF driver.
    If unsure say N.

Cc: John Linville <linville@redhat.com>
Cc: Jaroslav Kysela <jkysela@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:13 -04:00
Jeremy Cline 7bbfc781e1 configs: New config in sound/soc for v5.4-rc1
Message-id: <20190918194331.8835-1-jcline@redhat.com>
Patchwork-id: 272493
O-Subject: [ARK INTERNAL PATCH] [redhat] configs: New config in sound/soc for v5.4-rc1
Bugzilla:
RH-Acked-by: John Linville <linville@redhat.com>

Upstream Status: RHEL only.

Hi,

As part of the rebase effort to v5.4-rc1, New config option(s) were
exposed. Please review the options below.

As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.

If the value for a file that is added should be changed, please reply
with a better option.

* sound/soc/codecs/Kconfig (help): SND_SOC_UDA1334 (tristate)
    The UDA1334 is an NXP audio codec, supports the I2S-bus data format
    and has basic features such as de-emphasis (at 44.1 kHz sampling
    rate) and mute.

Cc: John Linville <linville@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:13 -04:00
Major Hayden 6945e85f04 gitlab: Add CI job for packaging scripts
Message-id: <20190920180802.27752-1-major@redhat.com>
Patchwork-id: 272742
O-Subject: [ARK INTERNAL PATCH] [redhat] gitlab: Add CI job for packaging scripts
Bugzilla:
RH-Acked-by: Laura Abbott <labbott@redhat.com>

This job runs each time the `internal` branch is updated. It gathers
the packaging-related files from the repo and artifacts them inside
GitLab. This allows CI jobs to quickly download packaging scripts to
use with other upstream repositories.

Signed-off-by: Major Hayden <major@redhat.com>
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:13 -04:00
Major Hayden 12a6b28702 Speed up CI with CKI image
Our CKI images have all of the packages needed to do kernel-related
things.

Signed-off-by: Major Hayden <major@redhat.com>
2021-08-30 10:49:12 -04:00
Neil Horman b67724b48a Disable e1000 driver in ARK
We tried to disable this driver in RHEL8, but the dev experience team
pushed back because virtbox only supports this driver.  We shouldn't
allow that to go on forever though, as the driver isn't being maintained
upstream anymore.  So lets turn it off in ARK and at least have the
conversation again in RHEL 9

Signed-off-by: Neil Horman <nhorman@redhat.com>
2021-08-30 10:49:12 -04:00
Jeremy Cline 3a0451dfd2 configs: Fix the pending default for CONFIG_ARM64_VA_BITS_52
The current setting results in an invalid configuration so while the
patch is under review, adjust the default.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:12 -04:00
Jeremy Cline d3ec060ee3 configs: Turn on OPTIMIZE_INLINING for everything
Upstream required this in commit ac7c3e4ff4 ("compiler: enable
CONFIG_OPTIMIZE_INLINING forcibly") so move the setting back into
pending for review.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:12 -04:00
Jeremy Cline 669a9f65e9 configs: Set valid pending defaults for CRYPTO_ESSIV
It's being selected by DM_CRYPT, so it must also be at least built as a
module.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:12 -04:00
Jeremy Cline 9f62c2022d Add an initial CI configuration for the internal branch
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:12 -04:00
Jeremy Cline a250568702 New drop of configuration options for v5.4-rc1
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:11 -04:00
Jeremy Cline 75b373fc40 New drop of configuration options for v5.4-rc1
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:11 -04:00
Jeremy Cline 20afc3fa18 Pull the RHEL version defines out of the Makefile
This is done via the kernel-put-RHEL-info-into-generated-headers.patch
in the rhpatches branch.

Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:11 -04:00
Jeremy Cline d17e2c0ebb Sync up the ARK build scripts
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:11 -04:00
Jeremy Cline bb9be15d5a Sync up the Fedora Rawhide configs
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:11 -04:00
Jeremy Cline b44d40197a Sync up the ARK config files
Signed-off-by: Jeremy Cline <jcline@redhat.com>
2021-08-30 10:49:11 -04:00
Laura Abbott 34cfd6feb3 configs: Adjust CONFIG_FORCE_MAX_ZONEORDER for Fedora
Fedora has been carrying an out of tree to change the max zone order
for a while. Until we figure out what we want to do with this patch,
just set it to the expected default.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:10 -04:00
Laura Abbott 4e68108356 configs: Add README for some other arches
We need a dummy file for having a folder

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:10 -04:00
Laura Abbott 24de930785 configs: Sync up Fedora configs
This brings Fedora in sync for 5.3 for new configs. This also includes
adjusting a few options based on dropping a few patches in Fedora.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:10 -04:00
Laura Abbott 771038af8d [initial commit] Add structure for building with git
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:10 -04:00
Laura Abbott 3468b32f1b [initial commit] Add Red Hat variables in the top level makefile
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:10 -04:00
Laura Abbott 38ea5c82ae [initial commit] Red Hat gitignore and attributes
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:09 -04:00
Laura Abbott 303b1b2214 [initial commit] Add changelog
This is needed as a base for generation

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:09 -04:00
Laura Abbott ef0859d926 [initial commit] Add makefile
This is a makefile used to re-direct to the redhat directory

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:09 -04:00
Laura Abbott 26d14bb035 [initial commit] Add files for generating the kernel.spec
Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:09 -04:00
Laura Abbott ab5c3b6fbe [initial commit] Add rpm directory
Add a local rpm directory for building

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:09 -04:00
Laura Abbott 99888c0ce4 [initial commit] Add files for packaging
These are various files that are either needed for packaging
or going from src-git -> dist-git

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:08 -04:00
Laura Abbott 0e6ebee41c [initial commit] Add kabi files
Add support for building/checking kabi. This does not
add in an ABI, only the support.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:08 -04:00
Laura Abbott c8079d9d8b [initial commit] Add scripts
Various scripts used to support kernel building

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:08 -04:00
Laura Abbott 53c97efb14 [initial commit] Add configs
These are the files that make up the kernel configuration.
Details are available in the tree.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:08 -04:00
Laura Abbott 04b7482740 [initial commit] Add Makefiles
Red Hat specific commands. Run 'make rh-help' for
more information.

Signed-off-by: Laura Abbott <labbott@redhat.com>
2021-08-30 10:49:07 -04:00
16261 changed files with 43926 additions and 1523 deletions

1
.get_maintainer.conf Normal file
View File

@ -0,0 +1 @@
# --mpath redhat/rhdocs/MAINTAINERS --no-git --no-git-fallback

9
.gitignore vendored
View File

@ -156,6 +156,15 @@ x509.genkey
# Kdevelop4
*.kdev4
#
# Red Hat
#
configs/*.config
localversion
# GitLab CI configuration
!.gitlab-ci.yml
# Clang's compilation database file
/compile_commands.json

284
.gitlab-ci.yml Normal file
View File

@ -0,0 +1,284 @@
# This CI will only work for project members. CI for public contributors
# runs via a webhook on the merge requests. There's nothing you have to do if
# you want your changes tested -- created pipeline will be automatically
# linked in the merge request and appropriate labels will be added to it.
# Changes to this file will NOT be reflected in the webhook testing.
include:
- project: cki-project/pipeline-definition
ref: main
file: kernel_templates.yml
stages:
- test
- build
- deploy
workflow:
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule"' # ARK release pipelines
- if: '$CI_MERGE_REQUEST_PROJECT_PATH =~ /^cki-project.kernel-ark/' # ARK MR CI
variables:
REQUESTED_PIPELINE_TYPE: 'ark-ci'
# We cannot merge rules through !reference and have to copy them over from the
# CKI pipeline: https://gitlab.com/gitlab-org/gitlab/-/issues/322992
- if: '$CI_MERGE_REQUEST_PROJECT_PATH =~ /^redhat.rhel/ || $CI_PROJECT_PATH =~ /^redhat.rhel/'
variables:
REQUESTED_PIPELINE_TYPE: 'internal'
- if: '$CI_MERGE_REQUEST_PROJECT_PATH =~ /^redhat.centos-stream/ || $CI_PROJECT_PATH =~ /^redhat.centos-stream/'
variables:
REQUESTED_PIPELINE_TYPE: '/^(trusted|centos-rhel)$/'
# We need to differentiate between the pipeline types that are triggered from this
# single file. Once the mirroring to c9s stops this anchor can be dropped and the
# regular ".trusted" anchor and "trusted" type can be used. The template is added
# here instead of into CKI to avoid having to clear up two places after mirror drop.
.trusted-ark:
trigger:
project: redhat/red-hat-ci-tools/kernel/cki-internal-pipelines/cki-trusted-contributors
strategy: depend
variables:
PIPELINE_TYPE: 'ark-ci'
kernel_type: 'upstream'
.trigger_ark_pipeline:
stage: test
trigger:
branch: kernel-ark
variables:
name: kernel-ark
builder_image: registry.gitlab.com/cki-project/containers/builder-rawhide
builder_image_tag: latest
srpm_make_target: dist-srpm
# We only need srpm so skip the rest of the stages
skip_build: 'true'
skip_publish: 'true'
skip_test: 'true'
skip_results: 'true'
.9-common:
variables:
builder_image_tag: latest
srpm_make_target: dist-srpm
native_tools: 'true'
architectures: 'x86_64 ppc64le aarch64 s390x'
POWER_BUILDER_SUFFIX: '-p9'
.trigger_c9s_pipeline:
trigger:
branch: c9s
variables:
name: centos-stream-9
builder_image: registry.gitlab.com/cki-project/containers/builder-stream9
kpet_tree_family: c9s
kernel_type: 'upstream' # Needs to be overriden due to inheriting from .rhel_common
.trigger_rhel9_pipeline:
trigger:
branch: rhel9
variables:
name: rhel9
builder_image: quay.io/cki/builder-rhel9
kpet_tree_family: rhel9
.realtime_check_c9s:
trigger:
branch: c9s-rt
variables:
merge_branch: main-rt
name: kernel-rt-c9s
.realtime_check_rhel9:
trigger:
branch: rhel9-rt
variables:
merge_branch: main-rt
name: kernel-rt-rhel9
.trigger_rhel9_build:
extends: .trigger_rhel9_pipeline
variables:
skip_test: 'true'
skip_results: 'true'
.realtime_full_c9s:
variables:
name: kernel-rt-c9s
kpet_tree_family: c9s-rt
RUN_ONLY_FOR_RT: 'true'
.realtime_full_rhel9:
variables:
name: kernel-rt-rhel9
kpet_tree_family: rhel9-rt
RUN_ONLY_FOR_RT: 'true'
# ARK CI
ark_merge_request:
extends: [.trusted-ark, .merge_request, .trigger_ark_pipeline]
# c9s CI
c9s_merge_request:
extends: [.trusted, .merge_request, .rhel_common,
.9-common, .trigger_c9s_pipeline]
c9s_realtime_check_merge_request:
extends: [.trusted, .merge_request,
.9-common,
.realtime_check_common,
.trigger_c9s_pipeline, .realtime_check_c9s]
c9s_baseline:
extends: [.trusted, .baseline, .rhel_common,
.9-common, .trigger_c9s_pipeline]
c9s_rhel9_compat_merge_request:
extends: [.centos_stream_rhel_internal, .merge_request, .rhel_common,
.9-common, .trigger_rhel9_build]
c9s_rhel9_compat_baseline:
extends: [.centos_stream_rhel_internal, .baseline, .rhel_common,
.9-common, .trigger_rhel9_build]
# c9s realtime branch CI
c9s_realtime_merge_request:
extends: [.trusted, .merge_request,
.9-common,
.realtime_pipeline_common,
.trigger_c9s_pipeline, .realtime_full_c9s]
c9s_realtime_baseline:
extends: [.trusted, .baseline,
.9-common,
.realtime_pipeline_common,
.trigger_c9s_pipeline, .realtime_full_c9s]
# RHEL9 CI
rhel9_merge_request:
extends: [.internal, .merge_request, .rhel_common,
.9-common, .trigger_rhel9_pipeline]
rhel9_realtime_check_merge_request:
extends: [.internal, .merge_request,
.9-common,
.realtime_check_common,
.trigger_rhel9_pipeline, .realtime_check_rhel9]
rhel9_baseline:
extends: [.internal, .baseline, .rhel_common,
.9-common, .trigger_rhel9_pipeline]
# RHEL9 realtime branch CI
rhel9_realtime_merge_request:
extends: [.internal, .merge_request,
.9-common,
.realtime_pipeline_common,
.trigger_rhel9_pipeline, .realtime_full_rhel9]
rhel9_realtime_baseline:
extends: [.internal, .baseline,
.9-common,
.realtime_pipeline_common,
.trigger_rhel9_pipeline, .realtime_full_rhel9]
# scheduled job
.scheduled_setup:
image: registry.gitlab.com/cki-project/containers/builder-fedora
variables:
GIT_DEPTH: "0"
GIT_CLONE_PATH: $CI_BUILDS_DIR/$CI_CONCURRENT_ID/kernel-ark
before_script:
- echo "fastestmirror=true" >> /etc/dnf/dnf.conf
- dnf -y install python3-gitlab git openssh-clients dnf-utils gnupg2
- git config user.name "Fedora Kernel Team"
- git config user.email "kernel-team@fedoraproject.org"
- echo "$PYTHON_GITLAB_CONFIG" >> ~/.python-gitlab.cfg
# Need SSH since the clone is set up without write access.
- eval $(ssh-agent -s)
- echo "$PRIVATE_KEY" | tr -d '\r' | ssh-add - > /dev/null
- mkdir -p ~/.ssh
- chmod 700 ~/.ssh
- echo "$GITLAB_KNOWN_HOSTS" >> ~/.ssh/known_hosts
- chmod 644 ~/.ssh/known_hosts
- git remote add gitlab git@gitlab.com:cki-project/kernel-ark.git
- gpg2 --import "$TORVALDS_GPG_KEY"
- git checkout --track origin/master && git describe
- export PROJECT_ID="$CI_PROJECT_ID"
merge_upstream:
extends: .scheduled_setup
script:
- git checkout --track origin/os-build && git describe
- make dist-merge-upstream-push || exit 1
retry: 2
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule" && $RAWHIDE_RELEASE == "false"'
# scheduled job
rawhide_release:
extends: .scheduled_setup
script:
- git checkout --track origin/ark-latest && git describe
- git checkout --track origin/ark-infra && git describe
- git checkout --track origin/os-build && git describe
- redhat/scripts/ci/ark-create-release.sh "master" "$CI_PROJECT_ID" || exit_code=$?
- if [ $exit_code -eq 3 ]; then echo "Tag exists, halting" && exit 0; fi;
- if [ $exit_code -ne 0 ]; then echo "Unable to create release tag" && exit 1; fi;
- git push gitlab os-build
# ark-create-release.sh creates a tag for ark-latest to be pushed.
# Make sure the ark-latest branch is checked out.
- git checkout ark-latest
- git push gitlab "$(git describe)"
- git push gitlab ark/*
- git push -f gitlab ark-latest
- git push -f gitlab ark-infra
retry: 2
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule" && $RAWHIDE_RELEASE == "true"'
test_docs:
stage: test
image: registry.gitlab.com/cki-project/containers/python
before_script:
- python3 -m venv ~/docs-venv
- source ~/docs-venv/bin/activate
- pip install sphinx
- cd redhat/docs/
script: make SPHINXOPTS="-W" html
rules:
- if: '$CI_MERGE_REQUEST_TARGET_BRANCH_NAME == "os-build"'
changes:
- redhat/docs/**/*
docs:
stage: build
image: registry.gitlab.com/cki-project/containers/python
before_script:
- python3 -m venv ~/docs-venv
- source ~/docs-venv/bin/activate
- pip install sphinx
- cd redhat/docs/
script: make SPHINXOPTS="-W" html
artifacts:
paths:
- redhat/docs/_build/html/
rules:
- if: '$CI_COMMIT_BRANCH == "os-build"'
changes:
- redhat/docs/**/*
pages:
stage: deploy
image: registry.gitlab.com/cki-project/containers/python
dependencies:
- docs
script:
- mv redhat/docs/_build/html/ public/
artifacts:
paths:
- public
rules:
- if: '$CI_COMMIT_BRANCH == "os-build"'
changes:
- redhat/docs/**/*

View File

@ -5892,6 +5892,15 @@
unknown_nmi_panic
[X86] Cause panic on unknown NMI.
unprivileged_bpf_disabled=
Format: { "0" | "1" | "2" }
Sets the initial value of
kernel.unprivileged_bpf_disabled sysctl knob.
0 - unprivileged bpf() syscall access is enabled.
1 - unprivileged bpf() syscall access is disabled permanently.
2 - unprivileged bpf() syscall access is disabled.
Default value is 2.
usbcore.authorized_default=
[USB] Default USB device authorization:
(default -1 = authorized except for wireless USB,

View File

@ -30,3 +30,5 @@ source "lib/Kconfig"
source "lib/Kconfig.debug"
source "Documentation/Kconfig"
source "Kconfig.redhat"

17
Kconfig.redhat Normal file
View File

@ -0,0 +1,17 @@
# SPDX-License-Identifier: GPL-2.0-only
#
# Red Hat specific options
#
menu "Red Hat options"
config RHEL_DIFFERENCES
bool "Remove support for deprecated features"
help
Red Hat may choose to deprecate certain features in its kernels.
Enable this option to remove support for hardware that is no
longer supported.
Unless you want a restricted kernel, say N here.
endmenu

View File

@ -18,6 +18,10 @@ $(if $(filter __%, $(MAKECMDGOALS)), \
PHONY := __all
__all:
# Set RHEL variables
# Use this spot to avoid future merge conflicts
include Makefile.rhelver
# We are using a recursive build, so we need to do a little thinking
# to get the ordering right.
#
@ -1263,7 +1267,13 @@ define filechk_version.h
((c) > 255 ? 255 : (c)))'; \
echo \#define LINUX_VERSION_MAJOR $(VERSION); \
echo \#define LINUX_VERSION_PATCHLEVEL $(PATCHLEVEL); \
echo \#define LINUX_VERSION_SUBLEVEL $(SUBLEVEL)
echo \#define LINUX_VERSION_SUBLEVEL $(SUBLEVEL); \
echo '#define RHEL_MAJOR $(RHEL_MAJOR)'; \
echo '#define RHEL_MINOR $(RHEL_MINOR)'; \
echo '#define RHEL_RELEASE_VERSION(a,b) (((a) << 8) + (b))'; \
echo '#define RHEL_RELEASE_CODE \
$(shell expr $(RHEL_MAJOR) \* 256 + $(RHEL_MINOR))'; \
echo '#define RHEL_RELEASE "$(RHEL_RELEASE)"'
endef
$(version_h): PATCHLEVEL := $(if $(PATCHLEVEL), $(PATCHLEVEL), 0)

45
Makefile.rhelver Normal file
View File

@ -0,0 +1,45 @@
RHEL_MAJOR = 9
RHEL_MINOR = 99
#
# RHEL_RELEASE
# -------------
#
# Represents build number in 'release' part of RPM's name-version-release.
# name is <package_name>, e.g. kernel
# version is upstream kernel version this kernel is based on, e.g. 4.18.0
# release is <RHEL_RELEASE>.<dist_tag>[<buildid>], e.g. 100.el8
#
# Use this spot to avoid future merge conflicts.
# Do not trim this comment.
RHEL_RELEASE = 42
#
# Early y+1 numbering
# --------------------
#
# In early y+1 process, RHEL_RELEASE consists of 2 numbers: x.y
# First is RHEL_RELEASE inherited/merged from y as-is, second number
# is incremented with each build starting from 1. After merge from y,
# it resets back to 1. This way y+1 nvr reflects status of last merge.
#
# Example:
#
# rhel8.0 rhel-8.1
# kernel-4.18.0-58.el8 --> kernel-4.18.0-58.1.el8
# kernel-4.18.0-58.2.el8
# kernel-4.18.0-59.el8 kernel-4.18.0-59.1.el8
# kernel-4.18.0-60.el8
# kernel-4.18.0-61.el8 --> kernel-4.18.0-61.1.el8
#
#
# Use this spot to avoid future merge conflicts.
# Do not trim this comment.
EARLY_YSTREAM ?= no
EARLY_YBUILD:=
EARLY_YRELEASE:=
ifneq ("$(ZSTREAM)", "yes")
ifeq ("$(EARLY_YSTREAM)","yes")
RHEL_RELEASE:=$(RHEL_RELEASE).$(EARLY_YRELEASE)
endif
endif

View File

@ -1469,9 +1469,9 @@ config HIGHMEM
If unsure, say n.
config HIGHPTE
bool "Allocate 2nd-level pagetables from highmem" if EXPERT
bool "Allocate 2nd-level pagetables from highmem"
depends on HIGHMEM
default y
default n
help
The VM uses one page of physical memory for each page table.
For systems with a lot of processes, this can use a lot of

View File

@ -911,7 +911,7 @@ endchoice
config ARM64_FORCE_52BIT
bool "Force 52-bit virtual addresses for userspace"
depends on ARM64_VA_BITS_52 && EXPERT
depends on ARM64_VA_BITS_52
help
For systems with 52-bit userspace VAs enabled, the kernel will attempt
to maintain compatibility with older software by providing 48-bit VAs
@ -1152,6 +1152,7 @@ config XEN
config FORCE_MAX_ZONEORDER
int
default "14" if ARM64_64K_PAGES
default "13" if (ARCH_THUNDER && !ARM64_64K_PAGES)
default "12" if ARM64_16K_PAGES
default "11"
help

View File

@ -385,10 +385,6 @@
};
};
&cdn_dp {
status = "okay";
};
&cpu_b0 {
cpu-supply = <&vdd_cpu_b>;
};
@ -711,7 +707,7 @@
connector {
compatible = "usb-c-connector";
data-role = "host";
data-role = "dual";
label = "USB-C";
op-sink-microwatt = <1000000>;
power-role = "dual";

View File

@ -40,7 +40,11 @@ int acpi_pci_disabled = 1; /* skip ACPI PCI scan and IRQ initialization */
EXPORT_SYMBOL(acpi_pci_disabled);
static bool param_acpi_off __initdata;
#ifdef CONFIG_RHEL_DIFFERENCES
static bool param_acpi_on __initdata = true;
#else
static bool param_acpi_on __initdata;
#endif
static bool param_acpi_force __initdata;
static int __init parse_acpi(char *arg)

View File

@ -128,6 +128,7 @@ int ipl_report_add_component(struct ipl_report *report, struct kexec_buf *kbuf,
unsigned char flags, unsigned short cert);
int ipl_report_add_certificate(struct ipl_report *report, void *key,
unsigned long addr, unsigned long len);
bool ipl_get_secureboot(void);
/*
* DIAG 308 support

View File

@ -2215,3 +2215,8 @@ int ipl_report_free(struct ipl_report *report)
}
#endif
bool ipl_get_secureboot(void)
{
return !!ipl_secure_flag;
}

View File

@ -49,6 +49,7 @@
#include <linux/memory.h>
#include <linux/compat.h>
#include <linux/start_kernel.h>
#include <linux/security.h>
#include <linux/hugetlb.h>
#include <linux/kmemleak.h>
@ -981,6 +982,9 @@ void __init setup_arch(char **cmdline_p)
log_component_list();
if (ipl_get_secureboot())
security_lock_kernel_down("Secure IPL mode", LOCKDOWN_INTEGRITY_MAX);
/* Have one command line that is parsed and saved in /proc/cmdline */
/* boot_command_line has been already set up in early.c */
*cmdline_p = boot_command_line;

View File

@ -1311,6 +1311,7 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
cpu_detect(c);
get_cpu_vendor(c);
get_cpu_cap(c);
get_model_name(c); /* RHEL: get model name for unsupported check */
get_cpu_address_sizes(c);
setup_force_cpu_cap(X86_FEATURE_CPUID);
cpu_parse_early_param();

View File

@ -20,6 +20,7 @@
#include <linux/root_dev.h>
#include <linux/hugetlb.h>
#include <linux/tboot.h>
#include <linux/security.h>
#include <linux/usb/xhci-dbgp.h>
#include <linux/static_call.h>
#include <linux/swiotlb.h>
@ -50,6 +51,7 @@
#include <asm/unwind.h>
#include <asm/vsyscall.h>
#include <linux/vmalloc.h>
#include <asm/intel-family.h>
/*
* max_low_pfn_mapped: highest directly mapped pfn < 4 GB
@ -723,6 +725,50 @@ static void __init early_reserve_memory(void)
trim_snb_memory();
}
#ifdef CONFIG_RHEL_DIFFERENCES
static void rh_check_supported(void)
{
bool guest;
guest = (x86_hyper_type != X86_HYPER_NATIVE || boot_cpu_has(X86_FEATURE_HYPERVISOR));
/* RHEL supports single cpu on guests only */
if (((boot_cpu_data.x86_max_cores * smp_num_siblings) == 1) &&
!guest && is_kdump_kernel()) {
pr_crit("Detected single cpu native boot.\n");
pr_crit("Important: In this kernel, single threaded, single CPU 64-bit physical systems are unsupported.");
}
/*
* If the RHEL kernel does not support this hardware, the kernel will
* attempt to boot, but no support is provided for this hardware
*/
switch (boot_cpu_data.x86_vendor) {
case X86_VENDOR_AMD:
case X86_VENDOR_INTEL:
break;
default:
pr_crit("Detected processor %s %s\n",
boot_cpu_data.x86_vendor_id,
boot_cpu_data.x86_model_id);
mark_hardware_unsupported("Processor");
break;
}
/*
* Due to the complexity of x86 lapic & ioapic enumeration, and PCI IRQ
* routing, ACPI is required for x86. acpi=off is a valid debug kernel
* parameter, so just print out a loud warning in case something
* goes wrong (which is most of the time).
*/
if (acpi_disabled && !guest)
pr_crit("ACPI has been disabled or is not available on this hardware. This may result in a single cpu boot, incorrect PCI IRQ routing, or boot failure.\n");
}
#else
#define rh_check_supported()
#endif
/*
* Dump out kernel offset information on panic.
*/
@ -929,6 +975,13 @@ void __init setup_arch(char **cmdline_p)
if (efi_enabled(EFI_BOOT))
efi_init();
efi_set_secure_boot(boot_params.secure_boot);
#ifdef CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT
if (efi_enabled(EFI_SECURE_BOOT))
security_lock_kernel_down("EFI Secure Boot mode", LOCKDOWN_INTEGRITY_MAX);
#endif
dmi_setup();
/*
@ -1094,19 +1147,7 @@ void __init setup_arch(char **cmdline_p)
/* Allocate bigger log buffer */
setup_log_buf(1);
if (efi_enabled(EFI_BOOT)) {
switch (boot_params.secure_boot) {
case efi_secureboot_mode_disabled:
pr_info("Secure boot disabled\n");
break;
case efi_secureboot_mode_enabled:
pr_info("Secure boot enabled\n");
break;
default:
pr_info("Secure boot could not be determined\n");
break;
}
}
efi_set_secure_boot(boot_params.secure_boot);
reserve_initrd();
@ -1219,6 +1260,8 @@ void __init setup_arch(char **cmdline_p)
efi_apply_memmap_quirks();
#endif
rh_check_supported();
unwind_init();
}

View File

@ -11,14 +11,17 @@
#include <linux/atomic.h>
#include <crypto/internal/rng.h>
#include <linux/err.h>
#include <linux/fips.h>
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/mutex.h>
#include <linux/random.h>
#include <linux/seq_file.h>
#include <linux/sched.h>
#include <linux/sched/signal.h>
#include <linux/slab.h>
#include <linux/string.h>
#include <linux/cryptouser.h>
#include <linux/compiler.h>
#include <net/netlink.h>
#include "internal.h"
@ -224,5 +227,73 @@ void crypto_unregister_rngs(struct rng_alg *algs, int count)
}
EXPORT_SYMBOL_GPL(crypto_unregister_rngs);
static ssize_t crypto_devrandom_read(void __user *buf, size_t buflen)
{
u8 tmp[256];
ssize_t ret;
if (!buflen)
return 0;
ret = crypto_get_default_rng();
if (ret)
return ret;
for (;;) {
int err;
int i;
i = min_t(int, buflen, sizeof(tmp));
err = crypto_rng_get_bytes(crypto_default_rng, tmp, i);
if (err) {
ret = err;
break;
}
if (copy_to_user(buf, tmp, i)) {
ret = -EFAULT;
break;
}
buflen -= i;
buf += i;
ret += i;
if (!buflen)
break;
if (need_resched()) {
if (signal_pending(current))
break;
schedule();
}
}
crypto_put_default_rng();
memzero_explicit(tmp, sizeof(tmp));
return ret;
}
static const struct random_extrng crypto_devrandom_rng = {
.extrng_read = crypto_devrandom_read,
.owner = THIS_MODULE,
};
static int __init crypto_rng_init(void)
{
if (fips_enabled)
random_register_extrng(&crypto_devrandom_rng);
return 0;
}
static void __exit crypto_rng_exit(void)
{
random_unregister_extrng();
}
late_initcall(crypto_rng_init);
module_exit(crypto_rng_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Random Number Generator");

View File

@ -94,6 +94,14 @@ int apei_hest_parse(apei_hest_func_t func, void *data)
if (hest_disable || !hest_tab)
return -EINVAL;
#ifdef CONFIG_ARM64
/* Ignore broken firmware */
if (!strncmp(hest_tab->header.oem_id, "HPE ", 6) &&
!strncmp(hest_tab->header.oem_table_id, "ProLiant", 8) &&
MIDR_IMPLEMENTOR(read_cpuid_id()) == ARM_CPU_IMP_APM)
return -EINVAL;
#endif
hest_hdr = (struct acpi_hest_header *)(hest_tab + 1);
for (i = 0; i < hest_tab->error_source_count; i++) {
len = hest_esrc_len(hest_hdr);

View File

@ -130,6 +130,7 @@ struct acpi_irq_parse_one_ctx {
unsigned int index;
unsigned long *res_flags;
struct irq_fwspec *fwspec;
bool skip_producer_check;
};
/**
@ -201,7 +202,8 @@ static acpi_status acpi_irq_parse_one_cb(struct acpi_resource *ares,
return AE_CTRL_TERMINATE;
case ACPI_RESOURCE_TYPE_EXTENDED_IRQ:
eirq = &ares->data.extended_irq;
if (eirq->producer_consumer == ACPI_PRODUCER)
if (!ctx->skip_producer_check &&
eirq->producer_consumer == ACPI_PRODUCER)
return AE_OK;
if (ctx->index >= eirq->interrupt_count) {
ctx->index -= eirq->interrupt_count;
@ -236,8 +238,19 @@ static acpi_status acpi_irq_parse_one_cb(struct acpi_resource *ares,
static int acpi_irq_parse_one(acpi_handle handle, unsigned int index,
struct irq_fwspec *fwspec, unsigned long *flags)
{
struct acpi_irq_parse_one_ctx ctx = { -EINVAL, index, flags, fwspec };
struct acpi_irq_parse_one_ctx ctx = { -EINVAL, index, flags, fwspec, false };
/*
* Firmware on arm64-based HPE m400 platform incorrectly marks
* its UART interrupt as ACPI_PRODUCER rather than ACPI_CONSUMER.
* Don't do the producer/consumer check for that device.
*/
if (IS_ENABLED(CONFIG_ARM64)) {
struct acpi_device *adev = acpi_bus_get_acpi_device(handle);
if (adev && !strcmp(acpi_device_hid(adev), "APMC0D08"))
ctx.skip_producer_check = true;
}
acpi_walk_resources(handle, METHOD_NAME__CRS, acpi_irq_parse_one_cb, &ctx);
return ctx.rc;
}

View File

@ -1720,6 +1720,15 @@ static bool acpi_device_enumeration_by_parent(struct acpi_device *device)
if (!acpi_match_device_ids(device, i2c_multi_instantiate_ids))
return false;
/*
* Firmware on some arm64 X-Gene platforms will make the UART
* device appear as both a UART and a slave of that UART. Just
* bail out here for X-Gene UARTs.
*/
if (IS_ENABLED(CONFIG_ARM64) &&
!strcmp(acpi_device_hid(device), "APMC0D08"))
return false;
INIT_LIST_HEAD(&resource_list);
acpi_dev_get_resources(device, &resource_list,
acpi_check_serial_bus_slave,

View File

@ -672,6 +672,24 @@ int ahci_stop_engine(struct ata_port *ap)
tmp &= ~PORT_CMD_START;
writel(tmp, port_mmio + PORT_CMD);
#ifdef CONFIG_ARM64
/* Rev Ax of Cavium CN99XX needs a hack for port stop */
if (dev_is_pci(ap->host->dev) &&
to_pci_dev(ap->host->dev)->vendor == 0x14e4 &&
to_pci_dev(ap->host->dev)->device == 0x9027 &&
midr_is_cpu_model_range(read_cpuid_id(),
MIDR_CPU_MODEL(ARM_CPU_IMP_BRCM, BRCM_CPU_PART_VULCAN),
MIDR_CPU_VAR_REV(0, 0),
MIDR_CPU_VAR_REV(0, MIDR_REVISION_MASK))) {
tmp = readl(hpriv->mmio + 0x8000);
udelay(100);
writel(tmp | (1 << 26), hpriv->mmio + 0x8000);
udelay(100);
writel(tmp & ~(1 << 26), hpriv->mmio + 0x8000);
dev_warn(ap->host->dev, "CN99XX SATA reset workaround applied\n");
}
#endif
/* wait for engine to stop. This could be as long as 500 msec */
tmp = ata_wait_register(ap, port_mmio + PORT_CMD,
PORT_CMD_LIST_ON, PORT_CMD_LIST_ON, 1, 500);

View File

@ -215,6 +215,21 @@ static int __init scan_for_dmi_ipmi(void)
{
const struct dmi_device *dev = NULL;
#ifdef CONFIG_ARM64
/* RHEL-only
* If this is ARM-based HPE m400, return now, because that platform
* reports the host-side ipmi address as intel port-io space, which
* does not exist in the ARM architecture.
*/
const char *dmistr = dmi_get_system_info(DMI_PRODUCT_NAME);
if (dmistr && (strcmp("ProLiant m400 Server", dmistr) == 0)) {
pr_debug("%s does not support host ipmi\n", dmistr);
return 0;
}
/* END RHEL-only */
#endif
while ((dev = dmi_find_device(DMI_DEV_TYPE_IPMI, NULL, dev)))
dmi_decode_ipmi((const struct dmi_header *) dev->device_data);

View File

@ -35,6 +35,7 @@
#include <linux/uuid.h>
#include <linux/nospec.h>
#include <linux/vmalloc.h>
#include <linux/dmi.h>
#include <linux/delay.h>
#define IPMI_DRIVER_VERSION "39.2"
@ -5160,8 +5161,21 @@ static int __init ipmi_init_msghandler_mod(void)
{
int rv;
pr_info("version " IPMI_DRIVER_VERSION "\n");
#ifdef CONFIG_ARM64
/* RHEL-only
* If this is ARM-based HPE m400, return now, because that platform
* reports the host-side ipmi address as intel port-io space, which
* does not exist in the ARM architecture.
*/
const char *dmistr = dmi_get_system_info(DMI_PRODUCT_NAME);
if (dmistr && (strcmp("ProLiant m400 Server", dmistr) == 0)) {
pr_debug("%s does not support host ipmi\n", dmistr);
return -ENOSYS;
}
/* END RHEL-only */
#endif
pr_info("version " IPMI_DRIVER_VERSION "\n");
mutex_lock(&ipmi_interfaces_mutex);
rv = ipmi_register_driver();
mutex_unlock(&ipmi_interfaces_mutex);

View File

@ -335,6 +335,7 @@
#include <linux/syscalls.h>
#include <linux/completion.h>
#include <linux/uuid.h>
#include <linux/rcupdate.h>
#include <crypto/chacha.h>
#include <crypto/sha1.h>
@ -349,6 +350,11 @@
/* #define ADD_INTERRUPT_BENCH */
/*
* Hook for external RNG.
*/
static const struct random_extrng __rcu *extrng;
/*
* Configuration information
*/
@ -481,6 +487,9 @@ static int ratelimit_disable __read_mostly;
module_param_named(ratelimit_disable, ratelimit_disable, int, 0644);
MODULE_PARM_DESC(ratelimit_disable, "Disable random ratelimit suppression");
static const struct file_operations extrng_random_fops;
static const struct file_operations extrng_urandom_fops;
/**********************************************************************
*
* OS independent entropy store. Here are the functions which handle
@ -1858,6 +1867,13 @@ random_poll(struct file *file, poll_table * wait)
return mask;
}
static __poll_t
extrng_poll(struct file *file, poll_table * wait)
{
/* extrng pool is always full, always read, no writes */
return EPOLLIN | EPOLLRDNORM;
}
static int
write_pool(struct entropy_store *r, const char __user *buffer, size_t count)
{
@ -1961,7 +1977,58 @@ static int random_fasync(int fd, struct file *filp, int on)
return fasync_helper(fd, filp, on, &fasync);
}
static int random_open(struct inode *inode, struct file *filp)
{
const struct random_extrng *rng;
rcu_read_lock();
rng = rcu_dereference(extrng);
if (rng && !try_module_get(rng->owner))
rng = NULL;
rcu_read_unlock();
if (!rng)
return 0;
filp->f_op = &extrng_random_fops;
filp->private_data = rng->owner;
return 0;
}
static int urandom_open(struct inode *inode, struct file *filp)
{
const struct random_extrng *rng;
rcu_read_lock();
rng = rcu_dereference(extrng);
if (rng && !try_module_get(rng->owner))
rng = NULL;
rcu_read_unlock();
if (!rng)
return 0;
filp->f_op = &extrng_urandom_fops;
filp->private_data = rng->owner;
return 0;
}
static int extrng_release(struct inode *inode, struct file *filp)
{
module_put(filp->private_data);
return 0;
}
static ssize_t
extrng_read(struct file *file, char __user *buf, size_t nbytes, loff_t *ppos)
{
return rcu_dereference_raw(extrng)->extrng_read(buf, nbytes);
}
const struct file_operations random_fops = {
.open = random_open,
.read = random_read,
.write = random_write,
.poll = random_poll,
@ -1972,6 +2039,7 @@ const struct file_operations random_fops = {
};
const struct file_operations urandom_fops = {
.open = urandom_open,
.read = urandom_read,
.write = random_write,
.unlocked_ioctl = random_ioctl,
@ -1980,9 +2048,31 @@ const struct file_operations urandom_fops = {
.llseek = noop_llseek,
};
static const struct file_operations extrng_random_fops = {
.open = random_open,
.read = extrng_read,
.write = random_write,
.poll = extrng_poll,
.unlocked_ioctl = random_ioctl,
.fasync = random_fasync,
.llseek = noop_llseek,
.release = extrng_release,
};
static const struct file_operations extrng_urandom_fops = {
.open = urandom_open,
.read = extrng_read,
.write = random_write,
.unlocked_ioctl = random_ioctl,
.fasync = random_fasync,
.llseek = noop_llseek,
.release = extrng_release,
};
SYSCALL_DEFINE3(getrandom, char __user *, buf, size_t, count,
unsigned int, flags)
{
const struct random_extrng *rng;
int ret;
if (flags & ~(GRND_NONBLOCK|GRND_RANDOM|GRND_INSECURE))
@ -1998,6 +2088,18 @@ SYSCALL_DEFINE3(getrandom, char __user *, buf, size_t, count,
if (count > INT_MAX)
count = INT_MAX;
rcu_read_lock();
rng = rcu_dereference(extrng);
if (rng && !try_module_get(rng->owner))
rng = NULL;
rcu_read_unlock();
if (rng) {
ret = rng->extrng_read(buf, count);
module_put(rng->owner);
return ret;
}
if (!(flags & GRND_INSECURE) && !crng_ready()) {
if (flags & GRND_NONBLOCK)
return -EAGAIN;
@ -2303,3 +2405,16 @@ void add_bootloader_randomness(const void *buf, unsigned int size)
add_device_randomness(buf, size);
}
EXPORT_SYMBOL_GPL(add_bootloader_randomness);
void random_register_extrng(const struct random_extrng *rng)
{
rcu_assign_pointer(extrng, rng);
}
EXPORT_SYMBOL_GPL(random_register_extrng);
void random_unregister_extrng(void)
{
RCU_INIT_POINTER(extrng, NULL);
synchronize_rcu();
}
EXPORT_SYMBOL_GPL(random_unregister_extrng);

View File

@ -28,6 +28,7 @@ obj-$(CONFIG_EFI_FAKE_MEMMAP) += fake_map.o
obj-$(CONFIG_EFI_BOOTLOADER_CONTROL) += efibc.o
obj-$(CONFIG_EFI_TEST) += test/
obj-$(CONFIG_EFI_DEV_PATH_PARSER) += dev-path-parser.o
obj-$(CONFIG_EFI) += secureboot.o
obj-$(CONFIG_APPLE_PROPERTIES) += apple-properties.o
obj-$(CONFIG_EFI_RCI2_TABLE) += rci2-table.o
obj-$(CONFIG_EFI_EMBEDDED_FIRMWARE) += embedded-firmware.o

View File

@ -31,6 +31,7 @@
#include <linux/ucs2_string.h>
#include <linux/memblock.h>
#include <linux/security.h>
#include <linux/bsearch.h>
#include <asm/early_ioremap.h>
@ -841,40 +842,101 @@ int efi_mem_type(unsigned long phys_addr)
}
#endif
struct efi_error_code {
efi_status_t status;
int errno;
const char *description;
};
static const struct efi_error_code efi_error_codes[] = {
{ EFI_SUCCESS, 0, "Success"},
#if 0
{ EFI_LOAD_ERROR, -EPICK_AN_ERRNO, "Load Error"},
#endif
{ EFI_INVALID_PARAMETER, -EINVAL, "Invalid Parameter"},
{ EFI_UNSUPPORTED, -ENOSYS, "Unsupported"},
{ EFI_BAD_BUFFER_SIZE, -ENOSPC, "Bad Buffer Size"},
{ EFI_BUFFER_TOO_SMALL, -ENOSPC, "Buffer Too Small"},
{ EFI_NOT_READY, -EAGAIN, "Not Ready"},
{ EFI_DEVICE_ERROR, -EIO, "Device Error"},
{ EFI_WRITE_PROTECTED, -EROFS, "Write Protected"},
{ EFI_OUT_OF_RESOURCES, -ENOMEM, "Out of Resources"},
#if 0
{ EFI_VOLUME_CORRUPTED, -EPICK_AN_ERRNO, "Volume Corrupt"},
{ EFI_VOLUME_FULL, -EPICK_AN_ERRNO, "Volume Full"},
{ EFI_NO_MEDIA, -EPICK_AN_ERRNO, "No Media"},
{ EFI_MEDIA_CHANGED, -EPICK_AN_ERRNO, "Media changed"},
#endif
{ EFI_NOT_FOUND, -ENOENT, "Not Found"},
#if 0
{ EFI_ACCESS_DENIED, -EPICK_AN_ERRNO, "Access Denied"},
{ EFI_NO_RESPONSE, -EPICK_AN_ERRNO, "No Response"},
{ EFI_NO_MAPPING, -EPICK_AN_ERRNO, "No mapping"},
{ EFI_TIMEOUT, -EPICK_AN_ERRNO, "Time out"},
{ EFI_NOT_STARTED, -EPICK_AN_ERRNO, "Not started"},
{ EFI_ALREADY_STARTED, -EPICK_AN_ERRNO, "Already started"},
#endif
{ EFI_ABORTED, -EINTR, "Aborted"},
#if 0
{ EFI_ICMP_ERROR, -EPICK_AN_ERRNO, "ICMP Error"},
{ EFI_TFTP_ERROR, -EPICK_AN_ERRNO, "TFTP Error"},
{ EFI_PROTOCOL_ERROR, -EPICK_AN_ERRNO, "Protocol Error"},
{ EFI_INCOMPATIBLE_VERSION, -EPICK_AN_ERRNO, "Incompatible Version"},
#endif
{ EFI_SECURITY_VIOLATION, -EACCES, "Security Policy Violation"},
#if 0
{ EFI_CRC_ERROR, -EPICK_AN_ERRNO, "CRC Error"},
{ EFI_END_OF_MEDIA, -EPICK_AN_ERRNO, "End of Media"},
{ EFI_END_OF_FILE, -EPICK_AN_ERRNO, "End of File"},
{ EFI_INVALID_LANGUAGE, -EPICK_AN_ERRNO, "Invalid Languages"},
{ EFI_COMPROMISED_DATA, -EPICK_AN_ERRNO, "Compromised Data"},
// warnings
{ EFI_WARN_UNKOWN_GLYPH, -EPICK_AN_ERRNO, "Warning Unknown Glyph"},
{ EFI_WARN_DELETE_FAILURE, -EPICK_AN_ERRNO, "Warning Delete Failure"},
{ EFI_WARN_WRITE_FAILURE, -EPICK_AN_ERRNO, "Warning Write Failure"},
{ EFI_WARN_BUFFER_TOO_SMALL, -EPICK_AN_ERRNO, "Warning Buffer Too Small"},
#endif
};
static int
efi_status_cmp_bsearch(const void *key, const void *item)
{
u64 status = (u64)(uintptr_t)key;
struct efi_error_code *code = (struct efi_error_code *)item;
if (status < code->status)
return -1;
if (status > code->status)
return 1;
return 0;
}
int efi_status_to_err(efi_status_t status)
{
int err;
struct efi_error_code *found;
size_t num = sizeof(efi_error_codes) / sizeof(struct efi_error_code);
switch (status) {
case EFI_SUCCESS:
err = 0;
break;
case EFI_INVALID_PARAMETER:
err = -EINVAL;
break;
case EFI_OUT_OF_RESOURCES:
err = -ENOSPC;
break;
case EFI_DEVICE_ERROR:
err = -EIO;
break;
case EFI_WRITE_PROTECTED:
err = -EROFS;
break;
case EFI_SECURITY_VIOLATION:
err = -EACCES;
break;
case EFI_NOT_FOUND:
err = -ENOENT;
break;
case EFI_ABORTED:
err = -EINTR;
break;
default:
err = -EINVAL;
}
found = bsearch((void *)(uintptr_t)status, efi_error_codes,
sizeof(struct efi_error_code), num,
efi_status_cmp_bsearch);
if (!found)
return -EINVAL;
return found->errno;
}
return err;
const char *
efi_status_to_str(efi_status_t status)
{
struct efi_error_code *found;
size_t num = sizeof(efi_error_codes) / sizeof(struct efi_error_code);
found = bsearch((void *)(uintptr_t)status, efi_error_codes,
sizeof(struct efi_error_code), num,
efi_status_cmp_bsearch);
if (!found)
return "Unknown error code";
return found->description;
}
static DEFINE_SPINLOCK(efi_mem_reserve_persistent_lock);

View File

@ -0,0 +1,38 @@
/* Core kernel secure boot support.
*
* Copyright (C) 2017 Red Hat, Inc. All Rights Reserved.
* Written by David Howells (dhowells@redhat.com)
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public Licence
* as published by the Free Software Foundation; either version
* 2 of the Licence, or (at your option) any later version.
*/
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
#include <linux/efi.h>
#include <linux/kernel.h>
#include <linux/printk.h>
/*
* Decide what to do when UEFI secure boot mode is enabled.
*/
void __init efi_set_secure_boot(enum efi_secureboot_mode mode)
{
if (efi_enabled(EFI_BOOT)) {
switch (mode) {
case efi_secureboot_mode_disabled:
pr_info("Secure boot disabled\n");
break;
case efi_secureboot_mode_enabled:
set_bit(EFI_SECURE_BOOT, &efi.flags);
pr_info("Secure boot enabled\n");
break;
default:
pr_warn("Secure boot could not be determined (mode %u)\n",
mode);
break;
}
}
}

View File

@ -322,19 +322,12 @@ static int rmi_input_event(struct hid_device *hdev, u8 *data, int size)
{
struct rmi_data *hdata = hid_get_drvdata(hdev);
struct rmi_device *rmi_dev = hdata->xport.rmi_dev;
unsigned long flags;
if (!(test_bit(RMI_STARTED, &hdata->flags)))
return 0;
local_irq_save(flags);
rmi_set_attn_data(rmi_dev, data[1], &data[2], size - 2);
generic_handle_irq(hdata->rmi_irq);
local_irq_restore(flags);
return 1;
}
@ -591,56 +584,6 @@ static const struct rmi_transport_ops hid_rmi_ops = {
.reset = rmi_hid_reset,
};
static void rmi_irq_teardown(void *data)
{
struct rmi_data *hdata = data;
struct irq_domain *domain = hdata->domain;
if (!domain)
return;
irq_dispose_mapping(irq_find_mapping(domain, 0));
irq_domain_remove(domain);
hdata->domain = NULL;
hdata->rmi_irq = 0;
}
static int rmi_irq_map(struct irq_domain *h, unsigned int virq,
irq_hw_number_t hw_irq_num)
{
irq_set_chip_and_handler(virq, &dummy_irq_chip, handle_simple_irq);
return 0;
}
static const struct irq_domain_ops rmi_irq_ops = {
.map = rmi_irq_map,
};
static int rmi_setup_irq_domain(struct hid_device *hdev)
{
struct rmi_data *hdata = hid_get_drvdata(hdev);
int ret;
hdata->domain = irq_domain_create_linear(hdev->dev.fwnode, 1,
&rmi_irq_ops, hdata);
if (!hdata->domain)
return -ENOMEM;
ret = devm_add_action_or_reset(&hdev->dev, &rmi_irq_teardown, hdata);
if (ret)
return ret;
hdata->rmi_irq = irq_create_mapping(hdata->domain, 0);
if (hdata->rmi_irq <= 0) {
hid_err(hdev, "Can't allocate an IRQ\n");
return hdata->rmi_irq < 0 ? hdata->rmi_irq : -ENXIO;
}
return 0;
}
static int rmi_probe(struct hid_device *hdev, const struct hid_device_id *id)
{
struct rmi_data *data = NULL;
@ -713,18 +656,11 @@ static int rmi_probe(struct hid_device *hdev, const struct hid_device_id *id)
mutex_init(&data->page_mutex);
ret = rmi_setup_irq_domain(hdev);
if (ret) {
hid_err(hdev, "failed to allocate IRQ domain\n");
return ret;
}
if (data->device_flags & RMI_DEVICE_HAS_PHYS_BUTTONS)
rmi_hid_pdata.gpio_data.disable = true;
data->xport.dev = hdev->dev.parent;
data->xport.pdata = rmi_hid_pdata;
data->xport.pdata.irq = data->rmi_irq;
data->xport.proto_name = "hid";
data->xport.ops = &hid_rmi_ops;

View File

@ -9,6 +9,7 @@
#include <linux/init.h>
#include <linux/types.h>
#include <linux/device.h>
#include <linux/dmi.h>
#include <linux/io.h>
#include <linux/err.h>
#include <linux/fs.h>
@ -2105,6 +2106,16 @@ static const struct amba_id etm4_ids[] = {
{},
};
static const struct dmi_system_id broken_coresight[] = {
{
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "HPE"),
DMI_MATCH(DMI_PRODUCT_NAME, "Apollo 70"),
},
},
{ } /* terminating entry */
};
MODULE_DEVICE_TABLE(amba, etm4_ids);
static struct amba_driver etm4x_amba_driver = {
@ -2138,6 +2149,11 @@ static int __init etm4x_init(void)
{
int ret;
if (dmi_check_system(broken_coresight)) {
pr_info("ETM4 disabled due to firmware bug\n");
return 0;
}
ret = etm4_pm_setup();
/* etm4_pm_setup() does its own cleanup - exit on error */
@ -2164,6 +2180,9 @@ clear_pm:
static void __exit etm4x_exit(void)
{
if (dmi_check_system(broken_coresight))
return;
amba_driver_unregister(&etm4x_amba_driver);
platform_driver_unregister(&etm4_platform_driver);
etm4_pm_clear();

View File

@ -182,42 +182,54 @@ void rmi_set_attn_data(struct rmi_device *rmi_dev, unsigned long irq_status,
attn_data.data = fifo_data;
kfifo_put(&drvdata->attn_fifo, attn_data);
schedule_work(&drvdata->attn_work);
}
EXPORT_SYMBOL_GPL(rmi_set_attn_data);
static irqreturn_t rmi_irq_fn(int irq, void *dev_id)
static void attn_callback(struct work_struct *work)
{
struct rmi_device *rmi_dev = dev_id;
struct rmi_driver_data *drvdata = dev_get_drvdata(&rmi_dev->dev);
struct rmi_driver_data *drvdata = container_of(work,
struct rmi_driver_data,
attn_work);
struct rmi4_attn_data attn_data = {0};
int ret, count;
count = kfifo_get(&drvdata->attn_fifo, &attn_data);
if (count) {
*(drvdata->irq_status) = attn_data.irq_status;
drvdata->attn_data = attn_data;
}
if (!count)
return;
*(drvdata->irq_status) = attn_data.irq_status;
drvdata->attn_data = attn_data;
ret = rmi_process_interrupt_requests(drvdata->rmi_dev);
if (ret)
rmi_dbg(RMI_DEBUG_CORE, &drvdata->rmi_dev->dev,
"Failed to process interrupt request: %d\n", ret);
kfree(attn_data.data);
drvdata->attn_data.data = NULL;
if (!kfifo_is_empty(&drvdata->attn_fifo))
schedule_work(&drvdata->attn_work);
}
static irqreturn_t rmi_irq_fn(int irq, void *dev_id)
{
struct rmi_device *rmi_dev = dev_id;
int ret;
ret = rmi_process_interrupt_requests(rmi_dev);
if (ret)
rmi_dbg(RMI_DEBUG_CORE, &rmi_dev->dev,
"Failed to process interrupt request: %d\n", ret);
if (count) {
kfree(attn_data.data);
drvdata->attn_data.data = NULL;
}
if (!kfifo_is_empty(&drvdata->attn_fifo))
return rmi_irq_fn(irq, dev_id);
return IRQ_HANDLED;
}
static int rmi_irq_init(struct rmi_device *rmi_dev)
{
struct rmi_device_platform_data *pdata = rmi_get_platform_data(rmi_dev);
struct rmi_driver_data *data = dev_get_drvdata(&rmi_dev->dev);
int irq_flags = irq_get_trigger_type(pdata->irq);
int ret;
@ -235,8 +247,6 @@ static int rmi_irq_init(struct rmi_device *rmi_dev)
return ret;
}
data->enabled = true;
return 0;
}
@ -886,23 +896,27 @@ void rmi_enable_irq(struct rmi_device *rmi_dev, bool clear_wake)
if (data->enabled)
goto out;
enable_irq(irq);
data->enabled = true;
if (clear_wake && device_may_wakeup(rmi_dev->xport->dev)) {
retval = disable_irq_wake(irq);
if (retval)
dev_warn(&rmi_dev->dev,
"Failed to disable irq for wake: %d\n",
retval);
}
if (irq) {
enable_irq(irq);
data->enabled = true;
if (clear_wake && device_may_wakeup(rmi_dev->xport->dev)) {
retval = disable_irq_wake(irq);
if (retval)
dev_warn(&rmi_dev->dev,
"Failed to disable irq for wake: %d\n",
retval);
}
/*
* Call rmi_process_interrupt_requests() after enabling irq,
* otherwise we may lose interrupt on edge-triggered systems.
*/
irq_flags = irq_get_trigger_type(pdata->irq);
if (irq_flags & IRQ_TYPE_EDGE_BOTH)
rmi_process_interrupt_requests(rmi_dev);
/*
* Call rmi_process_interrupt_requests() after enabling irq,
* otherwise we may lose interrupt on edge-triggered systems.
*/
irq_flags = irq_get_trigger_type(pdata->irq);
if (irq_flags & IRQ_TYPE_EDGE_BOTH)
rmi_process_interrupt_requests(rmi_dev);
} else {
data->enabled = true;
}
out:
mutex_unlock(&data->enabled_mutex);
@ -922,20 +936,22 @@ void rmi_disable_irq(struct rmi_device *rmi_dev, bool enable_wake)
goto out;
data->enabled = false;
disable_irq(irq);
if (enable_wake && device_may_wakeup(rmi_dev->xport->dev)) {
retval = enable_irq_wake(irq);
if (retval)
dev_warn(&rmi_dev->dev,
"Failed to enable irq for wake: %d\n",
retval);
}
/* make sure the fifo is clean */
while (!kfifo_is_empty(&data->attn_fifo)) {
count = kfifo_get(&data->attn_fifo, &attn_data);
if (count)
kfree(attn_data.data);
if (irq) {
disable_irq(irq);
if (enable_wake && device_may_wakeup(rmi_dev->xport->dev)) {
retval = enable_irq_wake(irq);
if (retval)
dev_warn(&rmi_dev->dev,
"Failed to enable irq for wake: %d\n",
retval);
}
} else {
/* make sure the fifo is clean */
while (!kfifo_is_empty(&data->attn_fifo)) {
count = kfifo_get(&data->attn_fifo, &attn_data);
if (count)
kfree(attn_data.data);
}
}
out:
@ -981,6 +997,8 @@ static int rmi_driver_remove(struct device *dev)
irq_domain_remove(data->irqdomain);
data->irqdomain = NULL;
cancel_work_sync(&data->attn_work);
rmi_f34_remove_sysfs(rmi_dev);
rmi_free_function_list(rmi_dev);
@ -1219,9 +1237,15 @@ static int rmi_driver_probe(struct device *dev)
}
}
retval = rmi_irq_init(rmi_dev);
if (retval < 0)
goto err_destroy_functions;
if (pdata->irq) {
retval = rmi_irq_init(rmi_dev);
if (retval < 0)
goto err_destroy_functions;
}
data->enabled = true;
INIT_WORK(&data->attn_work, attn_callback);
if (data->f01_container->dev.driver) {
/* Driver already bound, so enable ATTN now. */

View File

@ -7,6 +7,7 @@
#define pr_fmt(fmt) "iommu: " fmt
#include <linux/device.h>
#include <linux/dmi.h>
#include <linux/dma-iommu.h>
#include <linux/kernel.h>
#include <linux/bits.h>
@ -3118,6 +3119,27 @@ u32 iommu_sva_get_pasid(struct iommu_sva *handle)
}
EXPORT_SYMBOL_GPL(iommu_sva_get_pasid);
#ifdef CONFIG_ARM64
static int __init iommu_quirks(void)
{
const char *vendor, *name;
vendor = dmi_get_system_info(DMI_SYS_VENDOR);
name = dmi_get_system_info(DMI_PRODUCT_NAME);
if (vendor &&
(strncmp(vendor, "GIGABYTE", 8) == 0 && name &&
(strncmp(name, "R120", 4) == 0 ||
strncmp(name, "R270", 4) == 0))) {
pr_warn("Gigabyte %s detected, force iommu passthrough mode", name);
iommu_def_domain_type = IOMMU_DOMAIN_IDENTITY;
}
return 0;
}
arch_initcall(iommu_quirks);
#endif
/*
* Changes the default domain of an iommu group that has *only* one device
*

View File

@ -5318,6 +5318,11 @@ mptsas_probe(struct pci_dev *pdev, const struct pci_device_id *id)
ioc, MPI_SAS_OP_CLEAR_ALL_PERSISTENT);
}
#ifdef CONFIG_RHEL_DIFFERENCES
add_taint(TAINT_SUPPORT_REMOVED, LOCKDEP_STILL_OK);
pr_warn("MPTSAS MODULE IS NOT SUPPORTED\n");
#endif
error = scsi_add_host(sh, &ioc->pcidev->dev);
if (error) {
dprintk(ioc, printk(MYIOC_s_ERR_FMT
@ -5381,6 +5386,10 @@ static void mptsas_remove(struct pci_dev *pdev)
}
static struct pci_device_id mptsas_pci_table[] = {
#ifdef CONFIG_RHEL_DIFFERENCES
{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_SAS1068,
PCI_VENDOR_ID_VMWARE, PCI_ANY_ID },
#else
{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_SAS1064,
PCI_ANY_ID, PCI_ANY_ID },
{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_SAS1068,
@ -5393,6 +5402,7 @@ static struct pci_device_id mptsas_pci_table[] = {
PCI_ANY_ID, PCI_ANY_ID },
{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_SAS1068_820XELP,
PCI_ANY_ID, PCI_ANY_ID },
#endif
{0} /* Terminating entry */
};
MODULE_DEVICE_TABLE(pci, mptsas_pci_table);

View File

@ -1238,12 +1238,17 @@ static struct spi_function_template mptspi_transport_functions = {
*/
static struct pci_device_id mptspi_pci_table[] = {
#ifdef CONFIG_RHEL_DIFFERENCES
{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_53C1030,
PCI_VENDOR_ID_VMWARE, PCI_ANY_ID },
#else
{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_53C1030,
PCI_ANY_ID, PCI_ANY_ID },
{ PCI_VENDOR_ID_ATTO, MPI_MANUFACTPAGE_DEVID_53C1030,
PCI_ANY_ID, PCI_ANY_ID },
{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_53C1035,
PCI_ANY_ID, PCI_ANY_ID },
#endif
{0} /* Terminating entry */
};
MODULE_DEVICE_TABLE(pci, mptspi_pci_table);
@ -1534,6 +1539,12 @@ mptspi_probe(struct pci_dev *pdev, const struct pci_device_id *id)
0, 0, 0, 0, 5);
scsi_scan_host(sh);
#ifdef CONFIG_RHEL_DIFFERENCES
add_taint(TAINT_SUPPORT_REMOVED, LOCKDEP_STILL_OK);
pr_warn("MPTSPI MODULE IS NOT SUPPORTED\n");
#endif
return 0;
out_mptspi_probe:

View File

@ -3045,6 +3045,8 @@ static int __init team_module_init(void)
if (err)
goto err_nl_init;
mark_hardware_deprecated(DRV_NAME);
return 0;
err_nl_init:

View File

@ -12,6 +12,7 @@
#include <uapi/linux/wireguard.h>
#include <linux/fips.h>
#include <linux/init.h>
#include <linux/module.h>
#include <linux/genetlink.h>
@ -21,6 +22,11 @@ static int __init mod_init(void)
{
int ret;
#ifdef CONFIG_RHEL_DIFFERENCES
if (fips_enabled)
return -EOPNOTSUPP;
#endif
ret = wg_allowedips_slab_init();
if (ret < 0)
goto err_allowedips;
@ -48,6 +54,7 @@ static int __init mod_init(void)
pr_info("WireGuard " WIREGUARD_VERSION " loaded. See www.wireguard.com for information.\n");
pr_info("Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.\n");
mark_tech_preview("WireGuard", THIS_MODULE);
return 0;
err_netlink:

View File

@ -262,6 +262,9 @@ static void nvme_delete_ctrl_sync(struct nvme_ctrl *ctrl)
static blk_status_t nvme_error_status(u16 status)
{
if (unlikely(status & NVME_SC_DNR))
return BLK_STS_TARGET;
switch (status & 0x7ff) {
case NVME_SC_SUCCESS:
return BLK_STS_OK;
@ -321,6 +324,7 @@ enum nvme_disposition {
COMPLETE,
RETRY,
FAILOVER,
FAILUP,
};
static inline enum nvme_disposition nvme_decide_disposition(struct request *req)
@ -328,15 +332,16 @@ static inline enum nvme_disposition nvme_decide_disposition(struct request *req)
if (likely(nvme_req(req)->status == 0))
return COMPLETE;
if (blk_noretry_request(req) ||
if ((req->cmd_flags & (REQ_FAILFAST_DEV | REQ_FAILFAST_DRIVER)) ||
(nvme_req(req)->status & NVME_SC_DNR) ||
nvme_req(req)->retries >= nvme_max_retries)
return COMPLETE;
if (req->cmd_flags & REQ_NVME_MPATH) {
if (req->cmd_flags & (REQ_NVME_MPATH | REQ_FAILFAST_TRANSPORT)) {
if (nvme_is_path_error(nvme_req(req)->status) ||
blk_queue_dying(req->q))
return FAILOVER;
return (req->cmd_flags & REQ_NVME_MPATH) ?
FAILOVER : FAILUP;
} else {
if (blk_queue_dying(req->q))
return COMPLETE;
@ -358,6 +363,14 @@ static inline void nvme_end_req(struct request *req)
blk_mq_end_request(req, status);
}
static inline void nvme_failup_req(struct request *req)
{
nvme_update_ana(req);
nvme_req(req)->status = NVME_SC_HOST_PATH_ERROR;
nvme_end_req(req);
}
void nvme_complete_rq(struct request *req)
{
trace_nvme_complete_rq(req);
@ -376,6 +389,9 @@ void nvme_complete_rq(struct request *req)
case FAILOVER:
nvme_failover_req(req);
return;
case FAILUP:
nvme_failup_req(req);
return;
}
}
EXPORT_SYMBOL_GPL(nvme_complete_rq);

View File

@ -65,14 +65,10 @@ bool nvme_mpath_set_disk_name(struct nvme_ns *ns, char *disk_name, int *flags)
return true;
}
void nvme_failover_req(struct request *req)
void nvme_update_ana(struct request *req)
{
struct nvme_ns *ns = req->q->queuedata;
u16 status = nvme_req(req)->status & 0x7ff;
unsigned long flags;
struct bio *bio;
nvme_mpath_clear_current_path(ns);
/*
* If we got back an ANA error, we know the controller is alive but not
@ -83,6 +79,16 @@ void nvme_failover_req(struct request *req)
set_bit(NVME_NS_ANA_PENDING, &ns->flags);
queue_work(nvme_wq, &ns->ctrl->ana_work);
}
}
void nvme_failover_req(struct request *req)
{
struct nvme_ns *ns = req->q->queuedata;
unsigned long flags;
struct bio *bio;
nvme_mpath_clear_current_path(ns);
nvme_update_ana(req);
spin_lock_irqsave(&ns->head->requeue_lock, flags);
for (bio = req->bio; bio; bio = bio->bi_next)
@ -816,8 +822,7 @@ int nvme_mpath_init_identify(struct nvme_ctrl *ctrl, struct nvme_id_ctrl *id)
int error = 0;
/* check if multipath is enabled and we have the capability */
if (!multipath || !ctrl->subsys ||
!(ctrl->subsys->cmic & NVME_CTRL_CMIC_ANA))
if (!ctrl->subsys || !(ctrl->subsys->cmic & NVME_CTRL_CMIC_ANA))
return 0;
if (!ctrl->max_namespaces ||

View File

@ -746,6 +746,7 @@ void nvme_mpath_wait_freeze(struct nvme_subsystem *subsys);
void nvme_mpath_start_freeze(struct nvme_subsystem *subsys);
bool nvme_mpath_set_disk_name(struct nvme_ns *ns, char *disk_name, int *flags);
void nvme_failover_req(struct request *req);
void nvme_update_ana(struct request *req);
void nvme_kick_requeue_lists(struct nvme_ctrl *ctrl);
int nvme_mpath_alloc_disk(struct nvme_ctrl *ctrl,struct nvme_ns_head *head);
void nvme_mpath_add_disk(struct nvme_ns *ns, struct nvme_id_ns *id);
@ -784,6 +785,9 @@ static inline bool nvme_mpath_set_disk_name(struct nvme_ns *ns, char *disk_name,
static inline void nvme_failover_req(struct request *req)
{
}
static inline void nvme_update_ana(struct request *req)
{
}
static inline void nvme_kick_requeue_lists(struct nvme_ctrl *ctrl)
{
}

View File

@ -19,6 +19,7 @@
#include <linux/kexec.h>
#include <linux/of_device.h>
#include <linux/acpi.h>
#include <linux/kernel.h>
#include <linux/dma-map-ops.h>
#include "pci.h"
#include "pcie/portdrv.h"
@ -295,6 +296,34 @@ static struct attribute *pci_drv_attrs[] = {
};
ATTRIBUTE_GROUPS(pci_drv);
/**
* pci_hw_vendor_status - Tell if a PCI device is supported by the HW vendor
* @ids: array of PCI device id structures to search in
* @dev: the PCI device structure to match against
*
* Used by a driver to check whether this device is in its list of unsupported
* devices. Returns the matching pci_device_id structure or %NULL if there is
* no match.
*
* Reserved for Internal Red Hat use only.
*/
const struct pci_device_id *pci_hw_vendor_status(
const struct pci_device_id *ids,
struct pci_dev *dev)
{
char devinfo[64];
const struct pci_device_id *ret = pci_match_id(ids, dev);
if (ret) {
snprintf(devinfo, sizeof(devinfo), "%s %s",
dev_driver_string(&dev->dev), dev_name(&dev->dev));
mark_hardware_deprecated(devinfo);
}
return ret;
}
EXPORT_SYMBOL(pci_hw_vendor_status);
struct drv_dev_and_id {
struct pci_driver *drv;
struct pci_dev *dev;

View File

@ -4268,6 +4268,30 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9000,
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9084,
quirk_bridge_cavm_thrx2_pcie_root);
/*
* PCI BAR 5 is not setup correctly for the on-board AHCI controller
* on Broadcom's Vulcan processor. Added a quirk to fix BAR 5 by
* using BAR 4's resources which are populated correctly and NOT
* actually used by the AHCI controller.
*/
static void quirk_fix_vulcan_ahci_bars(struct pci_dev *dev)
{
struct resource *r = &dev->resource[4];
if (!(r->flags & IORESOURCE_MEM) || (r->start == 0))
return;
/* Set BAR5 resource to BAR4 */
dev->resource[5] = *r;
/* Update BAR5 in pci config space */
pci_write_config_dword(dev, PCI_BASE_ADDRESS_5, r->start);
/* Clear BAR4's resource */
memset(r, 0, sizeof(*r));
}
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9027, quirk_fix_vulcan_ahci_bars);
/*
* Intersil/Techwell TW686[4589]-based video capture cards have an empty (zero)
* class code. Fix it.

View File

@ -78,6 +78,7 @@ char aac_driver_version[] = AAC_DRIVER_FULL_VERSION;
* Note: The last field is used to index into aac_drivers below.
*/
static const struct pci_device_id aac_pci_tbl[] = {
#ifndef CONFIG_RHEL_DIFFERENCES
{ 0x1028, 0x0001, 0x1028, 0x0001, 0, 0, 0 }, /* PERC 2/Si (Iguana/PERC2Si) */
{ 0x1028, 0x0002, 0x1028, 0x0002, 0, 0, 1 }, /* PERC 3/Di (Opal/PERC3Di) */
{ 0x1028, 0x0003, 0x1028, 0x0003, 0, 0, 2 }, /* PERC 3/Si (SlimFast/PERC3Si */
@ -145,6 +146,7 @@ static const struct pci_device_id aac_pci_tbl[] = {
{ 0x9005, 0x0285, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 59 }, /* Adaptec Catch All */
{ 0x9005, 0x0286, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 60 }, /* Adaptec Rocket Catch All */
{ 0x9005, 0x0288, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 61 }, /* Adaptec NEMER/ARK Catch All */
#endif
{ 0x9005, 0x028b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 62 }, /* Adaptec PMC Series 6 (Tupelo) */
{ 0x9005, 0x028c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 63 }, /* Adaptec PMC Series 7 (Denali) */
{ 0x9005, 0x028d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 64 }, /* Adaptec PMC Series 8 */

View File

@ -369,11 +369,13 @@ end_reset:
/*------------------- PCI Driver operations and data ----------------- */
static const struct pci_device_id beiscsi_pci_id_table[] = {
#ifndef CONFIG_RHEL_DIFFERENCES
{ PCI_DEVICE(BE_VENDOR_ID, BE_DEVICE_ID1) },
{ PCI_DEVICE(BE_VENDOR_ID, BE_DEVICE_ID2) },
{ PCI_DEVICE(BE_VENDOR_ID, OC_DEVICE_ID1) },
{ PCI_DEVICE(BE_VENDOR_ID, OC_DEVICE_ID2) },
{ PCI_DEVICE(BE_VENDOR_ID, OC_DEVICE_ID3) },
#endif
{ PCI_DEVICE(ELX_VENDOR_ID, OC_SKH_ID1) },
{ 0 }
};

View File

@ -82,7 +82,9 @@ MODULE_DESCRIPTION("Driver for HP Smart Array Controller version " \
HPSA_DRIVER_VERSION);
MODULE_VERSION(HPSA_DRIVER_VERSION);
MODULE_LICENSE("GPL");
#ifndef CONFIG_RHEL_DIFFERENCES
MODULE_ALIAS("cciss");
#endif
static int hpsa_simple_mode;
module_param(hpsa_simple_mode, int, S_IRUGO|S_IWUSR);
@ -144,10 +146,12 @@ static const struct pci_device_id hpsa_pci_device_id[] = {
{PCI_VENDOR_ID_HP_3PAR, 0x0075, 0x1590, 0x007D},
{PCI_VENDOR_ID_HP_3PAR, 0x0075, 0x1590, 0x0088},
{PCI_VENDOR_ID_HP, 0x333f, 0x103c, 0x333f},
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_HP, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
PCI_CLASS_STORAGE_RAID << 8, 0xffff << 8, 0},
{PCI_VENDOR_ID_COMPAQ, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
PCI_CLASS_STORAGE_RAID << 8, 0xffff << 8, 0},
#endif
{0,}
};

View File

@ -24,6 +24,7 @@
#include <linux/pci.h>
const struct pci_device_id lpfc_id_table[] = {
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_VIPER,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_FIREFLY,
@ -54,14 +55,19 @@ const struct pci_device_id lpfc_id_table[] = {
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_HELIOS_DCSP,
PCI_ANY_ID, PCI_ANY_ID, },
#endif
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_BMID,
PCI_ANY_ID, PCI_ANY_ID, },
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_BSMB,
PCI_ANY_ID, PCI_ANY_ID, },
#endif
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_ZEPHYR,
PCI_ANY_ID, PCI_ANY_ID, },
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_HORNET,
PCI_ANY_ID, PCI_ANY_ID, },
#endif
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_ZEPHYR_SCSP,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_ZEPHYR_DCSP,
@ -70,6 +76,7 @@ const struct pci_device_id lpfc_id_table[] = {
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_ZSMB,
PCI_ANY_ID, PCI_ANY_ID, },
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_TFLY,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LP101,
@ -80,6 +87,7 @@ const struct pci_device_id lpfc_id_table[] = {
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LPE11000S,
PCI_ANY_ID, PCI_ANY_ID, },
#endif
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_SAT,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_SAT_MID,
@ -92,6 +100,7 @@ const struct pci_device_id lpfc_id_table[] = {
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_SAT_S,
PCI_ANY_ID, PCI_ANY_ID, },
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_PROTEUS_VF,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_PROTEUS_PF,
@ -102,18 +111,23 @@ const struct pci_device_id lpfc_id_table[] = {
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_SERVERENGINE, PCI_DEVICE_ID_TOMCAT,
PCI_ANY_ID, PCI_ANY_ID, },
#endif
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_FALCON,
PCI_ANY_ID, PCI_ANY_ID, },
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_BALIUS,
PCI_ANY_ID, PCI_ANY_ID, },
#endif
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LANCER_FC,
PCI_ANY_ID, PCI_ANY_ID, },
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LANCER_FCOE,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LANCER_FC_VF,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LANCER_FCOE_VF,
PCI_ANY_ID, PCI_ANY_ID, },
#endif
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LANCER_G6_FC,
PCI_ANY_ID, PCI_ANY_ID, },
{PCI_VENDOR_ID_EMULEX, PCI_DEVICE_ID_LANCER_G7_FC,

View File

@ -149,6 +149,7 @@ megasas_set_ld_removed_by_fw(struct megasas_instance *instance);
*/
static struct pci_device_id megasas_pci_table[] = {
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_SAS1064R)},
/* xscale IOP */
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_SAS1078R)},
@ -157,16 +158,19 @@ static struct pci_device_id megasas_pci_table[] = {
/* ppc IOP */
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_SAS1078GEN2)},
/* gen2*/
#endif
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_SAS0079GEN2)},
/* gen2*/
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_SAS0073SKINNY)},
/* skinny*/
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_SAS0071SKINNY)},
/* skinny*/
#ifndef CONFIG_RHEL_DIFFERENCES
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_VERDE_ZCR)},
/* xscale IOP, vega */
{PCI_DEVICE(PCI_VENDOR_ID_DELL, PCI_DEVICE_ID_DELL_PERC5)},
/* xscale IOP */
#endif
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_FUSION)},
/* Fusion */
{PCI_DEVICE(PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_PLASMA)},

View File

@ -12547,6 +12547,7 @@ bool scsih_ncq_prio_supp(struct scsi_device *sdev)
* The pci device ids are defined in mpi/mpi2_cnfg.h.
*/
static const struct pci_device_id mpt3sas_pci_table[] = {
#ifndef CONFIG_RHEL_DIFFERENCES
/* Spitfire ~ 2004 */
{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2004,
PCI_ANY_ID, PCI_ANY_ID },
@ -12565,6 +12566,7 @@ static const struct pci_device_id mpt3sas_pci_table[] = {
PCI_ANY_ID, PCI_ANY_ID },
{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2116_2,
PCI_ANY_ID, PCI_ANY_ID },
#endif
/* Thunderbolt ~ 2208 */
{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2208_1,
PCI_ANY_ID, PCI_ANY_ID },
@ -12589,9 +12591,11 @@ static const struct pci_device_id mpt3sas_pci_table[] = {
PCI_ANY_ID, PCI_ANY_ID },
{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SWITCH_MPI_EP_1,
PCI_ANY_ID, PCI_ANY_ID },
#ifndef CONFIG_RHEL_DIFFERENCES
/* SSS6200 */
{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SSS6200,
PCI_ANY_ID, PCI_ANY_ID },
#endif
/* Fury ~ 3004 and 3008 */
{ MPI2_MFGPAGE_VENDORID_LSI, MPI25_MFGPAGE_DEVID_SAS3004,
PCI_ANY_ID, PCI_ANY_ID },

View File

@ -7960,6 +7960,7 @@ static const struct pci_error_handlers qla2xxx_err_handler = {
};
static struct pci_device_id qla2xxx_pci_tbl[] = {
#ifndef CONFIG_RHEL_DIFFERENCES
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2100) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2200) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2300) },
@ -7972,13 +7973,18 @@ static struct pci_device_id qla2xxx_pci_tbl[] = {
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP8432) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP5422) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP5432) },
#endif
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2532) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2031) },
#ifndef CONFIG_RHEL_DIFFERENCES
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP8001) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP8021) },
#endif
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP8031) },
#ifndef CONFIG_RHEL_DIFFERENCES
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISPF001) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP8044) },
#endif
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2071) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2271) },
{ PCI_DEVICE(PCI_VENDOR_ID_QLOGIC, PCI_DEVICE_ID_QLOGIC_ISP2261) },

View File

@ -9855,6 +9855,7 @@ static struct pci_device_id qla4xxx_pci_tbl[] = {
.subvendor = PCI_ANY_ID,
.subdevice = PCI_ANY_ID,
},
#ifndef CONFIG_RHEL_DIFFERENCES
{
.vendor = PCI_VENDOR_ID_QLOGIC,
.device = PCI_DEVICE_ID_QLOGIC_ISP8022,
@ -9873,6 +9874,7 @@ static struct pci_device_id qla4xxx_pci_tbl[] = {
.subvendor = PCI_ANY_ID,
.subdevice = PCI_ANY_ID,
},
#endif
{0, 0},
};
MODULE_DEVICE_TABLE(pci, qla4xxx_pci_tbl);

View File

@ -5657,6 +5657,13 @@ static void hub_event(struct work_struct *work)
(u16) hub->change_bits[0],
(u16) hub->event_bits[0]);
/* Don't disconnect USB-SATA on TrimSlice */
if (strcmp(dev_name(hdev->bus->controller), "tegra-ehci.0") == 0) {
if ((hdev->state == 7) && (hub->change_bits[0] == 0) &&
(hub->event_bits[0] == 0x2))
hub->event_bits[0] = 0;
}
/* Lock the device, then check to see if we were
* disconnected while waiting for the lock to succeed. */
usb_lock_device(hdev);

View File

@ -4298,6 +4298,7 @@ static int ext4_fill_super(struct super_block *sb, void *data, int silent)
set_bit(EXT4_FLAGS_BDEV_IS_DAX, &sbi->s_ext4_flags);
if (sbi->s_mount_opt & EXT4_MOUNT_DAX_ALWAYS) {
static bool printed = false;
if (ext4_has_feature_inline_data(sb)) {
ext4_msg(sb, KERN_ERR, "Cannot use DAX on a filesystem"
" that may contain inline data");
@ -4308,6 +4309,10 @@ static int ext4_fill_super(struct super_block *sb, void *data, int silent)
"DAX unsupported by block device.");
goto failed_mount;
}
if (!printed) {
mark_tech_preview("ext4 direct access (dax)", NULL);
printed = true;
}
}
if (ext4_has_feature_encrypt(sb) && es->s_encryption_level) {

View File

@ -1593,6 +1593,7 @@ xfs_fs_fill_super(
if (xfs_has_dax_always(mp)) {
bool rtdev_is_dax = false, datadev_is_dax;
static bool printed = false;
xfs_warn(mp,
"DAX enabled. Warning: EXPERIMENTAL, use at your own risk");
@ -1612,6 +1613,10 @@ xfs_fs_fill_super(
error = -EINVAL;
goto out_filestream_unmount;
}
if (!printed) {
mark_tech_preview("xfs direct access (dax)", NULL);
printed = true;
}
}
if (xfs_has_discard(mp)) {

View File

@ -43,6 +43,8 @@
#define EFI_ABORTED (21 | (1UL << (BITS_PER_LONG-1)))
#define EFI_SECURITY_VIOLATION (26 | (1UL << (BITS_PER_LONG-1)))
#define EFI_IS_ERROR(x) ((x) & (1UL << (BITS_PER_LONG-1)))
typedef unsigned long efi_status_t;
typedef u8 efi_bool_t;
typedef u16 efi_char16_t; /* UNICODE character */
@ -782,6 +784,14 @@ extern int __init efi_setup_pcdp_console(char *);
#define EFI_MEM_ATTR 10 /* Did firmware publish an EFI_MEMORY_ATTRIBUTES table? */
#define EFI_MEM_NO_SOFT_RESERVE 11 /* Is the kernel configured to ignore soft reservations? */
#define EFI_PRESERVE_BS_REGIONS 12 /* Are EFI boot-services memory segments available? */
#define EFI_SECURE_BOOT 13 /* Are we in Secure Boot mode? */
enum efi_secureboot_mode {
efi_secureboot_mode_unset,
efi_secureboot_mode_unknown,
efi_secureboot_mode_disabled,
efi_secureboot_mode_enabled,
};
#ifdef CONFIG_EFI
/*
@ -793,6 +803,8 @@ static inline bool efi_enabled(int feature)
}
extern void efi_reboot(enum reboot_mode reboot_mode, const char *__unused);
extern void __init efi_set_secure_boot(enum efi_secureboot_mode mode);
bool __pure __efi_soft_reserve_enabled(void);
static inline bool __pure efi_soft_reserve_enabled(void)
@ -813,6 +825,8 @@ static inline bool efi_enabled(int feature)
static inline void
efi_reboot(enum reboot_mode reboot_mode, const char *__unused) {}
static inline void efi_set_secure_boot(enum efi_secureboot_mode mode) {}
static inline bool efi_soft_reserve_enabled(void)
{
return false;
@ -825,6 +839,7 @@ static inline bool efi_rt_services_supported(unsigned int mask)
#endif
extern int efi_status_to_err(efi_status_t status);
extern const char *efi_status_to_str(efi_status_t status);
/*
* Variable Attributes
@ -1077,13 +1092,6 @@ static inline bool efi_runtime_disabled(void) { return true; }
extern void efi_call_virt_check_flags(unsigned long flags, const char *call);
extern unsigned long efi_call_virt_save_flags(void);
enum efi_secureboot_mode {
efi_secureboot_mode_unset,
efi_secureboot_mode_unknown,
efi_secureboot_mode_disabled,
efi_secureboot_mode_enabled,
};
static inline
enum efi_secureboot_mode efi_get_secureboot_mode(efi_get_variable_t *get_var)
{

View File

@ -530,4 +530,21 @@ static inline void ftrace_dump(enum ftrace_dump_mode oops_dump_mode) { }
/* OTHER_WRITABLE? Generally considered a bad idea. */ \
BUILD_BUG_ON_ZERO((perms) & 2) + \
(perms))
struct module;
#ifdef CONFIG_RHEL_DIFFERENCES
void mark_hardware_unsupported(const char *msg);
void mark_hardware_deprecated(const char *msg);
void mark_tech_preview(const char *msg, struct module *mod);
void mark_driver_unsupported(const char *name);
void mark_driver_deprecated(const char *name);
#else
static inline void mark_hardware_unsupported(const char *msg) { }
static inline void mark_hardware_deprecated(const char *msg) { }
static inline void mark_tech_preview(const char *msg, struct module *mod) { }
static inline void mark_driver_unsupported(const char *name) { }
static inline void mark_driver_deprecated(const char *name) { }
#endif
#endif

View File

@ -394,6 +394,8 @@ LSM_HOOK(void, LSM_RET_VOID, bpf_prog_free_security, struct bpf_prog_aux *aux)
#endif /* CONFIG_BPF_SYSCALL */
LSM_HOOK(int, 0, locked_down, enum lockdown_reason what)
LSM_HOOK(int, 0, lock_kernel_down, const char *where, enum lockdown_reason level)
#ifdef CONFIG_PERF_EVENTS
LSM_HOOK(int, 0, perf_event_open, struct perf_event_attr *attr, int type)

View File

@ -1545,6 +1545,12 @@
*
* @what: kernel feature being accessed
*
* @lock_kernel_down
* Put the kernel into lock-down mode.
*
* @where: Where the lock-down is originating from (e.g. command line option)
* @level: The lock-down level (can only increase)
*
* Security hooks for perf events
*
* @perf_event_open:

View File

@ -380,6 +380,7 @@ struct module {
struct module_attribute *modinfo_attrs;
const char *version;
const char *srcversion;
const char *rhelversion;
struct kobject *holders_dir;
/* Exported symbols */

View File

@ -74,7 +74,24 @@ static inline void set_arch_panic_timeout(int timeout, int arch_default_timeout)
#define TAINT_LIVEPATCH 15
#define TAINT_AUX 16
#define TAINT_RANDSTRUCT 17
#define TAINT_FLAGS_COUNT 18
/* Start of Red Hat-specific taint flags */
#define TAINT_18 18
#define TAINT_19 19
#define TAINT_20 20
#define TAINT_21 21
#define TAINT_22 22
#define TAINT_23 23
#define TAINT_24 24
#define TAINT_25 25
#define TAINT_26 26
#define TAINT_SUPPORT_REMOVED 27
/* Bits 28 - 31 are reserved for Red Hat use only */
#define TAINT_RESERVED28 28
#define TAINT_RESERVED29 29
#define TAINT_RESERVED30 30
#define TAINT_UNPRIVILEGED_BPF 31
/* End of Red Hat-specific taint flags */
#define TAINT_FLAGS_COUNT 32
#define TAINT_FLAGS_MAX ((1UL << TAINT_FLAGS_COUNT) - 1)
struct taint_flag {

View File

@ -1470,6 +1470,10 @@ int pci_add_dynid(struct pci_driver *drv,
unsigned long driver_data);
const struct pci_device_id *pci_match_id(const struct pci_device_id *ids,
struct pci_dev *dev);
/* Reserved for Internal Red Hat use only */
const struct pci_device_id *pci_hw_vendor_status(
const struct pci_device_id *ids,
struct pci_dev *dev);
int pci_scan_bridge(struct pci_bus *bus, struct pci_dev *dev, int max,
int pass);

View File

@ -14,6 +14,11 @@
#include <uapi/linux/random.h>
struct random_extrng {
ssize_t (*extrng_read)(void __user *buf, size_t buflen);
struct module *owner;
};
struct random_ready_callback {
struct list_head list;
void (*func)(struct random_ready_callback *rdy);
@ -44,6 +49,8 @@ extern bool rng_is_initialized(void);
extern int add_random_ready_callback(struct random_ready_callback *rdy);
extern void del_random_ready_callback(struct random_ready_callback *rdy);
extern int __must_check get_random_bytes_arch(void *buf, int nbytes);
void random_register_extrng(const struct random_extrng *rng);
void random_unregister_extrng(void);
#ifndef MODULE
extern const struct file_operations random_fops, urandom_fops;

297
include/linux/rh_kabi.h Normal file
View File

@ -0,0 +1,297 @@
/*
* rh_kabi.h - Red Hat kABI abstraction header
*
* Copyright (c) 2014 Don Zickus
* Copyright (c) 2015-2018 Jiri Benc
* Copyright (c) 2015 Sabrina Dubroca, Hannes Frederic Sowa
* Copyright (c) 2016-2018 Prarit Bhargava
* Copyright (c) 2017 Paolo Abeni, Larry Woodman
*
* This file is released under the GPLv2.
* See the file COPYING for more details.
*
* These kabi macros hide the changes from the kabi checker and from the
* process that computes the exported symbols' checksums.
* They have 2 variants: one (defined under __GENKSYMS__) used when
* generating the checksums, and the other used when building the kernel's
* binaries.
*
* The use of these macros does not guarantee that the usage and modification
* of code is correct. As with all Red Hat only changes, an engineer must
* explain why the use of the macro is valid in the patch containing the
* changes.
*
*/
#ifndef _LINUX_RH_KABI_H
#define _LINUX_RH_KABI_H
#include <linux/compiler.h>
#include <linux/stringify.h>
/*
* RH_KABI_CONST
* Adds a new const modifier to a function parameter preserving the old
* checksum.
*
* RH_KABI_DEPRECATE
* Mark the element as deprecated and make it unusable by modules while
* preserving kABI checksums.
*
* RH_KABI_DEPRECATE_FN
* Mark the function pointer as deprecated and make it unusable by modules
* while preserving kABI checksums.
*
* RH_KABI_EXTEND
* Simple macro for adding a new element to a struct.
*
* RH_KABI_EXTEND_WITH_SIZE
* Adds a new element (usually a struct) to a struct and reserves extra
* space for the new element. The provided 'size' is the total space to
* be added in longs (i.e. it's 8 * 'size' bytes), including the size of
* the added element. It is automatically checked that the new element
* does not overflow the reserved space, now nor in the future. However,
* no attempt is done to check the content of the added element (struct)
* for kABI conformance - kABI checking inside the added element is
* effectively switched off.
* For any struct being added by RH_KABI_EXTEND_WITH_SIZE, it is
* recommended its content to be documented as not covered by kABI
* guarantee.
*
* RH_KABI_FILL_HOLE
* Simple macro for filling a hole in a struct.
*
* Warning: only use if a hole exists for _all_ arches. Use pahole to verify.
*
* RH_KABI_RENAME
* Simple macro for renaming an element without changing its type. This
* macro can be used in bitfields, for example.
*
* NOTE: does not include the final ';'
*
* RH_KABI_REPLACE
* Simple replacement of _orig with a union of _orig and _new.
*
* The RH_KABI_REPLACE* macros attempt to add the ability to use the '_new'
* element while preserving size alignment with the '_orig' element.
*
* The #ifdef __GENKSYMS__ preserves the kABI agreement, while the anonymous
* union structure preserves the size alignment (assuming the '_new' element
* is not bigger than the '_orig' element).
*
* RH_KABI_REPLACE_UNSAFE
* Unsafe version of RH_KABI_REPLACE. Only use for typedefs.
*
* RH_KABI_FORCE_CHANGE
* Force change of the symbol checksum. The argument of the macro is a
* version for cases we need to do this more than once.
*
* This macro does the opposite: it changes the symbol checksum without
* actually changing anything about the exported symbol. It is useful for
* symbols that are not whitelisted, we're changing them in an
* incompatible way and want to prevent 3rd party modules to silently
* corrupt memory. Instead, by changing the symbol checksum, such modules
* won't be loaded by the kernel. This macro should only be used as a
* last resort when all other KABI workarounds have failed.
*
* RH_KABI_EXCLUDE
* !!! WARNING: DANGEROUS, DO NOT USE unless you are aware of all the !!!
* !!! implications. This should be used ONLY EXCEPTIONALLY and only !!!
* !!! under specific circumstances. Very likely, this macro does not !!!
* !!! do what you expect it to do. Note that any usage of this macro !!!
* !!! MUST be paired with a RH_KABI_FORCE_CHANGE annotation of !!!
* !!! a suitable symbol (or an equivalent safeguard) and the commit !!!
* !!! log MUST explain why the chosen solution is appropriate. !!!
*
* Exclude the element from checksum generation. Any such element is
* considered not to be part of the kABI whitelist and may be changed at
* will. Note however that it's the responsibility of the developer
* changing the element to ensure 3rd party drivers using this element
* won't panic, for example by not allowing them to be loaded. That can
* be achieved by changing another, non-whitelisted symbol they use,
* either by nature of the change or by using RH_KABI_FORCE_CHANGE.
*
* Also note that any change to the element must preserve its size. Change
* of the size is not allowed and would constitute a silent kABI breakage.
* Beware that the RH_KABI_EXCLUDE macro does not do any size checks.
*
* NOTE
* Don't use ';' after these macros as it messes up the kABI checker by
* changing what the resulting token string looks like. Instead let this
* macro add the ';' so it can be properly hidden from the kABI checker
* (mainly for RH_KABI_EXTEND, but applied to all macros for uniformity).
*
*/
#ifdef __GENKSYMS__
# define RH_KABI_CONST
# define RH_KABI_EXTEND(_new)
# define RH_KABI_FILL_HOLE(_new)
# define RH_KABI_FORCE_CHANGE(ver) __attribute__((rh_kabi_change ## ver))
# define RH_KABI_RENAME(_orig, _new) _orig
# define _RH_KABI_DEPRECATE(_type, _orig) _type _orig
# define _RH_KABI_DEPRECATE_FN(_type, _orig, _args...) _type (*_orig)(_args)
# define _RH_KABI_REPLACE(_orig, _new) _orig
# define _RH_KABI_REPLACE_UNSAFE(_orig, _new) _orig
# define _RH_KABI_EXCLUDE(_elem)
#else
# define RH_KABI_ALIGN_WARNING ". Disable CONFIG_RH_KABI_SIZE_ALIGN_CHECKS if debugging."
# define RH_KABI_CONST const
# define RH_KABI_EXTEND(_new) _new;
# define RH_KABI_FILL_HOLE(_new) _new;
# define RH_KABI_FORCE_CHANGE(ver)
# define RH_KABI_RENAME(_orig, _new) _new
#if IS_BUILTIN(CONFIG_RH_KABI_SIZE_ALIGN_CHECKS)
# define __RH_KABI_CHECK_SIZE_ALIGN(_orig, _new) \
union { \
_Static_assert(sizeof(struct{_new;}) <= sizeof(struct{_orig;}), \
__FILE__ ":" __stringify(__LINE__) ": " __stringify(_new) " is larger than " __stringify(_orig) RH_KABI_ALIGN_WARNING); \
_Static_assert(__alignof__(struct{_new;}) <= __alignof__(struct{_orig;}), \
__FILE__ ":" __stringify(__LINE__) ": " __stringify(_orig) " is not aligned the same as " __stringify(_new) RH_KABI_ALIGN_WARNING); \
}
# define __RH_KABI_CHECK_SIZE(_item, _size) \
_Static_assert(sizeof(struct{_item;}) <= _size, \
__FILE__ ":" __stringify(__LINE__) ": " __stringify(_item) " is larger than the reserved size (" __stringify(_size) " bytes)" RH_KABI_ALIGN_WARNING)
#else
# define __RH_KABI_CHECK_SIZE_ALIGN(_orig, _new)
# define __RH_KABI_CHECK_SIZE(_item, _size)
#endif
#define RH_KABI_UNIQUE_ID __PASTE(rh_kabi_hidden_, __LINE__)
# define _RH_KABI_DEPRECATE(_type, _orig) _type rh_reserved_##_orig
# define _RH_KABI_DEPRECATE_FN(_type, _orig, _args...) \
_type (* rh_reserved_##_orig)(_args)
# define _RH_KABI_REPLACE(_orig, _new) \
union { \
_new; \
struct { \
_orig; \
} RH_KABI_UNIQUE_ID; \
__RH_KABI_CHECK_SIZE_ALIGN(_orig, _new); \
}
# define _RH_KABI_REPLACE_UNSAFE(_orig, _new) _new
# define _RH_KABI_EXCLUDE(_elem) _elem
#endif /* __GENKSYMS__ */
/* semicolon added wrappers for the RH_KABI_REPLACE macros */
# define RH_KABI_DEPRECATE(_type, _orig) _RH_KABI_DEPRECATE(_type, _orig);
# define RH_KABI_DEPRECATE_FN(_type, _orig, _args...) \
_RH_KABI_DEPRECATE_FN(_type, _orig, _args);
# define RH_KABI_REPLACE(_orig, _new) _RH_KABI_REPLACE(_orig, _new);
# define RH_KABI_REPLACE_UNSAFE(_orig, _new) _RH_KABI_REPLACE_UNSAFE(_orig, _new);
/*
* Macro for breaking up a random element into two smaller chunks using an
* anonymous struct inside an anonymous union.
*/
# define RH_KABI_REPLACE2(orig, _new1, _new2) RH_KABI_REPLACE(orig, struct{ _new1; _new2;})
# define RH_KABI_RESERVE(n) _RH_KABI_RESERVE(n);
/*
* Simple wrappers to replace standard Red Hat reserved elements.
*/
# define RH_KABI_USE(n, _new) RH_KABI_REPLACE(_RH_KABI_RESERVE(n), _new)
/*
* Macros for breaking up a reserved element into two smaller chunks using
* an anonymous struct inside an anonymous union.
*/
# define RH_KABI_USE2(n, _new1, _new2) RH_KABI_REPLACE(_RH_KABI_RESERVE(n), struct{ _new1; _new2; })
/*
* We tried to standardize on Red Hat reserved names. These wrappers
* leverage those common names making it easier to read and find in the
* code.
*/
# define _RH_KABI_RESERVE(n) unsigned long rh_reserved##n
#define RH_KABI_EXCLUDE(_elem) _RH_KABI_EXCLUDE(_elem);
/*
* Extending a struct while reserving extra space.
*/
#define RH_KABI_EXTEND_WITH_SIZE(_new, _size) \
RH_KABI_EXTEND(union { \
_new; \
unsigned long RH_KABI_UNIQUE_ID[_size]; \
__RH_KABI_CHECK_SIZE(_new, 8 * (_size)); \
})
/*
* RHEL macros to extend structs.
*
* base struct: The struct being extended. For example, pci_dev.
* extended struct: The Red Hat struct being added to the base struct.
* For example, pci_dev_rh.
*
* These macros should be used to extend structs before KABI freeze.
* They can be used post-KABI freeze in the limited case of the base
* struct not being embedded in another struct.
*
* Extended structs cannot be shrunk in size as changes will break
* the size & offset comparison.
*
* Extended struct elements are not guaranteed for access by modules unless
* explicitly commented as such in the declaration of the extended struct or
* the element in the extended struct.
*/
/*
* RH_KABI_SIZE_AND_EXTEND|_PTR() extends a struct by embedding or adding
* a pointer in a base struct. The name of the new struct is the name
* of the base struct appended with _rh.
*/
#define _RH_KABI_SIZE_AND_EXTEND_PTR(_struct) \
size_t _struct##_size_rh; \
RH_KABI_EXCLUDE(struct _struct##_rh *_struct##_rh)
#define RH_KABI_SIZE_AND_EXTEND_PTR(_struct) \
_RH_KABI_SIZE_AND_EXTEND_PTR(_struct)
#define _RH_KABI_SIZE_AND_EXTEND(_struct) \
size_t _struct##_size_rh; \
RH_KABI_EXCLUDE(struct _struct##_rh _struct##_rh)
#define RH_KABI_SIZE_AND_EXTEND(_struct) \
_RH_KABI_SIZE_AND_EXTEND(_struct)
/*
* RH_KABI_SET_SIZE calculates and sets the size of the extended struct and
* stores it in the size_rh field for structs that are dynamically allocated.
* This macro MUST be called when expanding a base struct with
* RH_KABI_SIZE_AND_EXTEND, and it MUST be called from the allocation site
* regardless of being allocated in the kernel or a module.
* Note: since this macro is intended to be invoked outside of a struct,
* a semicolon is necessary at the end of the line where it is invoked.
*/
#define RH_KABI_SET_SIZE(_name, _struct) ({ \
_name->_struct##_size_rh = sizeof(struct _struct##_rh); \
})
/*
* RH_KABI_INIT_SIZE calculates and sets the size of the extended struct and
* stores it in the size_rh field for structs that are statically allocated.
* This macro MUST be called when expanding a base struct with
* RH_KABI_SIZE_AND_EXTEND, and it MUST be called from the declaration site
* regardless of being allocated in the kernel or a module.
*/
#define RH_KABI_INIT_SIZE(_struct) \
._struct##_size_rh = sizeof(struct _struct##_rh),
/*
* RH_KABI_CHECK_EXT verifies allocated memory exists. This MUST be called to
* verify that memory in the _rh struct is valid, and can be called
* regardless if RH_KABI_SIZE_AND_EXTEND or RH_KABI_SIZE_AND_EXTEND_PTR is
* used.
*/
#define RH_KABI_CHECK_EXT(_ptr, _struct, _field) ({ \
size_t __off = offsetof(struct _struct##_rh, _field); \
_ptr->_struct##_size_rh > __off ? true : false; \
})
#endif /* _LINUX_RH_KABI_H */

View File

@ -364,6 +364,7 @@ struct rmi_driver_data {
struct rmi4_attn_data attn_data;
DECLARE_KFIFO(attn_fifo, struct rmi4_attn_data, 16);
struct work_struct attn_work;
};
int rmi_register_transport_device(struct rmi_transport_dev *xport);

View File

@ -472,6 +472,7 @@ int security_inode_notifysecctx(struct inode *inode, void *ctx, u32 ctxlen);
int security_inode_setsecctx(struct dentry *dentry, void *ctx, u32 ctxlen);
int security_inode_getsecctx(struct inode *inode, void **ctx, u32 *ctxlen);
int security_locked_down(enum lockdown_reason what);
int security_lock_kernel_down(const char *where, enum lockdown_reason level);
#else /* CONFIG_SECURITY */
static inline int call_blocking_lsm_notifier(enum lsm_event event, void *data)
@ -1348,6 +1349,10 @@ static inline int security_locked_down(enum lockdown_reason what)
{
return 0;
}
static inline int security_lock_kernel_down(const char *where, enum lockdown_reason level)
{
return 0;
}
#endif /* CONFIG_SECURITY */
#if defined(CONFIG_SECURITY) && defined(CONFIG_WATCH_QUEUE)

View File

@ -1648,7 +1648,7 @@ config AIO
this option saves about 7k.
config IO_URING
bool "Enable IO uring support" if EXPERT
bool "Enable IO uring support"
select IO_WQ
default y
help

View File

@ -12,6 +12,7 @@ obj-y = fork.o exec_domain.o panic.o \
notifier.o ksysfs.o cred.o reboot.o \
async.o range.o smpboot.o ucount.o regset.o
obj-$(CONFIG_RHEL_DIFFERENCES) += rh_taint.o
obj-$(CONFIG_USERMODE_DRIVER) += usermode_driver.o
obj-$(CONFIG_MODULES) += kmod.o
obj-$(CONFIG_MULTIUSER) += groups.o

View File

@ -24,6 +24,7 @@
#include <linux/ctype.h>
#include <linux/nospec.h>
#include <linux/audit.h>
#include <linux/init.h>
#include <uapi/linux/btf.h>
#include <linux/pgtable.h>
#include <linux/bpf_lsm.h>
@ -50,6 +51,23 @@ static DEFINE_SPINLOCK(map_idr_lock);
static DEFINE_IDR(link_idr);
static DEFINE_SPINLOCK(link_idr_lock);
static int __init unprivileged_bpf_setup(char *str)
{
unsigned long disabled;
if (!kstrtoul(str, 0, &disabled))
sysctl_unprivileged_bpf_disabled = !!disabled;
if (!sysctl_unprivileged_bpf_disabled) {
pr_warn("Unprivileged BPF has been enabled "
"(unprivileged_bpf_disabled=0 has been supplied "
"in boot parameters), tainting the kernel");
add_taint(TAINT_UNPRIVILEGED_BPF, LOCKDEP_STILL_OK);
}
return 1;
}
__setup("unprivileged_bpf_disabled=", unprivileged_bpf_setup);
int sysctl_unprivileged_bpf_disabled __read_mostly =
IS_BUILTIN(CONFIG_BPF_UNPRIV_DEFAULT_OFF) ? 2 : 0;

View File

@ -743,6 +743,7 @@ static struct module_attribute modinfo_##field = { \
MODINFO_ATTR(version);
MODINFO_ATTR(srcversion);
MODINFO_ATTR(rhelversion);
static char last_unloaded_module[MODULE_NAME_LEN+1];
@ -1206,6 +1207,7 @@ static struct module_attribute *modinfo_attrs[] = {
&module_uevent,
&modinfo_version,
&modinfo_srcversion,
&modinfo_rhelversion,
&modinfo_initstate,
&modinfo_coresize,
&modinfo_initsize,

View File

@ -38,8 +38,15 @@ int mod_verify_sig(const void *mod, struct load_info *info)
modlen -= sig_len + sizeof(ms);
info->len = modlen;
return verify_pkcs7_signature(mod, modlen, mod + modlen, sig_len,
ret = verify_pkcs7_signature(mod, modlen, mod + modlen, sig_len,
VERIFY_USE_SECONDARY_KEYRING,
VERIFYING_MODULE_SIGNATURE,
NULL, NULL);
if (ret == -ENOKEY && IS_ENABLED(CONFIG_INTEGRITY_PLATFORM_KEYRING)) {
ret = verify_pkcs7_signature(mod, modlen, mod + modlen, sig_len,
VERIFY_USE_PLATFORM_KEYRING,
VERIFYING_MODULE_SIGNATURE,
NULL, NULL);
}
return ret;
}

View File

@ -384,6 +384,20 @@ const struct taint_flag taint_flags[TAINT_FLAGS_COUNT] = {
[ TAINT_LIVEPATCH ] = { 'K', ' ', true },
[ TAINT_AUX ] = { 'X', ' ', true },
[ TAINT_RANDSTRUCT ] = { 'T', ' ', true },
[ TAINT_18 ] = { '?', '-', false },
[ TAINT_19 ] = { '?', '-', false },
[ TAINT_20 ] = { '?', '-', false },
[ TAINT_21 ] = { '?', '-', false },
[ TAINT_22 ] = { '?', '-', false },
[ TAINT_23 ] = { '?', '-', false },
[ TAINT_24 ] = { '?', '-', false },
[ TAINT_25 ] = { '?', '-', false },
[ TAINT_26 ] = { '?', '-', false },
[ TAINT_SUPPORT_REMOVED ] = { 'h', ' ', false },
[ TAINT_RESERVED28 ] = { '?', '-', false },
[ TAINT_RESERVED29 ] = { '?', '-', false },
[ TAINT_RESERVED30 ] = { '?', '-', false },
[ TAINT_UNPRIVILEGED_BPF ] = { 'u', ' ', false },
};
/**

109
kernel/rh_taint.c Normal file
View File

@ -0,0 +1,109 @@
#include <linux/kernel.h>
#include <linux/module.h>
/*
* The following functions are used by Red Hat to indicate to users that
* hardware and drivers are unsupported, or have limited support in RHEL major
* and minor releases. These functions output loud warning messages to the end
* user and should be USED WITH CAUTION.
*
* Any use of these functions _MUST_ be documented in the RHEL Release Notes,
* and have approval of management.
*/
/**
* mark_hardware_unsupported() - Mark hardware, class, or type as unsupported.
* @msg: Hardware name, class, or type
*
* Called to mark a device, class of devices, or types of devices as not having
* support in any RHEL minor release. This does not TAINT the kernel. Red Hat
* will not fix bugs against this hardware in this minor release. Red Hat may
* declare support in a future major or minor update release. This cannot be
* used to mark drivers unsupported.
*/
void mark_hardware_unsupported(const char *msg)
{
/* Print one single message */
pr_crit("Warning: %s - this hardware has not undergone testing by Red Hat and might not be certified. Please consult https://catalog.redhat.com for certified hardware.\n", msg);
}
EXPORT_SYMBOL(mark_hardware_unsupported);
/**
* mark_hardware_deprecated() - Mark hardware, class, or type as deprecated.
* @msg: Hardware name, class, or type
*
* Called to minimize the support status of a previously supported device in
* a minor release. This does not TAINT the kernel. Marking hardware
* deprecated is usually done in conjunction with the hardware vendor. Future
* RHEL major releases may not include this driver. Driver updates and fixes
* for this device will be limited to critical issues in future minor releases.
*/
void mark_hardware_deprecated(const char *msg)
{
pr_crit("Warning: %s - this hardware is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes for this device will be limited to critical issues. Please contact Red Hat Support or your device's hardware vendor for additional information.\n", msg);
}
EXPORT_SYMBOL(mark_hardware_deprecated);
/**
* mark_tech_preview() - Mark driver or kernel subsystem as 'Tech Preview'
* @msg: Driver or kernel subsystem name
*
* Called to minimize the support status of a new driver. This does TAINT the
* kernel. Calling this function indicates that the driver or subsystem has
* had limited testing and is not marked for full support within this RHEL
* minor release. The next RHEL minor release may contain full support for
* this driver. Red Hat does not guarantee that bugs reported against this
* driver or subsystem will be resolved.
*/
void mark_tech_preview(const char *msg, struct module *mod)
{
const char *str = NULL;
if (msg)
str = msg;
#ifdef CONFIG_MODULES
else if (mod && mod->name)
str = mod->name;
#endif
pr_warn("TECH PREVIEW: %s may not be fully supported.\n"
"Please review provided documentation for limitations.\n",
(str ? str : "kernel"));
add_taint(TAINT_AUX, LOCKDEP_STILL_OK);
#ifdef CONFIG_MODULES
if (mod)
mod->taints |= (1U << TAINT_AUX);
#endif
}
EXPORT_SYMBOL(mark_tech_preview);
/**
* mark_driver_unsupported - drivers that we know we don't want to support
* @name: the name of the driver
*
* In some cases Red Hat has chosen to build a driver for internal QE
* use. Use this function to mark those drivers as unsupported for
* customers.
*/
void mark_driver_unsupported(const char *name)
{
pr_crit("Warning: %s - This driver has not undergone sufficient testing by Red Hat for this release and therefore cannot be used in production systems.\n",
name ? name : "kernel");
}
EXPORT_SYMBOL(mark_driver_unsupported);
/**
* mark_driver_deprecated() - Mark drivers as deprecated.
* @name: the name of the driver
*
* Called to minimize the support status of a previously supported driver in
* a minor release. This does not TAINT the kernel. Future
* RHEL major releases may not include this driver. Driver updates and fixes
* will be limited to critical issues in future minor releases.
*/
void mark_driver_deprecated(const char *name)
{
pr_crit("Warning: %s - this driver is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes will be limited to critical issues. Please contact Red Hat Support for additional information.\n",
name ? name : "kernel");
}
EXPORT_SYMBOL(mark_driver_deprecated);

View File

@ -243,6 +243,11 @@ static int bpf_unpriv_handler(struct ctl_table *table, int write,
if (write && !ret) {
if (locked_state && unpriv_enable != 1)
return -EPERM;
if (!unpriv_enable) {
pr_warn("Unprivileged BPF has been enabled, "
"tainting the kernel");
add_taint(TAINT_UNPRIVILEGED_BPF, LOCKDEP_STILL_OK);
}
*(int *)table->data = unpriv_enable;
}
return ret;

16
makefile Normal file
View File

@ -0,0 +1,16 @@
ifeq ($(filter dist-% distg-%,$(MAKECMDGOALS)),)
include Makefile
endif
_OUTPUT := "."
# this section is needed in order to make O= to work
ifeq ("$(origin O)", "command line")
_OUTPUT := "$(abspath $(O))"
_EXTRA_ARGS := O=$(_OUTPUT)
endif
dist-%::
$(MAKE) -C redhat $(@) $(_EXTRA_ARGS)
distg-%::
$(MAKE) -C redhat $(@) $(_EXTRA_ARGS)

View File

@ -125,6 +125,12 @@ static void __init cma_activate_area(struct cma *cma)
spin_lock_init(&cma->mem_head_lock);
#endif
#ifdef CONFIG_RHEL_DIFFERENCES
/* s390x and ppc64 has been using CMA already in RHEL 8 as default. */
if (!IS_ENABLED(CONFIG_S390) && !IS_ENABLED(CONFIG_PPC64))
mark_tech_preview("CMA", NULL);
#endif /* CONFIG_RHEL_DIFFERENCES */
return;
not_in_zone:
@ -437,6 +443,10 @@ struct page *cma_alloc(struct cma *cma, unsigned long count,
if (!cma || !cma->count || !cma->bitmap)
goto out;
#ifdef CONFIG_RHEL_DIFFERENCES
pr_info_once("Initial CMA usage detected\n");
#endif /* CONFIG_RHEL_DIFFERENCES */
pr_debug("%s(cma %p, count %lu, align %d)\n", __func__, (void *)cma,
count, align);

8
redhat/.gitignore vendored Normal file
View File

@ -0,0 +1,8 @@
*.bz2
configs/kernel*.config
configs/*-merged
kabi/Module.kabi_*
kabi/kabi-current
kabi/kabi-rhel8*
kabi/kabi-rhel8*/*

560
redhat/Makefile Normal file
View File

@ -0,0 +1,560 @@
GIT ?= git
include Makefile.common
include Makefile.rhpkg
LANG=C
ifeq ("$(ZSTREAM)", "yes")
__YSTREAM = no
ifeq ("$(origin RHDISTGIT_BRANCH)", "command line")
__ZSTREAM = branch
else
__ZSTREAM = yes
endif
BUILDOPTS += +kabidupchk
else
__ZSTREAM = no
ifeq ("$(EARLY_YSTREAM)", "yes")
__YSTREAM = early
else
__YSTREAM = yes
endif
endif
ifeq ("$(NO_CONFIGCHECKS)","1")
PROCESS_CONFIGS_OPTS=
PROCESS_CONFIGS_CHECK_OPTS=
BUILDOPTS += -configchecks
else
PROCESS_CONFIGS_CHECK_OPTS=-n -t -c
PROCESS_CONFIGS_OPTS=-n -w -c
endif
BUILD_TARGET ?= --scratch $(BUILD_SCRATCH_TARGET)
FLAVOR =
RHGITURL?=$(shell $(GIT) config rhg.url || $(GIT) config remote.origin.url)
RHGITCOMMIT?=$(shell $(GIT) log -1 --pretty=format:%H)
# this section is needed in order to make O= to work
_OUTPUT := ..
ifeq ("$(origin O)", "command line")
_OUTPUT := $(O)
_EXTRA_ARGS := O=$(_OUTPUT)
endif
CURARCH := $(shell uname -m)
ARCHCONFIG := $(shell uname -m | sed -e s/x86_64/X86_64/ \
-e s/s390x/S390/ -e s/ppc.*/PPC/ )
KABIDW := $(REDHAT)/kabi-dwarf
include Makefile.cross
default: dist-help
dist-python-check:
@if [ ! -x /usr/bin/python3 ]; then \
echo "ERROR: Python 3 is needed." ; \
exit 1; \
fi
dist-kabi: dist-python-check
@for KABIARCH in $(ARCH_LIST); do \
$(REDHAT)/kabi/show-kabi -k $(REDHAT)/kabi/kabi-module/ -m \
-a $$KABIARCH -r $(RHEL_MAJOR).$(RHEL_MINOR) > $(REDHAT)/kabi/Module.kabi_$$KABIARCH;\
for i in {0..$(RHEL_MINOR)}; do \
mkdir -p $(REDHAT)/kabi/kabi-rhel$(RHEL_MAJOR)$$i/;\
$(REDHAT)/kabi/show-kabi -k $(REDHAT)/kabi/kabi-module/ -s -a $$KABIARCH \
-r $(RHEL_MAJOR).$$i > $(REDHAT)/kabi/kabi-rhel$(RHEL_MAJOR)$$i/kabi_stablelist_$$KABIARCH;\
done;\
done;
@(cd $(REDHAT)/kabi/ && ln -Tsf kabi-rhel$(RHEL_MAJOR)$(RHEL_MINOR) kabi-current)
dist-kabi-dup: dist-python-check
@for KABIARCH in $(ARCH_LIST); do \
touch $(REDHAT)/kabi/Module.kabi_dup_$$KABIARCH;\
if [ -d $(REDHAT)/kabi/kabi-dup-module/kabi_$$KABIARCH ]; then \
$(REDHAT)/kabi/show-kabi -k $(REDHAT)/kabi/kabi-dup-module/ -m \
-a $$KABIARCH -r $(RHEL_MAJOR).$(RHEL_MINOR) > \
$(REDHAT)/kabi/Module.kabi_dup_$$KABIARCH;\
fi \
done;
dist-check-kabi: dist-kabi
@if [ ! -e $(_OUTPUT)/Module.symvers ]; then \
echo "ERROR: You must compile the kernel and modules first";\
exit 1;\
fi
@$(REDHAT)/kabi/check-kabi -k $(REDHAT)/kabi/Module.kabi_$(MACH) \
-s $(_OUTPUT)/Module.symvers
dist-check-kabi-dup: dist-kabi-dup
@if [ ! -e $(_OUTPUT)/Module.symvers ]; then \
echo "ERROR: You must compile the kernel and modules first";\
exit 1;\
fi
@$(REDHAT)/kabi/check-kabi -k $(REDHAT)/kabi/Module.kabi_dup_$(MACH) \
-s $(_OUTPUT)/Module.symvers
dist-kabi-dw-base: dist-kabi
@echo "Generating baseline dataset for KABI DWARF-based comparison..."
@echo "**** GENERATING DWARF-based kABI baseline dataset ****"
@$(KABIDW)/run_kabi-dw.sh generate \
$(REDHAT)/kabi/kabi-current/kabi_stablelist_$(CURARCH) \
$(_OUTPUT) $(KABIDW)/base/$(CURARCH)/
dist-kabi-dw-check: dist-kabi
@if [ ! -d $(KABIDW)/base/$(CURARCH) ]; then \
echo "**** ERROR: ****"; \
echo "Comparison base not found in $(KABIDW)/base/$(CURARCH)."; \
echo "Please run \"make dist-kabi-dw-base\" first!"; \
exit 1; \
fi
@echo "**** GENERATING DWARF-based kABI dataset ****"
@$(KABIDW)/run_kabi-dw.sh generate \
$(REDHAT)/kabi/kabi-current/kabi_stablelist_$(CURARCH) \
$(_OUTPUT) $(KABIDW)/base/$(CURARCH).tmp/
@echo "**** KABI DWARF-based comparison report ****"
@$(KABIDW)/run_kabi-dw.sh compare \
$(KABIDW)/base/$(CURARCH) $(KABIDW)/base/$(CURARCH).tmp || :
@echo "**** End of KABI DWARF-based comparison report ****"
@rm -rf $(KABIDW)/base/$(CURARCH).tmp
dist-configs-commit: dist-configs-prep
@cd $(REDHAT)/configs; VERSION=$(KVERSION) ./generate_all_configs.sh "$(FLAVOR)" 1; \
./process_configs.sh -z $(PACKAGE_NAME) $(KVERSION) "" $(FLAVOR)
dist-configs: dist-configs-prep
@cd $(REDHAT)/configs; VERSION=$(KVERSION) ./generate_all_configs.sh "$(FLAVOR)" 1; \
./process_configs.sh $(PROCESS_CONFIGS_OPTS) $(PACKAGE_NAME) $(KVERSION)
dist-fedora-configs: FLAVOR = fedora
dist-fedora-configs: dist-configs
fedora-configs: dist-fedora-configs
dist-rhel-configs: FLAVOR = rhel
dist-rhel-configs: dist-configs
rh-configs: dist-rhel-configs
dist-configs-check: dist-configs-prep
cd $(REDHAT)/configs; ./process_configs.sh $(PROCESS_CONFIGS_CHECK_OPTS) $(PACKAGE_NAME)
dist-configs-prep: dist-clean-configs dist-buildreq-check
cd $(REDHAT)/configs; ./build_configs.sh "$(PACKAGE_NAME)" "$(ARCH_MACH)" "$(FLAVOR)"
dist-configs-arch: ARCH_MACH = $(MACH)
dist-configs-arch: dist-configs
dist-clean-configs:
cd $(REDHAT)/configs; rm -f kernel-*.config \
kernel-*.config.orig \
kernel-*.config.tmp
dist-clean-sources:
@rm -f $(RPM)/SPECS/*
@for i in $(SOURCES)/*; do \
rm -f $$i; \
done;
dist-clean-rpmdirs:
@for i in $(RPM)/{BUILD,SRPMS,RPMS,SPECS}/*; do \
rm -rf $$i; \
done;
dist-clean-scripts:
@rm -f dist-dump-variables.sh
dist-clean: dist-clean-sources dist-clean-configs dist-clean-rpmdirs dist-clean-scripts
dist-stub-key:
@echo "Copying pre-generated keys";
@echo "*** THIS IS NOT RECOMMENDED ***";
@echo "To be safe, keys should be created once for every build";
@echo "Use this option only for development builds";
@cp keys/stub_key.x509 $(_OUTPUT)/;
@cp keys/stub_key.priv $(_OUTPUT)/;
# force tarball to be regenerated if HEAD changes
.PHONY: $(TARBALL)
$(TARBALL):
@if [ $(SINGLE_TARBALL) -eq 1 ]; then \
scripts/create-tarball.sh $(GITID) $(TARBALL) linux-$(KVERSION)-$(PKGRELEASE); \
else \
scripts/create-tarball.sh $(MARKER) $(TARBALL) linux-$(TARFILE_RELEASE); \
fi
.PHONY: $(KABI_TARBALL)
$(KABI_TARBALL):
@(cd kabi && tar cjf $(SOURCES)/$(KABI_TARFILE) kabi-rhel$(RHEL_MAJOR)* kabi-current)
.PHONY: $(KABIDW_TARBALL)
$(KABIDW_TARBALL):
@if [ ! -d $(KABIDW)/base ]; then \
mkdir -p $(KABIDW)/base; \
fi
@(cd kabi-dwarf && tar cjf $(SOURCES)/$(KABIDW_TARFILE) base run_kabi-dw.sh)
dist-tarball: $(TARBALL)
@echo "redhat/$(TARFILE)"
dist-kernelrelease:
@echo $(PACKAGE_NAME)-$(KVERSION)-$(DISTRO_BUILD)
dist-kernelversion:
@echo $(KVERSION)-$(DISTRO_BUILD)
dist-specfile: setup-source
@echo $(SOURCES)/$(SPECFILE)
dist-git-version-check:
@# genspec.sh uses pathspec magic that wasn't introduced until version 2.13
@IFS=" ."; \
set -- $$($(GIT) --version); \
IFS=; \
if [ "$$3" -lt 2 -o \( "$$3" -eq 2 -a "$$4" -lt 13 \) ]; then \
echo "ERROR: You need git version 2.13 or newer to run some setup commands"; \
exit 1; \
fi
dist-buildreq-check: setup-source
@PKGLIST="rpm-build $(rpmspec -q --buildrequires $(SOURCES)/$(SPECFILE) | cut -d ' ' -f 1)"; \
MISSING=""; \
for pkg in $$PKGLIST; do \
rpm -q --whatprovides $$pkg >/dev/null || MISSING="$$MISSING $$pkg"; \
done; \
if [ -n "$$MISSING" ]; then \
echo "Error: please install $$MISSING"; \
exit 1; \
fi
setup-source: dist-git-version-check dist-clean-sources
@cp $(REDHAT)/$(SPECFILE).template $(SOURCES)/$(SPECFILE)
@if [ ! -e $(REDHAT)/$(CHANGELOG) ]; then \
echo "Creating $(CHANGELOG) as copy of $(CHANGELOG_PREV)"; \
cp $(REDHAT)/$(CHANGELOG_PREV) $(REDHAT)/$(CHANGELOG); \
fi
@cp $(REDHAT)/$(CHANGELOG) $(SOURCES)/$(CHANGELOG)
@$(REDHAT)/genspec.sh $(SOURCES) $(SOURCES)/$(SPECFILE) $(SOURCES)/$(CHANGELOG) $(PKGRELEASE) $(RPMKVERSION) $(RPMKPATCHLEVEL) $(RPMKSUBLEVEL) $(DISTRO_BUILD) $(RELEASED_KERNEL) $(SPECRELEASE) $(__ZSTREAM) "$(BUILDOPTS)" $(MARKER) `cat $(REDHAT)/marker` $(SINGLE_TARBALL) $(TARFILE_RELEASE) $(SNAPSHOT) $(UPSTREAM_BRANCH) $(INCLUDE_FEDORA_FILES) $(INCLUDE_RHEL_FILES) $(BUILDID)
@cp $(SOURCES)/$(SPECFILE) $(SOURCES)/../SPECS/
generate-testpatch-tmp:
@$(GIT) diff --no-renames HEAD ":(exclude,top).get_maintainer.conf" \
":(exclude,top).gitattributes" \
":(exclude,top).gitignore" \
":(exclude,top)makefile" \
":(exclude,top)Makefile.rhelver" \
":(exclude,top)redhat" > $(TESTPATCH).tmp
sources-rh: $(TARBALL) generate-testpatch-tmp setup-source dist-configs-check
@cp -l $(TARBALL) $(SOURCES)/ || cp $(TARBALL) $(SOURCES)/
@touch $(TESTPATCH)
@diff $(TESTPATCH).tmp $(TESTPATCH) > /dev/null || \
echo "WARNING: There are uncommitted changes in your tree or the changes are not in sync with linux-kernel-test.patch. Either commit the changes or run 'make dist-test-patch'"
@rm $(TESTPATCH).tmp
@cp $(TESTPATCH) $(SOURCES)/linux-kernel-test.patch
@cat configs/flavors | while read flavor; do echo "Copying sources for $${flavor}"; [ -e $${flavor}_files ] && cp $${flavor}_files/* $(SOURCES); done
@cp cpupower.* \
keys/rhel*.x509 \
kabi/check-kabi \
configs/$(PACKAGE_NAME)-*.config \
gating.yaml \
rpminspect.yaml \
update_scripts.sh \
kvm_stat.logrotate \
mod-denylist.sh \
mod-internal.list \
mod-sign.sh \
configs/flavors \
configs/generate_all_configs.sh \
configs/merge.pl \
configs/process_configs.sh \
parallel_xz.sh \
generate_crashkernel_default.sh \
../Makefile.rhelver \
README.rst \
kernel-local \
$(SOURCES)/
@if [ "$(RELEASED_KERNEL)" -ne 0 ]; then \
cp keys/redhatsecureboot{301,501,ca5,ca1}.cer $(SOURCES)/; \
cp keys/secureboot_{ppc,s390}.cer $(SOURCES)/; \
else \
cp keys/redhatsecureboot{003,401,ca2,ca4}.cer $(SOURCES)/; \
fi
@for KABIARCH in $(ARCH_LIST); do \
cp kabi/Module.kabi_$$KABIARCH $(SOURCES)/; \
cp kabi/Module.kabi_dup_$$KABIARCH $(SOURCES)/; \
done
@(cd kabi && tar cjf $(SOURCES)/$(KABI_TARFILE) kabi-rhel$(RHEL_MAJOR)* kabi-current)
@if [ ! -d $(KABIDW)/base ]; then \
mkdir -p $(KABIDW)/base; \
fi
@(cd kabi-dwarf && tar cjf $(SOURCES)/$(KABIDW_TARFILE) base run_kabi-dw.sh)
dist-sources: dist-kabi dist-kabi-dup sources-rh
dist-test-patch: generate-testpatch-tmp
@mv $(TESTPATCH).tmp $(TESTPATCH);
do-rpmbuild: dist-sources
$(RPMBUILD) --define "_sourcedir $(SOURCES)" --define "_builddir $(RPM)/BUILD" --define "_srcrpmdir $(RPM)/SRPMS" --define "_rpmdir $(RPM)/RPMS" --define "_specdir $(RPM)/SPECS" --define "dist $(DIST)" $(RPMBUILDOPTS) $(RPM)/SOURCES/$(PACKAGE_NAME).spec
dist-all-rpms: RPMBUILDOPTS=--target $(MACH) -ba
dist-all-rpms: dist-sources do-rpmbuild
dist-srpm: RPMBUILDOPTS=--nodeps -bs
dist-srpm: dist-sources do-rpmbuild
dist-srpm-gcov: BUILDID=".gcov"
dist-srpm-gcov: BUILDOPTS="+gcov"
dist-srpm-gcov: dist-srpm
dist-rpms: RPMBUILDOPTS=--target $(MACH) -bb
dist-rpms: dist-sources do-rpmbuild
dist-kernel-%: dist-sources
RPMBUILDOPTS="--target $(MACH) --with $* -bb" make do-rpmbuild
dist-prep: RPMBUILDOPTS=--nodeps --target noarch -bp
dist-prep: dist-sources do-rpmbuild
dist-perf: RPMBUILDOPTS=--without up --without smp --without zfcpdump --without debug --without doc --without headers --without --without doc --without debuginfo --target $(MACH) -bb
dist-perf: dist-sources do-rpmbuild
dist-rpm-baseonly: RPMBUILDOPTS=--target $(MACH) --without debug --without debuginfo --without vdso_install --without bpftool --without perf --without tools -bb
dist-rpm-baseonly: dist-sources do-rpmbuild
# unless you know what you're doing, you don't want to use the next four ones
dist-release-finish: setup-source
@cp $(SOURCES)/$(CHANGELOG) $(REDHAT)/$(CHANGELOG)
@$(GIT) add $(REDHAT)/$(CHANGELOG)
@$(GIT) add $(REDHAT)/marker
@$(GIT) commit -s ../Makefile.rhelver $(REDHAT)/marker $(REDHAT)/$(CHANGELOG) $(PACKAGE_NAME).spec.template -m "[redhat] $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PREBUILD)$(BUILD)$(BUILDID)"
dist-release-changed: setup-source
@cp $(SOURCES)/$(CHANGELOG) $(REDHAT)/$(CHANGELOG)
@echo $(MARKER) > $(REDHAT)/marker
@# if neither changelog nor marker was updated, skip bumping a release
@$(GIT) update-index -q --really-refresh
@if $(GIT) diff-index --quiet HEAD; then \
echo "Nothing changed, skipping updates"; \
else \
$(GIT) checkout -- $(REDHAT)/$(CHANGELOG); \
$(REDHAT)/scripts/new_release.sh $(REDHAT) $(__YSTREAM) $(__ZSTREAM) $(BUMP_RELEASE); \
$(MAKE) dist-release-finish; \
fi
dist-release: dist-clean-sources
@$(MAKE) dist-release-changed
dist-release-tag:
@$(GIT) tag -a -m "$(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE)" $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE)
git-tree-check:
@if test -n "$(DIST_PUSH)" && test -z "$(shell $(GIT) remote get-url gitlab 2>/dev/null)"; then \
echo -e "Please run 'git remote add gitlab <url>' to enable git-push.\n"; \
exit 1; \
fi
@$(GIT) diff-index --quiet HEAD || \
{ echo -e "Dirty tree, please clean before merging.\n"; exit 1; }
DIST_BRANCH ?= "os-build"
dist-merge-upstream: git-tree-check
@if test "$(shell $(GIT) branch --show-current)" != "$(DIST_BRANCH)"; then \
echo -e "Please checkout $(DIST_BRANCH) branch before merging.\n"; \
exit 1; \
fi;
@# If TAG is empty, script defaults to master:HEAD
@$(GIT) checkout $(DIST_BRANCH)
@cd ..; $(REDHAT)/scripts/ci/ark-update-configs.sh $(TAG)
dist-merge-upstream-push: export DIST_PUSH="1"
dist-merge-upstream-push: dist-merge-upstream
dist-fedora-release: git-tree-check
@# If TAG is empty, script defaults to master:HEAD
@cd ..; $(REDHAT)/scripts/ci/ark-create-release.sh $(TAG) || \
(echo "Unable to create release tag"; exit 1)
dist-fedora-release-push: export DIST_PUSH="1"
dist-fedora-release-push: dist-fedora-release
.PHONY: dist-brew dist-koji
dist-brew : BUILD_FLAGS ?= $(BREW_FLAGS) $(TEST_FLAGS)
dist-koji : BUILD_FLAGS ?= $(KOJI_FLAGS) $(TEST_FLAGS)
distg-brew: BUILD_FLAGS ?= $(BREW_FLAGS) $(TEST_FLAGS)
distg-koji: BUILD_FLAGS ?= $(KOJI_FLAGS) $(TEST_FLAGS)
dist-brew dist-koji: dist-%: dist-srpm
$* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) $(SRPMS)/$(PACKAGE_NAME)-$(KVERSION)-$(PKGRELEASE)$(DIST).src.rpm $(OUTPUT_FILE)
distg-brew distg-koji: distg-%:
$* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) "$(RHGITURL)?redhat/koji#$(RHGITCOMMIT)"
.PHONY: $(REDHAT)/rpm/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/rpm/SOURCES/$(PACKAGE_NAME).spec:
@echo "dist-sources"
@$(MAKE) dist-sources
dist-git-test: export RH_DIST_GIT_TEST="1"
dist-git-test: dist-git
dist-git: dist-srpm $(KABI_TARBALL) $(KABIDW_TARBALL)
ifeq ("$(RHDISTGIT_BRANCH)", "")
$(error RHDISTGIT_BRANCH unset)
endif
@if [ "$(DISTRO)" == "centos" ]; then \
if [ -z "$(GL_DISTGIT_USER)" ]; then \
echo "Error: please provide your gitlab username with GL_DISTGIT_USER"; \
exit 1; \
fi; \
fi
$(REDHAT)/scripts/rh-dist-git.sh "$(RHDISTGIT_BRANCH)" "$(RHDISTGIT_CACHE)" "$(RHDISTGIT_TMP)" "$(RHDISTGIT)" "$(TARBALL)" "$(KABI_TARBALL)" "$(KABIDW_TARBALL)" "$(__ZSTREAM)" "$(PACKAGE_NAME)" "$(RHEL_MAJOR)" "$(RHPKG_BIN)" "$(SRPMS)/$(PACKAGE_NAME)-$(KVERSION)-$(PKGRELEASE)$(DIST).src.rpm"
dist-rtg: dist-release
@$(MAKE) dist-release-tag
@$(MAKE) dist-git
# RH_LATEST returns the value of the latest "known good" kernel from brew.
# This should not be confused with the latest top-of-tree development tag.
dist-get-latest:
$(eval RH_LATEST:=$(shell brew latest-pkg --quiet rhel-${RHEL_MAJOR}.${RHEL_MINOR}.0-candidate kernel | awk ' { print $$1 } '))
@echo "The latest kernel package tag is ${RH_LATEST}."
dist-os-version:
@echo "OSVERSION: $(RHEL_MAJOR).$(RHEL_MINOR)"
.EXPORT_ALL_VARIABLES:
.PHONY: dist-dump-variables
dist-dump-variables:
grep -h "^[ ]*[a-zA-Z_][a-zA-Z_0-9]*[ ]*[:?]*=" $(REDHAT)/Makefile.common $(REDHAT)/Makefile $(TOPDIR)/Makefile.rhelver | sed -e 's/[ ]*\([a-zA-Z_][a-zA-Z_0-9]*\).*/echo "\1=$$\1"/' | sort | uniq > dist-dump-variables.sh
chmod +x $(REDHAT)/dist-dump-variables.sh
@$(REDHAT)/dist-dump-variables.sh
dist-self-test:
@if test -x /usr/bin/bats; then \
bats $(REDHAT)/self-test/*.bats ; \
else \
echo "dist-self-test: The bats package is not installed" ; \
fi
dist-help:
@echo 'Cleaning targets:'
@echo ' dist-clean - Clean redhat/configs/ and redhat/rpm/ directories.'
@echo ''
@echo 'Building targets:'
@echo ' dist-srpm - Create a source RPM.'
@echo ' dist-all-rpms - Create a source RPM and build binary RPMs locally.'
@echo ' dist-brew - Create a source RPM and call brew to build binary RPMs.'
@echo ' distg-brew - Build RPMs using a remote git repo.'
@echo ' [Configuration needed.]'
@echo ' dist-cross-all-rpms - Build RPMs for all supported archs using a cross'
@echo ' compiler.'
@echo ''
@echo 'Configuration targets:'
@echo ' dist-configs - Create RHEL config files in redhat/config/.'
@echo ''
@echo 'For detailed description and full list of targets, run `make dist-full-help`.'
@echo ''
dist-full-help:
@echo 'Cleaning targets:'
@echo ' dist-clean - Do dist-clean-sources, dist-clean-configs, &'
@echo ' dist-clean-rpmdirs.'
@echo ' dist-clean-sources - Clean the redhat/rpm/SOURCES/ directory.'
@echo ' dist-clean-configs - Clean the redhat/configs/ directory.'
@echo ' dist-clean-rpmdirs - Clean the redhat/rpm/{BUILD,SRPMS,RPMS,SPECS}/'
@echo ' directories.'
@echo ''
@echo 'Building targets:'
@echo ' All RPM/SRPM files will be put under the redhat/rpm/ directory.'
@echo ''
@echo ' dist-srpm - Create a source RPM and put it into the redhat/rpm/SRPMS/'
@echo ' directory. See the dist-brew target for available options.'
@echo ' dist-srpm-gcov - Create a source RPM with gcov enabled and put it into the'
@echo ' redhat/rpm/SRPMS/ directory.'
@echo ' dist-brew - Create a kernel SRPM and then call brew to build the'
@echo ' created SRPM. Add BUILDOPTS="+<opt> -<opt> [...]" to'
@echo ' enable/disable build options.'
@echo ' Available <opt>s and their default values:' \
$$(sed -n -e 's/^%define with_\([^ \t]*\).*\?_without_.*/+\1/p' \
-e 's/^%define with_\([^ \t]*\).*\?_with_.*/-\1/p' kernel.spec.template | \
grep -v 'only$$') | fmt -80
@echo ' dist-koji - Create a kernel SRPM and then call koji to build the'
@echo ' created SRPM. See the dist-brew target for available'
@echo ' options.'
@echo ' distg-brew - Pass HEAD of the current git branch to brew to build an'
@echo ' RPM set. Do not forget to push to the remote repository'
@echo ' first. Preceed make command by RHGITCOMMIT=<commitID>'
@echo ' specify commit ID to use.'
@echo ' To set the remote repo, invoke:'
@echo ' git config rhg.url git://<repo_path>'
@echo ' distg-koji - Pass HEAD of the current git branch to koji to build an'
@echo ' RPM set. Do not forget to push to the remote repository'
@echo ' first. See the distg-brew target for options and'
@echo ' configuration.'
@echo ' dist-rpms - Create the binary RPMS for the kernel.'
@echo ' See the dist-brew target for available options.'
@echo ' dist-rpm-baseonly - Create the binary RPMS for the kernel and modules'
@echo ' (no userspace tools or debuginfo).'
@echo ' dist-kernel-<type> - Create binary RPMS for a particular kernel type.'
@echo ' Available <type>s:'\
$$(sed -n 's/^%define with_\([^ ]*only\).*/\1/p' kernel.spec.template)
@echo ' dist-all-rpms - Create the binary RPMS and the SRPM for the kernel.'
@echo ' See the dist-brew target for available options.'
@echo ' dist-prep - Setup the redhat/rpm/BUILD/ directory with the kernel'
@echo ' source. See the dist-brew target for available options.'
@echo ' dist-test-patch - Create a diff against HEAD and put it in'
@echo ' linux-kernel-test.patch. This patch will'
@echo ' be added to the kernel build.'
@echo ' dist-stub-key - Use pre generated keys to speed local test builds.'
@echo ' dist-cross-download - [x86_64 only] download cross compiler rpms.'
@echo ' dist-cross-all-builds - [x86_64 only] execute "rpmbuild -bc" for all'
@echo ' supported archs using RHEL cross compiler.'
@echo ' dist-cross-<arch>-build - [x86_64 only] execute "rpmbuild -bc" for specified'
@echo ' <arch> using RHEL cross compiler.'
@echo ' Supported <arch>s: x86_64'\
$$(sed -n 's/.*--target \([^ ]*\).*/\1/p' Makefile.cross | sort -u)
@echo ' dist-cross-all-rpms - [x86_64 only] execute rpm builds for all supported'
@echo ' archs using RHEL cross compiler.'
@echo ' dist-cross-<arch>-rpms - [x86_64 only] execute rpm builds for specified'
@echo ' <arch> using RHEL cross compiler.'
@echo ' See dist-cross-<arch>-build for the supported archs.'
@echo ' dist-rhel-configs - build ELN configs'
@echo ' dist-fedora-configs - build Fedora configs'
@echo ''
@echo 'kABI targets:'
@echo ' dist-kabi - Create kABI stablelist files in redhat/kabi/kabi-rhel*/'
@echo ' and merge kABI checksums into redhat/kabi/Module.kabi_*.'
@echo ' dist-kabi-dup - Merge kABI checksums for Driver Update Program (DUP)'
@echo ' into redhat/kabi/Module.kabi_dup_*.'
@echo ' dist-check-kabi - Check for changes in kABI stablelisted symbols.'
@echo ' Requires a pre-compiled tree: run `make dist-configs`,'
@echo ' copy the relevant config file from redhat/configs/ to'
@echo ' .config, and run `make`.'
@echo ' dist-check-kabi-dup - Like dist-check-kabi but uses a DUP kABI stablelist.'
@echo ' dist-kabi-dw-base - Generate the base dataset for kABI DWARF-based check.'
@echo ' dist-kabi-dw-check - Run DWARF-based kABI comparison of current binaries'
@echo ' with the base dataset.'
@echo ''
@echo 'Configuration targets:'
@echo ' dist-configs - Creates config files for RHEL $(RHEL_MAJOR) architectures,'
@echo ' cleans them by running make nonint_oldconfig, and copies'
@echo ' them to redhat/configs/ directory. This is the target to use'
@echo ' for a config! Copy the config file you want from the'
@echo ' redhat/configs/ directory to .config'
@echo ' dist-configs-arch - Same as dist-configs but for single architecture only.'
@echo ''
@echo 'Misc targets:'
@echo ' dist-buildreq-check - Checks for presence of packages required for build'
@echo ' dist-get-latest - Returns the latest "known good" kernel from brew. This'
@echo ' should not be confused with the latest top-of-tree'
@echo ' development tag.'
@echo ' dist-os-version - Displays the current Red Hat Enterprise Linux versioni'
@echo ' target used by the current branch/tree.'
@echo ' dist-self-test - Runs self-tests from the redhat/self-test directory'
@echo ''

166
redhat/Makefile.common Normal file
View File

@ -0,0 +1,166 @@
TOPDIR:=$(shell $(GIT) rev-parse --show-toplevel)
REDHAT:=$(TOPDIR)/redhat
include $(TOPDIR)/Makefile.rhelver
include $(REDHAT)/Makefile.variables
RPMBUILD := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \
else echo rpm; fi)
MACH := $(shell uname -m)
HEAD ?= HEAD
RPMKVERSION:=$(shell $(GIT) show $(HEAD):Makefile | sed -ne '/^VERSION\ =\ /{s///;p;q}')
RPMKPATCHLEVEL:=$(shell $(GIT) show $(HEAD):Makefile | sed -ne '/^PATCHLEVEL\ =\ /{s///;p;q}')
RPMKSUBLEVEL:=$(shell $(GIT) show $(HEAD):Makefile | sed -ne '/^SUBLEVEL\ =\ /{s///;p;q}')
RPMKEXTRAVERSION:=$(shell $(GIT) show $(HEAD):Makefile | sed -ne '/^EXTRAVERSION\ =\ /{s///;p;q}')
GITID:= $(shell $(GIT) log --max-count=1 --pretty=format:%H $(HEAD))
# marker is git tag which we base off of for exporting patches
# Make sure marker uses RPMKPATCHLEVEL and RPMKEXTRAVERSION from the kernel
# makefile as opposed to any adjusted version for snapshotting.
ifneq ($(RPMKEXTRAVERSION),)
MARKER:=v$(RPMKVERSION).$(RPMKPATCHLEVEL)$(RPMKEXTRAVERSION)
KEXTRAVERSION:=$(shell echo $(RPMKEXTRAVERSION) | sed -e s/-/./)
PREBUILD:=0$(KEXTRAVERSION).
UPSTREAM_TARBALL_NAME:=$(RPMKVERSION).$(RPMKPATCHLEVEL)$(RPMKEXTRAVERSION)
else
ifeq ($(RPMKSUBLEVEL),0)
MARKER:=v$(RPMKVERSION).$(RPMKPATCHLEVEL)
UPSTREAM_TARBALL_NAME:=$(RPMKVERSION).$(RPMKPATCHLEVEL)
else
MARKER:=v$(RPMKVERSION).$(RPMKPATCHLEVEL).$(RPMKSUBLEVEL)
UPSTREAM_TARBALL_NAME:=$(RPMKVERSION).$(RPMKPATCHLEVEL).$(RPMKSUBLEVEL)
endif
PREBUILD:=
endif
ifneq ($(findstring .fc,$(DIST)),)
DISTRO ?= fedora
else
DISTRO ?= rhel
endif
# If VERSION_ON_UPSTREAM is set, the versioning of the rpm package is based
# on a branch tracking upstream. This allows for generating rpms
# based on untagged releases.
ifndef VERSION_ON_UPSTREAM
ifeq ("$(DIST)", ".elrdy")
VERSION_ON_UPSTREAM:=1
else ifeq ("$(DISTRO)", "fedora")
VERSION_ON_UPSTREAM:=1
else
VERSION_ON_UPSTREAM:=0
endif
endif
ifeq ($(VERSION_ON_UPSTREAM),1)
# UPSTREAM_BRANCH is expected to track mainline.
UPSTREAM:=$(shell $(GIT) rev-parse -q --verify origin/$(UPSTREAM_BRANCH) || \
$(GIT) rev-parse -q --verify $(UPSTREAM_BRANCH))
ifeq ($(UPSTREAM),)
$(error "Missing an $(UPSTREAM_BRANCH) branch")
endif
MERGE_BASE:=$(shell $(GIT) merge-base $(HEAD) $(UPSTREAM))
_TAG:=$(shell $(GIT) describe $(MERGE_BASE))
# a snapshot off of a tagged git is of the form [tag]-[cnt]-g[hash]
SNAPSHOT:=$(shell echo $(_TAG) | grep -c '\-g')
else
SNAPSHOT:=0
endif
ifeq ($(SNAPSHOT),1)
# The base for generating tags is the snapshot commit
MARKER:=$(shell echo $(_TAG) | awk -F "-g" '{ print $$2 }')
# The merge window is weird because the actual versioning hasn't
# been updated but we still need something that works for
# packaging. Fix this by bumping the patch level and marking
# this as rc0
ifeq ($(RPMKEXTRAVERSION),)
KEXTRAVERSION:=.rc0
PREBUILD:=0$(KEXTRAVERSION).
RPMKPATCHLEVEL:=$(shell expr $(RPMKPATCHLEVEL) + 1)
endif
# Obtain the date that HEAD was committed (not the snapshot commit).
HEAD_DATE:=$(shell $(GIT) show -s --format=%cd --date=format:%Y%m%d $(HEAD))
PREBUILD:=$(PREBUILD)$(HEAD_DATE)git$(MARKER).
UPSTREAM_TARBALL_NAME:=$(patsubst v%,%,$(_TAG))
endif
# RPMKPATCHVERSION may get adjusted if we're snapshotting
# during the merge window so ensure this gets set after
# we've checked for snapshots
KVERSION:=$(RPMKVERSION).$(RPMKPATCHLEVEL).$(RPMKSUBLEVEL)
RPMVERSION:=$(KVERSION)
BUILD:=$(RHEL_RELEASE)
PACKAGE_NAME:=kernel
SPECFILE:=$(PACKAGE_NAME).spec
RPM:=$(REDHAT)/rpm
SRPMS:=$(RPM)/SRPMS
SOURCES:=$(RPM)/SOURCES
TESTPATCH:=$(REDHAT)/linux-kernel-test.patch
ARCH_LIST=aarch64 ppc64le s390x x86_64 riscv64
# Make can't match on a regex to match fc31, fc32 so add another check here
# A unified tarball means that the tarball in the srpm contains both the
# upstream sources and redhat patches. A non-unified tarball means that
# the tarball is only upstream sources and the patches get applied as
# a diff in the spec file
ifeq ("$(DIST)", ".elrdy")
SINGLE_TARBALL:=0
else ifeq ("$(DISTRO)", "fedora")
SINGLE_TARBALL:=0
else
SINGLE_TARBALL:=1
endif
STAMP_VERSION:=$(KVERSION)
LOCVERFILE:=../localversion
# create an empty localversion file if you don't want a local buildid
ifneq ($(wildcard $(LOCVERFILE)),)
BUILDID:=$(shell cat $(LOCVERFILE))
$(info BUILDID is "$(BUILDID)". Update '$(shell dirname $(REDHAT))/localversion' to change.)
else
ifeq ($(BUILDID),)
BUILDID:=.test
endif
$(info BUILDID is "$(BUILDID)".)
endif
PKGRELEASE:=$(PREBUILD)$(BUILD)$(BUILDID)
SPECRELEASE:=$(PREBUILD)$(BUILD)%{?buildid}%{?dist}
ifeq ("$(SINGLE_TARBALL)", "0")
TARFILE_RELEASE:=$(UPSTREAM_TARBALL_NAME)
else
TARFILE_RELEASE:=$(KVERSION)-$(PKGRELEASE)
endif
TARFILE:=linux-$(TARFILE_RELEASE).tar.xz
TARBALL:=$(REDHAT)/$(TARFILE)
DISTRO_BUILD:=$(PREBUILD)$(shell echo $(BUILD) | sed -e 's|\(^[0-9]\{1,4\}\)\..*|\1|')
KABI_TARFILE:=kernel-abi-stablelists-$(KVERSION)-$(DISTRO_BUILD).tar.bz2
KABI_TARBALL:=$(REDHAT)/rpm/SOURCES/$(KABI_TARFILE)
KABIDW_TARFILE:=kernel-kabi-dw-$(KVERSION)-$(DISTRO_BUILD).tar.bz2
KABIDW_TARBALL:=$(REDHAT)/rpm/SOURCES/$(KABIDW_TARFILE)
CHANGELOG:=$(PACKAGE_NAME).changelog-$(RHEL_MAJOR).$(RHEL_MINOR)
CHANGELOG_PREV:=$(PACKAGE_NAME).changelog-$(RHEL_MAJOR).$(shell expr $(RHEL_MINOR) - 1)
ifeq ("$(DIST)", ".elrdy")
RHPRODUCT:=rhel-ready
else ifeq ("$(DISTRO)", "fedora")
RHPRODUCT:=rawhide
else ifeq ("$(DISTRO)", "centos")
RHPRODUCT:=c$(RHEL_MAJOR)s
else
RHPRODUCT:=rhel-$(RHEL_MAJOR).$(RHEL_MINOR).0
endif
ifeq ("$(DIST)", ".elrdy")
BUILD_SCRATCH_TARGET ?= temp-ark-rhel-8-test
else ifeq ("$(DISTRO)", "fedora")
BUILD_SCRATCH_TARGET ?= temp-ark-rhel-8-test
else ifeq ("$(DISTRO)", "centos")
BUILD_PROFILE ?= -p stream
BUILD_SCRATCH_TARGET ?= c$(RHEL_MAJOR)s-candidate
else
BUILD_SCRATCH_TARGET ?= rhel-$(RHEL_MAJOR).$(RHEL_MINOR).0-test-pesign
endif

86
redhat/Makefile.cross Normal file
View File

@ -0,0 +1,86 @@
CROSS_RPMFLAGS = $(RPMBUILD) --define "_sourcedir $(SOURCES)" --define "_builddir $(RPM)/BUILD" --define "_srcrpmdir $(RPM)/SRPMS" --define "_rpmdir $(RPM)/RPMS" --define "_specdir $(RPM)/SPECS" --define "dist $(DIST)"
CROSS_PACKAGE_LIST = \
cross-binutils-common cross-gcc-common diffstat \
glibc-static ncurses-devel numactl-devel rng-tools
ifeq ($(ARCH),arm64)
CROSS_PACKAGE_LIST += binutils-aarch64-linux-gnu gcc-aarch64-linux-gnu
else ifeq ($(ARCH),powerpc)
CROSS_PACKAGE_LIST += binutils-powerpc64-linux-gnu gcc-powerpc64-linux-gnu
else ifeq ($(ARCH),s390)
CROSS_PACKAGE_LIST += binutils-s390x-linux-gnu gcc-s390x-linux-gnu
else ifeq ($(ARCH),riscv64)
CROSS_PACKAGE_LIST += binutils-riscv64-linux-gnu gcc-riscv64-linux-gnu
else
CROSS_PACKAGE_LIST += binutils-aarch64-linux-gnu gcc-aarch64-linux-gnu
CROSS_PACKAGE_LIST += binutils-powerpc64-linux-gnu gcc-powerpc64-linux-gnu
CROSS_PACKAGE_LIST += binutils-s390x-linux-gnu gcc-s390x-linux-gnu
CROSS_PACKAGE_LIST += binutils-riscv64-linux-gnu gcc-riscv64-linux-gnu
endif
dist-cross-download:
@if [ "$(ARCHCONFIG)" != "X86_64" ]; then \
echo "$(ARCHCONFIG) ERROR: cross compile only enabled for x86_64"; \
exit 1; \
fi;
@ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) \
$(REDHAT)/scripts/download_cross.sh $(CROSS_PACKAGE_LIST)
dist-cross-aarch64-rpms: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target aarch64 --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "aarch64"
dist-cross-ppc64-rpms: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target ppc64 --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "ppc64"
dist-cross-s390x-rpms: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target s390x --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "s390x"
dist-cross-riscv64-rpms: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target riscv64 --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "riscv64"
dist-cross-all-rpms: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target aarch64 --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) --target ppc64 --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) --target s390x --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) --target riscv64 --with cross -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "aarch64 ppc64 s390x x86_64 riscv64"
dist-cross-aarch64-build: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target aarch64 --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "aarch64"
dist-cross-ppc64-build: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target ppc64 --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "ppc64"
dist-cross-s390x-build: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target s390x --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "s390x"
dist-cross-riscv64-build: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target riscv64 --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "riscv64"
dist-cross-all-builds: dist-cross-download dist-sources
$(REDHAT)/scripts/x86_rngd.sh
$(CROSS_RPMFLAGS) --target aarch64 --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) --target ppc64 --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) --target s390x --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) --target riscv64 --with cross --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(CROSS_RPMFLAGS) --without debuginfo -bc $(RPM)/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/scripts/generate-cross-report.sh "aarch64 ppc64 s390x x86_64 riscv64"

41
redhat/Makefile.rhpkg Normal file
View File

@ -0,0 +1,41 @@
# variables that can be overrided by ~/.rhpkg.mk or $(TOPDIR)/.rhpkg.mk
#
# Command to invoke rhpkg
ifeq ("$(DISTRO)", "fedora")
RHPKG_BIN:=fedpkg
else ifeq ("$(DISTRO)", "centos")
RHPKG_BIN:=centpkg
else
RHPKG_BIN:=rhpkg
endif
# Kerberos username for pkgs.devel.redhat.com
RHDISTGIT_USER:="$(shell whoami)"
# Local dist-git _clean_ clone. To be used when updating dist-git
#RHDISTGIT_CACHE:=
# Temporary directory to clone the dist-git repo to. Change this if you
# have a faster storage
RHDISTGIT_TMP:=/tmp
# Branch it should be switched into
RHDISTGIT_BRANCH:=${RHPRODUCT}
# load configuration, starting with home directory then local
ifeq ("$(RHDISTGIT_CACHE)", "")
ifneq ("$(wildcard ${HOME}/.rhpkg.mk)", "")
include ${HOME}/.rhpkg.mk
endif
ifneq ("$(wildcard $(TOPDIR)/.rhpkg.mk)", "")
include $(TOPDIR)/.rhpkg.mk
endif
endif
ifneq ("$(DISTRO)", "centos")
RHDISTGIT:="ssh://$(RHDISTGIT_USER)@pkgs.devel.redhat.com/rpms/$(PACKAGE_NAME)"
else
# CentOS uses a fork + merge request based workflow with dist-git to
# handle changes, so you need to provide the gitlab username and we by
# default set the default user's fork path. The dist-git target in
# redhat/Makefile has a check to see if the variable is not set.
GL_FORK_PATH?=$(PACKAGE_NAME).git
RHDISTGIT:=git@gitlab.com:$(GL_DISTGIT_USER)/$(GL_FORK_PATH)
endif

47
redhat/Makefile.variables Normal file
View File

@ -0,0 +1,47 @@
# Variables below should be changed as needed for building on a different
# branch, or with a different upstream branch. This should be the only
# file that needs to be changed now, and is included in redhat/Makefile
# and redhat/Makefile.common
# This is the source branch that you are building out of typically this is
# the current branch.
DIST_BRANCH ?= "os-build"
# This is the dist release suffix used in the package release, eg. .fc34,
# .el8 etc. In a different branch this may be set to a fixed value.
DIST ?= $(shell $(RPMBUILD) --eval '%{?dist}')
# The branch used as upstream. This is what the upstream tarball is it
# should be tracked in a local branch. This would be "master" for the
# Linus master branch or linux-5.x.y for a stable branch. It can also be
# any other upstream you have added as a branch locally.
UPSTREAM_BRANCH ?= master
# If VERSION_ON_UPSTREAM is set, the versioning of the rpm package is based
# on a branch tracking upstream. This allows for generating rpms
# based on untagged releases.
VERSION_ON_UPSTREAM:=1
# RELEASED_KERNEL swaps between the pre-release secureboot keys and
# the release one, for vmlinux signing. It also controls whether Fedora
# kernels are built as debug kernels or release kernels with a separate
# kernel-debug build.
# Set RELEASED_KERNEL to 1 when the upstream source tarball contains a
# kernel release. (This includes prepatch or "rc" releases.)
# Set RELEASED_KERNEL to 0 when the upstream source tarball contains an
# unreleased kernel development snapshot.
RELEASED_KERNEL:=0
# BUMP_RELEASE determines whether the pkgrelease is bumped when you call
# 'make dist-release'. It should be set to "yes" if you expect to do
# multiple updates and builds without bumping the base version, and no
# when you expect every build to use a different base kernel version.
BUMP_RELEASE:=yes
# INCLUDE_*_FILES determines whether or not the specific OS flavor files will
# be included as part of the source RPM. Downstream projects, such as
# centos-stream or RHEL, can disable file inclusion by setting these values
# to '0'.
INCLUDE_FEDORA_FILES:=1
INCLUDE_RHEL_FILES:=1

25
redhat/README.rst Normal file
View File

@ -0,0 +1,25 @@
===================
The Kernel dist-git
===================
The kernel is maintained in a `source tree`_ rather than directly in dist-git.
The specfile is maintained as a `template`_ in the source tree along with a set
of build scripts to generate configurations, (S)RPMs, and to populate the
dist-git repository.
The `documentation`_ for the source tree covers how to contribute and maintain
the tree.
If you're looking for the downstream patch set it's available in the source
tree with "git log master..ark-patches" or
`online`_.
Each release in dist-git is tagged in the source repository so you can easily
check out the source tree for a build. The tags are in the format
name-version-release, but note release doesn't contain the dist tag since the
source can be built in different build roots (Fedora, CentOS, etc.)
.. _source tree: https://gitlab.com/cki-project/kernel-ark.git
.. _template: https://gitlab.com/cki-project/kernel-ark/-/blob/os-build/redhat/kernel.spec.template
.. _documentation: https://gitlab.com/cki-project/kernel-ark/-/wikis/home
.. _online: https://gitlab.com/cki-project/kernel-ark/-/commits/ark-patches

14
redhat/commit_template Normal file
View File

@ -0,0 +1,14 @@
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.

5
redhat/configs/.gitignore vendored Normal file
View File

@ -0,0 +1,5 @@
*merged
config-*
kernel*config
*.old
*.tmp

63
redhat/configs/README Normal file
View File

@ -0,0 +1,63 @@
Red Hat Enterprise Linux Always Ready config option scheme
------------------------------------------------------
Historically, the RHEL kernel is forked from a Fedora kernel.
Today, the Always Ready Kernel (ARK) is constantly rebased as new kernel
releases come out. New configuration options are reviewed and set
with each release.
The config options are split out into a hierarchical
tree structure, with one file per config option at each level of the
hierarchy. The config options are merged and properly layered according to
the file "priority" in the same directory as this README to generate the
final kernel-$VERSION-<arch>-<variant>.config files we need for building the
actual kernels.
The configuration is broken down into several directories:
ark - This contains all configuration options that have been fully
reviewed by kernel developers and are suitable for inclusion at branch time.
pending-common - This directory contains all configuration options that have
not yet been fully reviewed for inclusion. Because of the rate at which
kernel options come out, we can't guarantee everything has been reviewed
by the time a build needs to happen. In the interest of letting the build
proceed for other testing, configuration options are staged in the
pending directory. It is expected that this directory will be empty
at branch time.
In each directory (ark etc.), we have generic/CONFIG_* and debug/CONFIG_*, then
generic/<arch>/CONFIG_* and generic/<arch>/<variant>/CONFIG_*, as well as
debug/<arch>/CONFIG_*. While this may seem overly complex compared with
past RHEL kernel config setups at first glance, its actually quite
straight-forward and should be less error-prone. There's no potential
for configuration options getting out of order or conflicts when changing
adjacent configuraiton options.
pending-fedora - This directory contains configuration options that have not
been reviewed by Fedora kernel maintainers. Since the Fedora kernel turns on
more configuration options than ARK, there are often settings that are not set
to default in pending-common. These settings are moved to the fedora/
configuration directory after community review. Options are populated with
"make FLAVOR=fedora dist-commit-configs".
custom-overrides - This directory contains an empty set of the generic and debug
arch-specific directory tree. Any config option set here is applied last and
therefore will override anything set in the ark, fedora, or pending directories.
This allows users to easily override a config option without altering the
standard directories. Users can even maintain their own branch with a full set
of custom configuration options that can be easily be rebased on top of
os-build without worrying about conflicts.
All the configuration options for each arch and variant can be found
in the "priority" file.
If you want to make a change that applies to all kernels, debug and
non-debug alike, add a config option file under ark/generic/. If it should
only apply to all debug kernels, add it under ark/debug/. Arch-specific
options go under ark/generic/<arch>/ and so on. Each layer's individual config
option files are concatenated together with all other options at the same
level, then stacked atop the lower layers until reaching the highest
precedence layer for the given config option.
Send any questions, comments or concerns to rhkernel-list@redhat.com.

View File

@ -0,0 +1,134 @@
evaluate_configs is a tool that can verify the settings of kernel
CONFIGs in the redhat/configs directory. The data for evaluate_configs
is a combination of the redhat/configs files and the priority files.
Introduction to Basic Output
============================
This command demonstrates how to display information about the
CONFIG_HEADER_TEST option for RHEL.
[prarit@prarit configs]$ ./evaluate_configs -p priority.rhel -c CONFIG_HEADER_TEST
CONFIG_HEADER_TEST
legend g ga1 ga2 d da1 da2
common-x86_64 y - - - X -
common-ppc64le y - X - - X
common-s390x y - X - - X
common-s390x-zfcpdump y - - X X X
common-aarch64 y - - - X -
ark-x86_64 y - - - X -
ark-ppc64le y - X - - X
ark-s390x y - X - - X
ark-s390x-zfcpdump y - - X X X
ark-aarch64 y - - - X -
pending-common-x86_64 - - - - X -
pending-common-ppc64le - - X - - X
pending-common-s390x - - X - - X
pending-common-s390x-zfcpdump - - - X X X
pending-common-aarch64 - - - - X -
The legend row, shows the subdirectory entries. These can be mapped
back to the priority.rhel entries, for example, for x86_64
# x86_64
x86_64=generic:generic-x86:generic-x86-x86_64
x86_64-debug=generic:generic-x86:generic-x86-x86_64:debug:debug-x86-x86_64
are combined into one entry for x86_64 where
g maps to "generic"
ga1 maps to "generic-x86"
ga2 maps to "generic-x86-x86-64"
d maps to "debug"
da1 maps to nothing (more on this below)
da2 maps to debug-x86-x86_64
The left hand column indicates the directory and config-variant. For
example, ark-s390x-zfcpdump is the s390x-zfcpdump variant and the
row beside it shows the config settings in the ark directory.
The data contained in the output can have 5 values:
y = CONFIG is set to 'y'
m = CONFIG is set to 'm'
n = CONFIG is set to 'is not set'
- = CONFIG file does not exist
X = CONFIG file entry is not in priority file
As can be seen above in the CONFIG_HEADER_TEST output, da1 is not present
in the priority.rhel file and is marked with an 'X'.
Options
=======
-c CONFIG
Evalulate these specific CONFIGs. This can be a file,
or a comma-separated list. If nothing is specified then
all CONFIGs are examined by default.)
-d
Enable debug
-p priority.file
Specify a priority.file (no default)
-j
Evaluate common directory
-f
Evaluate and fix a priority's CONFIGs
All commands except -j require a -p argument.
Evaluate CONFIGs
================
The -f option can be used to evaluate all the CONFIGs by executing, for
example
# evaluate_configs -p priority.rhel -f
or a single CONFIG
# evaluate_configs -p priority.rhel -f -c CONFIG_HEADER_TEST
The Evaluate Output will show a different view than the Basic Output above:
ERROR: (hierarchy) ark/generic/CONFIG_HEADER_TEST : superseding value has y.
|CONFIG_HEADER_TEST (ark-aarch64)
|g ga1 ga2 d da1 da2 g ga1 ga2 d da1 da2 g ga1 ga2 d da1 da2
|y - - - X - y - - - X - - - - - X -
| Deleting ark/generic/CONFIG_HEADER_TEST
This view is the Basic Output's aarch64 data in a single line, From the
above output,
common-aarch64 y - - - X -
ark-aarch64 y - - - X -
pending-common-aarch64 - - - - X -
The Evaluate output makes it easier to visually see a conflict. One
can read the line and if there are two y|m|n separated by one or more - or
X's in a line, then there is the possibility of a conflict.
If the CONFIG setting is found to be incorrect it it automatically removed
and a message
| Deleting ark/generic/CONFIG_HEADER_TEST
will be output.
Evaluate common Directory
=========================
This function does a 1-to-1 comparison of CONFIG settings in the
ark and fedora directories, and checks to see if the CONFIG should be set
in the common directory.
The output is the same as the Evaluate output.
This functionality uses the priority.common file and can be executed via
evaluate_configs -j
for all CONFIGs, or
evaluate_configs -j -c CONFIG_HEADER_TEST
for a single CONFIG.

View File

@ -0,0 +1 @@
CONFIG_ATH10K_DEBUG=y

View File

@ -0,0 +1 @@
CONFIG_ATH10K_TRACING=y

View File

@ -0,0 +1 @@
# CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is not set

View File

@ -0,0 +1 @@
CONFIG_CFG80211_DEBUGFS=y

View File

@ -0,0 +1 @@
CONFIG_CGROUP_DEBUG=y

View File

@ -0,0 +1 @@
CONFIG_CPUMASK_OFFSTACK=y

View File

@ -0,0 +1 @@
CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN=y

View File

@ -0,0 +1 @@
CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=20000

View File

@ -0,0 +1 @@
CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1

View File

@ -0,0 +1 @@
CONFIG_DEBUG_PAGEALLOC=y

View File

@ -0,0 +1 @@
# CONFIG_DEBUG_PAGEALLOC_ENABLE_DEFAULT is not set

View File

@ -0,0 +1 @@
CONFIG_DEBUG_PAGE_REF=y

View File

@ -0,0 +1 @@
CONFIG_DEBUG_SLAB=y

View File

@ -0,0 +1 @@
CONFIG_DEBUG_VM=y

View File

@ -0,0 +1 @@
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120

View File

@ -0,0 +1 @@
CONFIG_DMADEVICES_VDEBUG=y

Some files were not shown because too many files have changed in this diff Show More