Compare commits

...

1214 Commits

Author SHA1 Message Date
Justin M. Forbes e6a1e060b5
Merge Linux v5.15.1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-07 12:56:08 -06:00
Greg Kroah-Hartman b6abb62daa Linux 5.15.1
Link: https://lore.kernel.org/r/20211104141159.551636584@linuxfoundation.org
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
Tested-by: Florian Fainelli <f.fainelli@gmail.com>
Tested-by: Ken Moffat <zarniwhoop@ntlworld.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:31 +01:00
Takashi Iwai 569fd073a9 ALSA: usb-audio: Add quirk for Audient iD14
commit df0380b953 upstream.

Audient iD14 (2708:0002) may get a control message error that
interferes the operation e.g. with alsactl.  Add the quirk to ignore
such errors like other devices.

BugLink: https://bugzilla.suse.com/show_bug.cgi?id=1191247
Cc: <stable@vger.kernel.org>
Link: https://lore.kernel.org/r/20211102161859.19301-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:31 +01:00
Matthew Brost fd5f954b69 Revert "drm/i915/gt: Propagate change in error status to children on unhold"
commit ac653dd799 upstream.

Propagating errors to dependent fences is broken and can lead to errors
from one client ending up in another. In commit 3761baae90 ("Revert
"drm/i915: Propagate errors on awaiting already signaled fences""), we
attempted to get rid of fence error propagation but missed the case
added in commit 8e9f84cf5c ("drm/i915/gt: Propagate change in error
status to children on unhold"). Revert that one too. This error was
found by an up-and-coming selftest which triggers a reset during
request cancellation and verifies that subsequent requests complete
successfully.

v2:
 (Daniel Vetter)
  - Use revert
v3:
 (Jason)
  - Update commit message

v4 (Daniele):
 - fix checkpatch error in commit message.

References: '3761baae908a ("Revert "drm/i915: Propagate errors on awaiting already signaled fences"")'
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20210909164744.31249-8-matthew.brost@intel.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:31 +01:00
Anson Jacob 8af3a335b5 drm/amd/display: Revert "Directly retrain link from debugfs"
commit 1131cadfd7 upstream.

This reverts commit f5b6a20c7e.

This patch broke new settings from taking effect. Hotplug is
required for new settings to take effect.

Reviewed-by: Mikita Lipski <mikita.lipski@amd.com>
Acked-by: Mikita Lipski <mikita.lipski@amd.com>
Signed-off-by: Anson Jacob <Anson.Jacob@amd.com>
Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:31 +01:00
Christian König 6ecad8906f drm/amdgpu: revert "Add autodump debugfs node for gpu reset v8"
commit c8365dbda0 upstream.

This reverts commit 728e7e0cd6.

Further discussion reveals that this feature is severely broken
and needs to be reverted ASAP.

GPU reset can never be delayed by userspace even for debugging or
otherwise we can run into in kernel deadlocks.

Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Alex Deucher <alexander.deucher@amd.com>
Acked-by: Nirmoy Das <nirmoy.das@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:31 +01:00
Bryan O'Donoghue a273384cf1 Revert "wcn36xx: Disable bmps when encryption is disabled"
commit 285bb1738e upstream.

This reverts commit c6522a5076.

Testing on tip-of-tree shows that this is working now. Revert this and
re-enable BMPS for Open APs.

Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Link: https://lore.kernel.org/r/20211022140447.2846248-3-bryan.odonoghue@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:31 +01:00
Wang Kefeng 57f31b3132 ARM: 9120/1: Revert "amba: make use of -1 IRQs warn"
commit eb4f756915 upstream.

After commit 77a7300aba ("of/irq: Get rid of NO_IRQ usage"),
no irq case has been removed, irq_of_parse_and_map() will return
0 in all cases when get error from parse and map an interrupt into
linux virq space.

amba_device_register() is only used on no-DT initialization, see
  s3c64xx_pl080_init()		arch/arm/mach-s3c/pl080.c
  ep93xx_init_devices()		arch/arm/mach-ep93xx/core.c

They won't set -1 to irq[0], so no need the warn.

This reverts commit 2eac58d502.

Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:31 +01:00
Lucas Stach 110d5f4421 Revert "soc: imx: gpcv2: move reset assert after requesting domain power up"
commit 2b2f106eb5 upstream.

This reverts commit a77ebdd9f553. It turns out that the VPU domain has no
different requirements, even though the downstream ATF implementation seems
to suggest otherwise. Powering on the domain with the reset asserted works
fine. As the changed sequence has caused sporadic issues with the GPU
domains, just revert the change to go back to the working sequence.

Cc: <stable@vger.kernel.org> # 5.14
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Acked-by: Peng Fan <peng.fan@nxp.com>
Tested-by: Adam Ford <aford173@gmail.com> #imx8mm-beacon
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:30 +01:00
Yifan Zhang f17dca0ab3 drm/amdkfd: fix boot failure when iommu is disabled in Picasso.
commit afd18180c0 upstream.

When IOMMU disabled in sbios and kfd in iommuv2 path, iommuv2
init will fail. But this failure should not block amdgpu driver init.

Reported-by: youling <youling257@gmail.com>
Tested-by: youling <youling257@gmail.com>
Signed-off-by: Yifan Zhang <yifan1.zhang@amd.com>
Reviewed-by: James Zhu <James.Zhu@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:30 +01:00
Greg Kroah-Hartman f5e3b7f0f0 Revert "usb: core: hcd: Add support for deferring roothub registration"
This reverts commit 58877b0824.

It has been reported to be causing problems in Arch and Fedora bug
reports.

Reported-by: Hans de Goede <hdegoede@redhat.com>
Link: https://bbs.archlinux.org/viewtopic.php?pid=2000956#p2000956
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2019542
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2019576
Link: https://lore.kernel.org/r/42bcbea6-5eb8-16c7-336a-2cb72e71bc36@redhat.com
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Chris Chiu <chris.chiu@canonical.com>
Cc: Alan Stern <stern@rowland.harvard.edu>
Cc: Kishon Vijay Abraham I <kishon@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:30 +01:00
Greg Kroah-Hartman 421f91bf04 Revert "xhci: Set HCD flag to defer primary roothub registration"
This reverts commit b7a0a792f8.

It has been reported to be causing problems in Arch and Fedora bug
reports.

Reported-by: Hans de Goede <hdegoede@redhat.com>
Link: https://bbs.archlinux.org/viewtopic.php?pid=2000956#p2000956
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2019542
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2019576
Link: https://lore.kernel.org/r/42bcbea6-5eb8-16c7-336a-2cb72e71bc36@redhat.com
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Chris Chiu <chris.chiu@canonical.com>
Cc: Alan Stern <stern@rowland.harvard.edu>
Cc: Kishon Vijay Abraham I <kishon@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:30 +01:00
Dan Carpenter cb66714087 media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt()
commit 35d2969ea3 upstream.

The bounds checking in avc_ca_pmt() is not strict enough.  It should
be checking "read_pos + 4" because it's reading 5 bytes.  If the
"es_info_length" is non-zero then it reads a 6th byte so there needs to
be an additional check for that.

I also added checks for the "write_pos".  I don't think these are
required because "read_pos" and "write_pos" are tied together so
checking one ought to be enough.  But they make the code easier to
understand for me.  The check on write_pos is:

	if (write_pos + 4 >= sizeof(c->operand) - 4) {

The first "+ 4" is because we're writing 5 bytes and the last " - 4"
is to leave space for the CRC.

The other problem is that "length" can be invalid.  It comes from
"data_length" in fdtv_ca_pmt().

Cc: stable@vger.kernel.org
Reported-by: Luo Likang <luolikang@nsfocus.com>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:30 +01:00
Erik Ekman abc558fd0f sfc: Fix reading non-legacy supported link modes
commit 041c614882 upstream.

Everything except the first 32 bits was lost when the pause flags were
added. This makes the 50000baseCR2 mode flag (bit 34) not appear.

I have tested this with a 10G card (SFN5122F-R7) by modifying it to
return a non-legacy link mode (10000baseCR).

Signed-off-by: Erik Ekman <erik@kryo.se>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2021-11-06 14:13:30 +01:00
Justin M. Forbes 53a48f391e
Turn on COMMON_CLK_AXG_AUDIO for Fedora rhbz 2020481
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-05 07:36:27 -05:00
Justin M. Forbes c2e5ed5097 Merge branch '5.15-pbr' into 'fedora-5.15'
Some minor updates

See merge request cki-project/kernel-ark!1471
2021-11-03 18:55:07 +00:00
Peter Robinson 4c50f615a1 fedora: gpio: tweak some GPIO drivers
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-03 14:28:30 +00:00
Peter Robinson b4ca45cd1c Enable VMXNET3 for aarch64
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-03 14:16:03 +00:00
Peter Robinson 8998c342cd all: drop removed obsolete config options
No functional change, options dropped upstream and were disabled
already.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-03 14:16:00 +00:00
Justin M. Forbes 98f229f64b
Revert "fedora: Disable fbdev drivers and use simpledrm instead"
This reverts commit 655b80fea3.
2021-11-02 14:20:45 -05:00
Justin M. Forbes 2cc6498a91
Enable binder for fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 14:34:09 -05:00
Justin M. Forbes 1c915f7a95
Add fedora-dist-git-test.sh and release_targets
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:58:05 -05:00
Justin M. Forbes 90ef303256
Update Makefile.variables for 5.15 stable
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:50:38 -05:00
Justin M. Forbes a850aaf6d4
Reset RHEL_RELEASE for 5.16
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:18 -05:00
Kamal Heib ae2439d18c
redhat: configs: Update configs for vmware
Based on VMware's request enable vmxnet3 and disable vmw_pvrdma for
aarch64.

Signed-off-by: Kamal Heib <kheib@redhat.com>
2021-11-01 13:45:18 -05:00
Justin M. Forbes 2a14209bcf
Fedora configs for 5.15
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:18 -05:00
Jan Stancek 1f645ee6f0
redhat/kernel.spec.template: don't hardcode gcov arches
Use all arches except nobuildarches and noarch.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
2021-11-01 13:45:18 -05:00
Jan Stancek cec484e434
redhat/configs: create a separate config for gcov options
Use existing config infrastructure to build and validate
gcov-enabled configs. Meaning for each arch we also apply
GCOV options on top and validate it.

From same options dir (kgcov) build also partial config, which
contains only GCOV options. We can merge this partial config
during build on top of existing config, which avoids the need
to store all possible combinations in dist-git and SRPM.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
2021-11-01 13:45:18 -05:00
Don Zickus 00696038e5
Update documentation with FAQ and update frequency
I added an FAQ section based on questions I hear all the time
from developers.  Also based on feedback, I added how often the
different brances are updated.  Not everyone realizes it is daily.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-11-01 13:45:18 -05:00
Don Zickus bf15347eb0
Document force pull option for mirroring
kernel-ark rebases every GA which breaks mirroring.  Update
the docs to tell users to expect this by overwriting divergent
branches.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-11-01 13:45:18 -05:00
Don Zickus e97ee07407
Ignore the rhel9 kabi files
Use a more generic filter to ignore the kabi files.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-11-01 13:45:17 -05:00
Don Zickus 4373c77945
Remove legacy elrdy cruft
Remove an idea that never worked out, 'elrdy'.  The Makefiles have
enough complexity in there, lets remove a layer of it, in hopes someone
finds a way to simplify things.

Signed-off-by: Don Zickus <dzickus@redhat.com>
2021-11-01 13:45:17 -05:00
Prarit Bhargava 85b87c0f49
RHMAINTAINERS: Update for Oct 29 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:45:17 -05:00
Fedora Kernel Team 5477f03189
[redhat] kernel-5.15.0-59
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:17 -05:00
Fedora Kernel Team 7c222810d1
[redhat] kernel-5.15.0-0.rc7.20211031git180eca540ae0.58
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:17 -05:00
Fedora Kernel Team 49c83608dc
[redhat] kernel-5.15.0-0.rc7.20211030git119c85055d86.57
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:17 -05:00
Fedora Kernel Team e5636363a5
[redhat] kernel-5.15.0-0.rc7.20211029gitf25a5481af12.56
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:16 -05:00
Jan Stancek a3fa4dfc7d
redhat/configs/evaluate_configs: walk cfgvariants line by line
get_subdirs() code suggests it should walk cfgvariants line by line,
but with quotes it passes everything to inner loop.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
2021-11-01 13:45:16 -05:00
Jan Stancek 3ac02acaac
redhat/configs/evaluate_configs: insert EMPTY tags at correct place
evaluate_configs currently inserts empty tags always at the end
of cfgvariants line, which breaks the table if a new variant
is introduced (which is not a super-set of debug variant).

Let's walk cfgvariants to discover all toplevel directories
and give each an ordering number. Then during addition of EMPTY
tags walk through existing tags and compare ordering number of
toplevel portion of each tag. This number determines where
to insert new tag.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
2021-11-01 13:45:16 -05:00
Jan Stancek 48537c71a0
redhat: make dist-srpm-gcov add to BUILDOPTS
Don't reset other BUILDOPTS when using dist-srpm-gcov target.

Fixes: 528777da30 ("Fix dist-srpm-gcov")
Signed-off-by: Jan Stancek <jstancek@redhat.com>
2021-11-01 13:45:16 -05:00
Fedora Kernel Team 91ea913eb0
[redhat] kernel-5.15.0-0.rc7.20211028git1fc596a56b33.55
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:16 -05:00
Justin M. Forbes f7293961af
Build CONFIG_SPI_PXA2XX as a module on x86
While turning off CONFIG_SPI_PXA2XX was the reviewed and set option for
RHEL, SND_SOC_INTEL_BDW_RT5677_MACH is built as a module in RHEL 8 and
was set that way for ark/RHEL 9. Unofrtunately that driver depends on
the SPI controller, and upstream commit 630db15493 made it select
SPI_PXA2XX leaving us with a broken config. At some point, an entry was
made in pending-common to enable SPI_PXA2XX on x86, but there was no
corresponding MR to get review and make it official.  We have been
building this way for over a year, so let's review this and set it
properly.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:16 -05:00
Joel Savitz 47a369030c
redhat/configs: enable CONFIG_BCMGENET as module
The genet driver enables the use of ethernet on SOCs including
that of the Raspberry Pi 4B.

Upstream Status: RHEL-only
Tested: on a physical Raspberry Pi 4B

Signed-off-by: Joel Savitz <jsavitz@redhat.com>
2021-11-01 13:45:16 -05:00
Fedora Kernel Team 782d351097
[redhat] kernel-5.15.0-0.rc7.20211027gitd25f27432f80.54
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:15 -05:00
Justin M. Forbes bc22c96765
Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:15 -05:00
Fedora Kernel Team c6b90da43f
[redhat] kernel-5.15.0-0.rc7.53
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:15 -05:00
Justin M. Forbes 8f64d31054
Enable CONFIG_FAIL_SUNRPC for debug builds
As was requested in MR 1350, this will enable FAIL_SUNRPC for debug
builds.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:15 -05:00
Fedora Kernel Team 2b165f24e2
[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.

 Symbol: VDPA_USER [=n]
 Type  : tristate
 Defined at drivers/vdpa/Kconfig:36
   Prompt: VDUSE (vDPA Device in Userspace) support
   Depends on: VDPA [=m] && EVENTFD [=y] && MMU [=y] && HAS_DMA [=y]
   Location:
     -> Device Drivers
       -> vDPA drivers (VDPA [=m])
 Selects: DMA_OPS [=y] && VHOST_IOTLB [=m] && IOMMU_IOVA [=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>
2021-11-01 13:45:15 -05:00
Fedora Kernel Team aa2cd59c27
[redhat] New configs in certs/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: MODULE_SIG_KEY_TYPE_ECDSA [=n]
 Type  : bool
 Defined at certs/Kconfig:31
   Prompt: ECDSA
   Depends on: <choice> && (MODULE_SIG [=y] || IMA_APPRAISE_MODSIG [=y] && MODULES [=y])
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Certificates for signature checking
         -> Type of module signing key to be generated (<choice> [=y])
 Selects: CRYPTO_ECDSA [=m]

---

 Symbol: MODULE_SIG_KEY_TYPE_RSA [=y]
 Type  : bool
 Defined at certs/Kconfig:25
   Prompt: RSA
   Depends on: <choice> && (MODULE_SIG [=y] || IMA_APPRAISE_MODSIG [=y] && MODULES [=y])
   Location:
     -> Cryptographic API (CRYPTO [=y])
       -> Certificates for signature checking
         -> Type of module signing key to be generated (<choice> [=y])

---

Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:15 -05:00
Fedora Kernel Team a7613e9a45
[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: FAIL_SUNRPC [=n]
 Type  : bool
 Defined at lib/Kconfig.debug:1948
   Prompt: Fault-injection capability for SunRPC
   Depends on: FAULT_INJECTION_DEBUG_FS [=y] && SUNRPC_DEBUG [=y]
   Location:
     -> Kernel hacking
       -> Kernel Testing and Coverage
         -> Fault-injection framework (FAULT_INJECTION [=y])
           -> Debugfs entries for fault-injection capabilities (FAULT_INJECTION_DEBUG_FS [=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-11-01 13:45:15 -05:00
Fedora Kernel Team 47f1554195
[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.

 Symbol: QCOM_LMH [=n]
 Type  : tristate
 Defined at drivers/thermal/qcom/Kconfig:35
   Prompt: Qualcomm Limits Management Hardware
   Depends on: THERMAL [=y] && (ARCH_QCOM [=y] && OF [=y] || COMPILE_TEST [=n]) && ARCH_QCOM [=y]
   Location:
     -> Device Drivers
       -> Thermal drivers (THERMAL [=y])
         -> Qualcomm thermal drivers

---

Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:14 -05:00
Fedora Kernel Team ef59ddf704
[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.

 Symbol: MFD_RSMU_I2C [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:2202
   Prompt: Renesas Synchronization Management Unit with I2C
   Depends on: HAS_IOMEM [=y] && I2C [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_CORE [=m] && REGMAP_I2C [=m]

---

 Symbol: MFD_RSMU_SPI [=n]
 Type  : tristate
 Defined at drivers/mfd/Kconfig:2216
   Prompt: Renesas Synchronization Management Unit with SPI
   Depends on: HAS_IOMEM [=y] && SPI [=y] && OF [=y]
   Location:
     -> Device Drivers
       -> Multifunction device drivers
 Selects: MFD_CORE [=m] && REGMAP_SPI [=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-11-01 13:45:14 -05:00
Javier Martinez Canillas 655b80fea3
fedora: Disable fbdev drivers and use simpledrm instead
Replace the fbdev drivers, that are still used in Fedora with
the latest simpledrm driver and the DRM fbdev emulation layer.

Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
2021-11-01 13:45:14 -05:00
Fedora Kernel Team 18d99d862d
[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.

 Symbol: PINCTRL_MSM [=n]
 Type  : tristate
 Defined at drivers/pinctrl/qcom/Kconfig:4
   Prompt: Qualcomm core pin controller driver
   Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && (QCOM_SCM [=n] || !QCOM_SCM [=n])
   Location:
     -> Device Drivers
       -> Pin controllers (PINCTRL [=y])
 Selects: PINMUX [=y] && PINCONF [=y] && GENERIC_PINCONF [=y] && GPIOLIB_IRQCHIP [=y] && IRQ_DOMAIN_HIERARCHY [=y] && IRQ_FASTEOI_HIERARCHY_HANDLERS [=n]

---

Cc: Brian Masney <bmasney@redhat.com>
Cc: David Arcari <darcari@redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:14 -05:00
Fedora Kernel Team 85e6bd16c8
[redhat] kernel-5.15.0-0.rc6.20211025git87066fdd2e30.52
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:14 -05:00
Fedora Kernel Team bf277805f1
[redhat] kernel-5.15.0-0.rc6.20211023git9c0c4d24ac00.51
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:14 -05:00
Fedora Kernel Team 1c84700733
[redhat] kernel-5.15.0-0.rc6.20211022git64222515138e.50
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:14 -05:00
Fedora Kernel Team aa0a803098
[redhat] kernel-5.15.0-0.rc6.20211021git2f111a6fd5b5.49
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:13 -05:00
Jiri Olsa 6523864cf0
spec: Don't fail spec build if ksamples fails
Make sure ksamples failed build does not break the wholo rpm build.
This change was missed in the original change:
  83987025a7 spec: Allow bpf selftest/samples to fail

Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-11-01 13:45:13 -05:00
Justin M. Forbes 68c5b36a7f
Enable CONFIG_QCOM_SCM for arm
Commit 0f0f80d9d5 added
CONFIG_ARM_SMMU_QCOM which is a hidden config that defaults to on if
ARM_SMMU and ARCH_QCOM are enabled.   It also selects QCOM_SCM. As both
ARM_SMMU and ARCH_QCOM are enabled for RHEL configs, we need to flip
QCOM_SCM for arm as well of we get a mismatch.  Doing so will also
create a new config item QCOM_SCM_DOWNLOAD_MODE_DEFAULT, which I have
left at the default config of off. If that needs to change, I am happy
to change it.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:13 -05:00
Fedora Kernel Team 89f6025c2b
[redhat] kernel-5.15.0-0.rc6.20211020gitd9abdee5fd5a.48
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:13 -05:00
Fedora Kernel Team 93029ffa93
[redhat] kernel-5.15.0-0.rc6.47
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:13 -05:00
Tom Stellard 4e5436858f
redhat: Disable clang's integrated assembler on ppc64le and s390x
Clang's integrated assembler was failing on these architecures, so
we need to fallback on binutils instead.

Signed-off-by: Tom Stellard <tstellar@redhat.com>
2021-11-01 13:45:13 -05:00
Bruno Meneguele 15a9ac3c80
redhat/configs: enable CONFIG_IMA_WRITE_POLICY
CONFIG_IMA_WRITE_POLICY is enabled in Fedora and is being enabled in
CentOS Stream 9 and, consequently, RHEL-9. Enable it in ARK for future
releases too.

Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>
2021-11-01 13:45:13 -05:00
Fedora Kernel Team 7b84e42a49
[redhat] kernel-5.15.0-0.rc6.46
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:12 -05:00
Fedora Kernel Team 920f719d6d
[redhat] kernel-5.15.0-0.rc5.20211017gitd999ade1cc86.45
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:12 -05:00
Fedora Kernel Team 1ef42b6460
[redhat] AUTOMATIC: New configs 2021-11-01 13:45:12 -05:00
Fedora Kernel Team 616764c665
[redhat] kernel-5.15.0-0.rc5.20211016git8fe31e0995f0.44
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:12 -05:00
CKI Gitlab b9bf65ef84
[redhat] New configs in sound/pci 2021-11-01 13:45:12 -05:00
Fedora Kernel Team 4622a631aa
[redhat] kernel-5.15.0-0.rc5.20211015gitec681c53f8d2.43
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:12 -05:00
Don Zickus 74624a1312
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-11-01 13:45:12 -05:00
John W. Linville b7881fdc17
redhat: configs: add CONFIG_NTB and related items
Signed-off-by: John W. Linville <linville@redhat.com>
2021-11-01 13:45:11 -05:00
Justin M. Forbes 58e66a7539
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-11-01 13:45:11 -05:00
Fedora Kernel Team 4ba81ef237
[redhat] kernel-5.15.0-0.rc5.20211014git348949d9a444.42
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:11 -05:00
Fedora Kernel Team d755366020
[redhat] kernel-5.15.0-0.rc5.20211013gitf4d0cc426f77.41
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:11 -05:00
Fedora Kernel Team 001d5c9f27
[redhat] kernel-5.15.0-0.rc5.20211012gitfa5878760579.40
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:11 -05:00
CKI Gitlab e62c88004e
[redhat] New configs in arch/powerpc 2021-11-01 13:45:11 -05:00
Fedora Kernel Team 90dd653f2a
[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-11-01 13:45:10 -05:00
Nico Pache 46e2002710
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-11-01 13:45:10 -05:00
Herton R. Krzesinski 5e7cb7cec2
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-11-01 13:45:10 -05:00
Mark Salter 2c23f619a0
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-11-01 13:45:10 -05:00
Fedora Kernel Team d4a96906a7
[redhat] kernel-5.15.0-0.rc5.39
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:10 -05:00
Fedora Kernel Team 0c5c8d417f
[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-11-01 13:45:10 -05:00
Fedora Kernel Team 5cfddbf3ed
[redhat] kernel-5.15.0-0.rc4.20211010git7fd2bf83d59a.38
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:10 -05:00
Fedora Kernel Team f2f8e0cd81
[redhat] kernel-5.15.0-0.rc4.20211009git5d6ab0bb408f.37
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:09 -05:00
Herton R. Krzesinski 6e5a7f21a9
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-11-01 13:45:09 -05:00
Fedora Kernel Team 8fd0346f99
[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-11-01 13:45:09 -05:00
Fedora Kernel Team 18db3fd54e
[redhat] kernel-5.15.0-0.rc4.20211008git1da38549dd64.36
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:09 -05:00
Fedora Kernel Team 66259e3d1b
[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-11-01 13:45:09 -05:00
Fedora Kernel Team 7c48b3097a
[redhat] kernel-5.15.0-0.rc4.20211007git5af4055fa813.35
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:09 -05:00
Justin M. Forbes ba3cc6c3e0
Fedora NTFS config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:09 -05:00
Justin M. Forbes 16820ea4a1
Fedora 5.15 configs part 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:08 -05:00
Fedora Kernel Team 2e2222ad97
[redhat] kernel-5.15.0-0.rc4.20211006git60a9483534ed.34
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:08 -05:00
Fedora Kernel Team 7d4a1f288f
[redhat] kernel-5.15.0-0.rc4.20211005gitf6274b06e326.33
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:08 -05:00
Justin M. Forbes 5bc8dcdfea
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-11-01 13:45:08 -05:00
Fedora Kernel Team 4b03685949
[redhat] kernel-5.15.0-0.rc4.32
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:08 -05:00
Fedora Kernel Team 2bffbc1972
[redhat] kernel-5.15.0-0.rc3.20211003git7b66f4393ad4.31
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:08 -05:00
Fedora Kernel Team 4f9bcc2d01
[redhat] kernel-5.15.0-0.rc3.20211002git53d5fc89d66a.30
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:08 -05:00
Vitaly Kuznetsov f91c435989
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-11-01 13:45:07 -05:00
Hans de Goede 7575f910b1
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-11-01 13:45:07 -05:00
Fedora Kernel Team a737382d1f
[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-11-01 13:45:07 -05:00
Fedora Kernel Team d3583b5f0c
[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-11-01 13:45:07 -05:00
Joel Savitz f96534b46a
redhat/docs: update Koji link to avoid redirect
Signed-off-by: Joel Savitz <jsavitz@redhat.com>
2021-11-01 13:45:07 -05:00
Prarit Bhargava ccfa382d94
RHMAINTAINERS: Update for Oct 1 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:45:07 -05:00
Herton R. Krzesinski c1afdcbe65
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-11-01 13:45:07 -05:00
Fedora Kernel Team 41bfdce270
[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-11-01 13:45:06 -05:00
Fedora Kernel Team 1383ae5bc0
[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-11-01 13:45:06 -05:00
Fedora Kernel Team 13072ba4f8
[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-11-01 13:45:06 -05:00
Fedora Kernel Team fc1bfdef9c
[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-11-01 13:45:06 -05:00
Phil Sutter f8a3b62e4d
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-11-01 13:45:06 -05:00
Fedora Kernel Team c675898bf5
[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-11-01 13:45:06 -05:00
Fedora Kernel Team dafeb8b698
[redhat] kernel-5.15.0-0.rc3.20211001git4de593fb965f.29
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:06 -05:00
Justin M. Forbes 4ba095e331
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-11-01 13:45:05 -05:00
Justin M. Forbes df2bcdb0d0
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-11-01 13:45:05 -05:00
Herton R. Krzesinski ebb3ac72aa
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-11-01 13:45:05 -05:00
Fedora Kernel Team 08bdfc5fa8
[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-11-01 13:45:05 -05:00
Prarit Bhargava 6f66bcb0cc
redhat/kernel.spec.template: Cleanup source numbering
Cleanup the numbering of the source files.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:45:05 -05:00
Prarit Bhargava d83270dbfc
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-11-01 13:45:05 -05:00
Prarit Bhargava daea1360c6
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-11-01 13:45:05 -05:00
Prarit Bhargava de8e6bc2ed
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-11-01 13:45:05 -05:00
Prarit Bhargava 1ae6e7a1ae
redhat/Makefile: Use flavors file
Use the configs/flavors file instead of hardcoding directory copies.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:45:04 -05:00
Justin M. Forbes 2a46667304
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-11-01 13:45:04 -05:00
Fedora Kernel Team 09f33282c9
[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-11-01 13:45:04 -05:00
Fedora Kernel Team a30a8af331
[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-11-01 13:45:04 -05:00
Fedora Kernel Team 333068e661
[redhat] kernel-5.15.0-0.rc3.20210930git02d5e016800d.28
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:04 -05:00
Kamal Heib 18b91785b1
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-11-01 13:45:04 -05:00
Fedora Kernel Team 25f7a9a7cd
[redhat] kernel-5.15.0-0.rc3.20210929gita4e6f95a891a.27
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:04 -05:00
Fedora Kernel Team f2006e39fa
[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-11-01 13:45:03 -05:00
David Arcari 85b39afa70
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-11-01 13:45:03 -05:00
Fedora Kernel Team ca226c6e09
[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-11-01 13:45:03 -05:00
Fedora Kernel Team 0137925223
[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-11-01 13:45:03 -05:00
Herton R. Krzesinski 109d6314e5
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-11-01 13:45:03 -05:00
Fedora Kernel Team 69430a500b
[redhat] kernel-5.15.0-0.rc3.20210928git0513e464f900.26
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:03 -05:00
Justin M. Forbes b8d66cac5d
Manually add pending items that need to be set due to mismatch
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:03 -05:00
Fedora Kernel Team 17663b9ea5
[redhat] AUTOMATIC: New configs 2021-11-01 13:45:02 -05:00
Fedora Kernel Team 8446ec8019
[redhat] AUTOMATIC: New configs 2021-11-01 13:45:02 -05:00
Justin M. Forbes 020866326d
Clean up pending common
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:45:02 -05:00
Waiman Long f323e86486
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-11-01 13:45:02 -05:00
Herton R. Krzesinski cb1d88925b
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-11-01 13:45:02 -05:00
Fedora Kernel Team 89b83efbe0
[redhat] kernel-5.15.0-0.rc3.25
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:02 -05:00
Fedora Kernel Team b8699abe1e
[redhat] kernel-5.15.0-0.rc2.20210926gita3b397b4fffb.24
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:01 -05:00
Fedora Kernel Team 242c0d2ac0
[redhat] kernel-5.15.0-0.rc2.20210925git7d42e9818258.23
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:01 -05:00
Fedora Kernel Team 8323b8f8c6
[redhat] kernel-5.15.0-0.rc2.20210924gitf9e36107ec70.22
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:01 -05:00
Fedora Kernel Team 28764c6850
[redhat] kernel-5.15.0-0.rc2.20210923git58e2cf5d7946.21
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:01 -05:00
Claudio Imbrenda ed9235e9b1
[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-11-01 13:45:01 -05:00
Tao Liu 22d02d9bc3
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-11-01 13:45:01 -05:00
Fedora Kernel Team 55f98d793e
[redhat] kernel-5.15.0-0.rc2.20210922git92477dd1faa6.20
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:01 -05:00
Fedora Kernel Team 37295b765b
[redhat] kernel-5.15.0-0.rc2.20210921gitd9fb678414c0.19
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:00 -05:00
Fedora Kernel Team aeb653ae20
[redhat] kernel-5.15.0-0.rc2.18
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:00 -05:00
Fedora Kernel Team 5393abc0b7
[redhat] kernel-5.15.0-0.rc1.20210919gitd4d016caa4b8.17
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:00 -05:00
Fedora Kernel Team e43609ec28
[redhat] kernel-5.15.0-0.rc1.20210918git4357f03d6611.16
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:00 -05:00
Herton R. Krzesinski 8d762c8e27
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-11-01 13:45:00 -05:00
Herton R. Krzesinski 32d2f92fb7
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-11-01 13:45:00 -05:00
Fedora Kernel Team b5eb5664ab
[redhat] kernel-5.15.0-0.rc1.20210917gitbdb575f87217.15
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:45:00 -05:00
Coiby Xu fc20ce1737
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-11-01 13:44:59 -05:00
Fedora Kernel Team 7fe6344aec
[redhat] kernel-5.15.0-0.rc1.20210916gitff1ffd71d5f0.14
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:59 -05:00
Justin M. Forbes 3bddcd5ab7
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-11-01 13:44:59 -05:00
Fedora Kernel Team 79a5638e53
[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-11-01 13:44:59 -05:00
Fedora Kernel Team 86e8a753bb
[redhat] kernel-5.15.0-0.rc1.20210915git3ca706c189db.13
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:59 -05:00
Prarit Bhargava 7c4878335f
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-11-01 13:44:59 -05:00
Fedora Kernel Team 2e841c4623
[redhat] kernel-5.15.0-0.rc1.20210914gitd0ee23f9d78b.12
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:59 -05:00
Fedora Kernel Team 5ea7fd6a05
[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-11-01 13:44:58 -05:00
Fedora Kernel Team 77c0b28735
[redhat] kernel-5.15.0-0.rc1.11
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:58 -05:00
Fedora Kernel Team 76fbdce247
[redhat] kernel-5.15.0-0.rc0.20210912git78e709522d2c.10
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:58 -05:00
Fedora Kernel Team 9115ca6580
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:58 -05:00
Fedora Kernel Team fd808090c0
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:58 -05:00
Fedora Kernel Team 443f5ec52b
[redhat] kernel-5.15.0-0.rc0.20210911git926de8c4326c.9
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:58 -05:00
Fedora Kernel Team 4d29428eb6
[redhat] kernel-5.15.0-0.rc0.20210910gitbf9f243f23e6.8
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:58 -05:00
Fedora Kernel Team 8d009c2721
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:57 -05:00
Fedora Kernel Team 832bc00c3f
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:57 -05:00
Fedora Kernel Team 10ff004d0a
[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-11-01 13:44:57 -05:00
Fedora Kernel Team cbdf483197
[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-11-01 13:44:57 -05:00
Justin M. Forbes 9888909f60
Update CONFIG_WERROR to disabled as it can cause issue with out of tree modules. 2021-11-01 13:44:57 -05:00
Fedora Kernel Team 5b1b8e9654
[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-11-01 13:44:57 -05:00
Justin M. Forbes b814c6bf47
Fixup IOMMU configs in pending so that configs are sane again
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:57 -05:00
Fedora Kernel Team 7e033d26d5
[redhat] kernel-5.15.0-0.rc0.20210909gita3fa7a101dcf.7
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:57 -05:00
Fedora Kernel Team 8e661fe3ac
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:56 -05:00
Fedora Kernel Team 16aeea7f5d
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:56 -05:00
Fedora Kernel Team 33edfa7410
[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-11-01 13:44:56 -05:00
Fedora Kernel Team 99a1e03db9
[redhat] kernel-5.15.0-0.rc0.20210908gitac08b1c68d1b.6
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:56 -05:00
Fedora Kernel Team 83b85384ed
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:56 -05:00
Fedora Kernel Team 8bfc6c1dc8
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:56 -05:00
Justin M. Forbes 4371acbd3c
Some initial Fedora config items for 5.15
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:56 -05:00
Fedora Kernel Team d779577293
[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-11-01 13:44:55 -05:00
Fedora Kernel Team d95b7c85bc
[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-11-01 13:44:55 -05:00
Fedora Kernel Team 4567bdf4c3
[redhat] kernel-5.15.0-0.rc0.20210907git4b93c544e90e.5
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:55 -05:00
Fedora Kernel Team 946ca68fad
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:55 -05:00
Fedora Kernel Team 693f7a4a2f
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:55 -05:00
Patrick Talbert 5464e4db69
[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-11-01 13:44:55 -05:00
Fedora Kernel Team d7554abe76
[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-11-01 13:44:55 -05:00
Fedora Kernel Team c26318c545
[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-11-01 13:44:54 -05:00
Fedora Kernel Team 078ee99541
[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-11-01 13:44:54 -05:00
Fedora Kernel Team c148ad18be
[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-11-01 13:44:54 -05:00
Fedora Kernel Team d7baf971a3
[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-11-01 13:44:54 -05:00
Fedora Kernel Team a74cb837bc
[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-11-01 13:44:54 -05:00
Fedora Kernel Team f4660852c4
[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-11-01 13:44:54 -05:00
CKI Gitlab aa5cc4baaf
[redhat] New configs in init/Kconfig 2021-11-01 13:44:54 -05:00
Fedora Kernel Team b4cea63568
[redhat] kernel-5.15.0-0.rc0.20210903gita9c9a6f741cd.4
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:53 -05:00
Fedora Kernel Team 047f4aac07
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:53 -05:00
Fedora Kernel Team bcf4ea1a09
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:53 -05:00
Fedora Kernel Team b3cfaf668a
[redhat] kernel-5.15.0-0.rc0.20210902git4ac6d90867a4.3
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:53 -05:00
Fedora Kernel Team bc6b8dda21
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:53 -05:00
Fedora Kernel Team ced807ac5f
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:53 -05:00
Fedora Kernel Team e530e1c76b
[redhat] kernel-5.15.0-0.rc0.20210901git9e9fb7655ed5.2
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:53 -05:00
Fedora Kernel Team 73e4be6c97
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:53 -05:00
Fedora Kernel Team c5ea73b21d
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:52 -05:00
Fedora Kernel Team 843c9a9101
[redhat] kernel-5.15.0-0.rc0.20210831gitb91db6a0b52e.1
Signed-off-by: Fedora Kernel Team <kernel-team@fedoraproject.org>
2021-11-01 13:44:52 -05:00
Fedora Kernel Team b17be0be56
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:52 -05:00
Fedora Kernel Team 7729232a66
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:52 -05:00
Mark Salter ad98d0f25e
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-11-01 13:44:52 -05:00
Justin M. Forbes 7867510f8a
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-11-01 13:44:52 -05:00
Herton R. Krzesinski d9c8f67cd7
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-11-01 13:44:52 -05:00
Gustavo Walbon 9563e12033
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-11-01 13:44:51 -05:00
Fedora Kernel Team fa4ff68318
[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-11-01 13:44:51 -05:00
David Arcari 51f44f9823
Attempt to fix Intel PMT code 2021-11-01 13:44:51 -05:00
Fedora Kernel Team aefd21df54
[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-11-01 13:44:51 -05:00
Veronika Kabatova 8bcdffd185
CI: Enable realtime branch testing
Bugzilla: INTERNAL
Upstream Status: RHEL-only

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-11-01 13:44:51 -05:00
Veronika Kabatova 6e25bbca27
CI: Enable realtime checks for c9s and RHEL9
Upstream Status: RHEL-only
Bugzilla: INTERNAL

Signed-off-by: Veronika Kabatova <vkabatov@redhat.com>
2021-11-01 13:44:51 -05:00
Fedora Kernel Team 5c834c58c8
[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-11-01 13:44:51 -05:00
Fedora Kernel Team 2e4c91a95d
[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-11-01 13:44:50 -05:00
Bill O'Donnell b6389968a1
[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-11-01 13:44:50 -05:00
Peter Robinson 5aba2051d1
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-11-01 13:44:50 -05:00
Peter Robinson 5f5d2f7583
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-11-01 13:44:50 -05:00
Peter Robinson a6d380fd79
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-11-01 13:44:50 -05:00
Peter Robinson d445d05210
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-11-01 13:44:50 -05:00
Fedora Kernel Team 98e5593465
[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-11-01 13:44:49 -05:00
Matthias Brugger e3e9737865
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-11-01 13:44:49 -05:00
Dan Johansen 5dab5e4c4c
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-11-01 13:44:49 -05:00
Tomas Henzl d0b1a0a409
[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-11-01 13:44:49 -05:00
Herton R. Krzesinski 96369a02c5
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-11-01 13:44:49 -05:00
Justin M. Forbes b89487e92c
More Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:49 -05:00
Prarit Bhargava c2212f5dcf
RHMAINTAINERS: Update for Aug 20 2021
Update RHMAINTAINERS.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:44:48 -05:00
Fedora Kernel Team cc7d5bf8ce
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:48 -05:00
Justin M. Forbes bcb8a72db4
Fedora config updates for 5.14
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:48 -05:00
Veronika Kabatova addddac930
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-11-01 13:44:48 -05:00
Veronika Kabatova fa3bec2bff
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-11-01 13:44:48 -05:00
Veronika Kabatova 4df29ee9f1
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-11-01 13:44:48 -05:00
Veronika Kabatova 62f7b5c099
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-11-01 13:44:48 -05:00
Justin M. Forbes 70c562a8e5
Filter updates for aarch64
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:47 -05:00
Fedora Kernel Team c3a9663501
[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-11-01 13:44:47 -05:00
Fedora Kernel Team c28e265b31
[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-11-01 13:44:47 -05:00
Chris von Recklinghausen a9e21a7736
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-11-01 13:44:47 -05:00
Hans de Goede 9ae4ac975e
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-11-01 13:44:47 -05:00
CKI Gitlab 1621ac0c6a
[redhat] New configs in drivers/scsi 2021-11-01 13:44:47 -05:00
Desnes A. Nunes do Rosario 3fdf9f2b42
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-11-01 13:44:47 -05:00
Peter Robinson b0657cbe05
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-11-01 13:44:46 -05:00
Diego Domingos d72cbaf07e
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-11-01 13:44:46 -05:00
Herbert Xu 51582d2669
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-11-01 13:44:46 -05:00
Herbert Xu cf22dfe2f7
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-11-01 13:44:46 -05:00
Kamal Heib 7269146ed3
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-11-01 13:44:46 -05:00
Justin M. Forbes 250cb2f029
update filters for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:46 -05:00
Prarit Bhargava ffff102706
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-11-01 13:44:46 -05:00
Justin M. Forbes ec0f787d6d
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-11-01 13:44:46 -05:00
Hans de Goede 70310d73f4
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-11-01 13:44:45 -05:00
Diego Domingos 98549b719e
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-11-01 13:44:45 -05:00
Eric Auger b614ad2765
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-11-01 13:44:45 -05:00
Prarit Bhargava d8a32f655d
RHMAINTAINERS: Update for Aug 6 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:44:45 -05:00
Fedora Kernel Team 50bd303c18
[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-11-01 13:44:45 -05:00
Jaroslav Kysela 96681873c3
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-11-01 13:44:45 -05:00
Jaroslav Kysela d6b6b9a049
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-11-01 13:44:45 -05:00
Fedora Kernel Team 47e1cff22f
[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-11-01 13:44:44 -05:00
CKI Gitlab ba89991aa3
[redhat] New configs in net/netfilter 2021-11-01 13:44:44 -05:00
Peter Robinson 168c34916b
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-11-01 13:44:44 -05:00
Herton R. Krzesinski 7095a89105
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-11-01 13:44:44 -05:00
Justin M. Forbes 6a5511af92
Remove fedora version of the LOCKDEP_BITS, we should use common
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:44 -05:00
Justin M. Forbes 3d4f920abc
Re-enable sermouse for x86 (rhbz 1974002)
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:44 -05:00
Justin M. Forbes 80da894ba0
Fedora 5.14 configs round 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:44 -05:00
Herton R. Krzesinski 78ee282860
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-11-01 13:44:43 -05:00
Vladis Dronov 7779a3298e
[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-11-01 13:44:43 -05:00
Vitaly Kuznetsov 5adeec38e4
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-11-01 13:44:43 -05:00
root 7e84a48857
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-11-01 13:44:43 -05:00
Jiri Benc 8bc1f08722
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-11-01 13:44:43 -05:00
Jerome Marchand 8177a8e827
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-11-01 13:44:43 -05:00
Herton R. Krzesinski 4eb32a9b06
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-11-01 13:44:43 -05:00
Fedora Kernel Team 6d2a7c564c
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:42 -05:00
Fedora Kernel Team bf87f868ee
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:42 -05:00
Patrick Talbert ec9c6f481e
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-11-01 13:44:42 -05:00
Peter Robinson 6b6bbe9226
fedora: sound config updates for 5.14
Some sound config updates for Fedora.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:44:42 -05:00
Peter Robinson 7d9bed5d82
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-11-01 13:44:42 -05:00
Peter Robinson 5b6e277789
The CONFIG_RAW_DRIVER has been removed from upstream
No functional change

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:44:42 -05:00
Peter Robinson 8fd43dbffd
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-11-01 13:44:41 -05:00
Peter Robinson 4cb3a90a96
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-11-01 13:44:41 -05:00
Peter Robinson 092d4e9321
fedora: Remove STAGING_GASKET_FRAMEWORK
It was removed from upstream staging so can be dropped.

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:44:41 -05:00
Peter Robinson bc99cc5c81
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-11-01 13:44:41 -05:00
Peter Robinson c114bb24d9
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-11-01 13:44:41 -05:00
Peter Robinson 2c12e461ff
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-11-01 13:44:41 -05:00
Waiman Long e8bdfd869a
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-11-01 13:44:41 -05:00
Herton R. Krzesinski 24e8a1c673
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-11-01 13:44:40 -05:00
Marius Hoch 67a08b6afa
Build Fedora x86s kernels with bytcr-wm5102 2021-11-01 13:44:40 -05:00
Patrick Lang d29916822a
Deleted redhat/configs/fedora/generic/x86/CONFIG_FB_HYPERV 2021-11-01 13:44:40 -05:00
Herton R. Krzesinski d570e81f19
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-11-01 13:44:40 -05:00
Herton R. Krzesinski 2e20ae18cf
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-11-01 13:44:40 -05:00
Patrick Talbert ede4219408
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-11-01 13:44:40 -05:00
Patrick Talbert 556125c5fd
[redhat] configs: Enable CONFIG_DRM_HYPERV as a module
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-11-01 13:44:40 -05:00
Fedora Kernel Team 8ff2bae9b7
[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-11-01 13:44:39 -05:00
Don Zickus 782013cb64
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-11-01 13:44:39 -05:00
Jan Stancek 585dfd6374
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-11-01 13:44:39 -05:00
Michael Petlan 28e1fac3b7
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-11-01 13:44:39 -05:00
Michael Petlan 2572765cc1
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-11-01 13:44:39 -05:00
Michael Petlan e09cd9b21a
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-11-01 13:44:39 -05:00
Fedora Kernel Team e245671218
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:39 -05:00
Ming Lei 36a1f1f414
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-11-01 13:44:38 -05:00
Fedora Kernel Team 78b53d5101
[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-11-01 13:44:38 -05:00
Tom Stellard 10a01b63f2
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-11-01 13:44:38 -05:00
Peter Robinson 607ee7a247
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-11-01 13:44:38 -05:00
Don Zickus bdf3d0d6a1
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-11-01 13:44:38 -05:00
Justin M. Forbes 4778bbcc0a
Fedor config update for new option
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:38 -05:00
Fedora Kernel Team 9328a23952
[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-11-01 13:44:37 -05:00
Fedora Kernel Team 33c89a9baa
[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-11-01 13:44:37 -05:00
Fedora Kernel Team 3752b9c049
[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-11-01 13:44:37 -05:00
Mark Salter 8b21e96f34
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-11-01 13:44:37 -05:00
Peter Robinson 666db5cad5
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-11-01 13:44:37 -05:00
Peter Robinson 7d55410bea
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-11-01 13:44:37 -05:00
Peter Robinson 5825c591b8
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-11-01 13:44:37 -05:00
Patrick Talbert 284a51b22d
Update CONFIG_ARM_FFA_TRANSPORT 2021-11-01 13:44:37 -05:00
Fedora Kernel Team 2da5abdc6e
[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-11-01 13:44:36 -05:00
Veronika Kabatova 592159987f
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-11-01 13:44:36 -05:00
Justin M. Forbes 7a8c4f7edb
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-11-01 13:44:36 -05:00
Mark Salter 0f51310d54
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-11-01 13:44:36 -05:00
Prarit Bhargava 97c7f12e69
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-11-01 13:44:36 -05:00
Peter Robinson ee7bc84b18
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-11-01 13:44:36 -05:00
Eric Auger 674e16a852
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-11-01 13:44:36 -05:00
Phil Auld a0a0366627
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-11-01 13:44:35 -05:00
Fedora Kernel Team 872d10aca7
[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-11-01 13:44:35 -05:00
Fedora Kernel Team e1b409b38b
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:35 -05:00
Fedora Kernel Team 0a550e03cd
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:35 -05:00
Fedora Kernel Team 2a4e05c593
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:35 -05:00
Fedora Kernel Team c39887285d
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:35 -05:00
Prarit Bhargava c89b67df93
RHMAINTAINERS: Update for Jul 8 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:44:35 -05:00
Coiby Xu 8fb855797f
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-11-01 13:44:34 -05:00
Fedora Kernel Team c26f33037b
[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-11-01 13:44:34 -05:00
Fedora Kernel Team d2fa66f68c
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:34 -05:00
Fedora Kernel Team 25af93f3e5
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:34 -05:00
Fedora Kernel Team 69845d2a9d
[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-11-01 13:44:34 -05:00
Herton R. Krzesinski ab98eaa771
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-11-01 13:44:34 -05:00
Bruno Meneguele 47120d7d32
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-11-01 13:44:34 -05:00
Čestmír Kalina eb3d0d06b9
[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-11-01 13:44:33 -05:00
Fedora Kernel Team 1c32714c37
[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-11-01 13:44:33 -05:00
Fedora Kernel Team 25a948a8f9
[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-11-01 13:44:33 -05:00
Bruno Meneguele 89447f29de
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-11-01 13:44:33 -05:00
Bruno Meneguele 8da3fce6ff
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-11-01 13:44:33 -05:00
Alaa Hleihel 54ef1ab866
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-11-01 13:44:33 -05:00
Kairui Song 2b2042470f
[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-11-01 13:44:33 -05:00
Fedora Kernel Team ac3bc4dc59
[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-11-01 13:44:32 -05:00
Fedora Kernel Team ef67d5c910
[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-11-01 13:44:32 -05:00
Fedora Kernel Team d11e41c1ee
[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-11-01 13:44:32 -05:00
Fedora Kernel Team 233da84e5e
[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-11-01 13:44:32 -05:00
Fedora Kernel Team c5254eaf00
[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-11-01 13:44:32 -05:00
Fedora Kernel Team aca4114ce4
[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-11-01 13:44:32 -05:00
Peter Robinson 9b0a9605b2
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-11-01 13:44:32 -05:00
Fedora Kernel Team 1e4ef6d4f6
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:31 -05:00
Fedora Kernel Team a609af3284
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:31 -05:00
Fedora Kernel Team 19c34cf07f
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:31 -05:00
Fedora Kernel Team cc10bf5a8f
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:31 -05:00
Tom Stellard ea06a642f4
[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-11-01 13:44:31 -05:00
Fedora Kernel Team 3eeed86d76
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:31 -05:00
Fedora Kernel Team 1a7f099f2a
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:31 -05:00
Fedora Kernel Team 5695caca05
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:30 -05:00
Fedora Kernel Team dd0a5a8874
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:30 -05:00
Justin M. Forbes 1e61265177
COMMON_CLK_STM32MP157_SCMI is bool and selects COMMON_CLK_SCMI
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:30 -05:00
Timothée Ravier 041c9fa1b0
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-11-01 13:44:30 -05:00
Fedora Kernel Team c7efdba987
[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-11-01 13:44:30 -05:00
Fedora Kernel Team e4f8643d7f
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:30 -05:00
Fedora Kernel Team 775a6b3f50
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:30 -05:00
Justin M. Forbes 7e93389215
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-11-01 13:44:29 -05:00
Justin M. Forbes 74ee01e407
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-11-01 13:44:29 -05:00
Justin M. Forbes e157d0262c
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-11-01 13:44:29 -05:00
Fedora Kernel Team 2eb3503ed2
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:29 -05:00
Fedora Kernel Team e31dc9d95b
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:29 -05:00
Peter Robinson 2846cb5c8f
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-11-01 13:44:29 -05:00
Justin M. Forbes 6055c396e3
Enable Landlock for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:29 -05:00
Justin M. Forbes 5f96706e12
Filter update for Fedora aarch64
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:28 -05:00
Fedora Kernel Team 3002452a2c
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:28 -05:00
Fedora Kernel Team dd3adab155
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:28 -05:00
Herton R. Krzesinski ac5169b70d
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-11-01 13:44:28 -05:00
Fedora Kernel Team 98c461331f
[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-11-01 13:44:28 -05:00
Herton R. Krzesinski 6988b1034d
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-11-01 13:44:28 -05:00
Thomas Huth 6793314d6e
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-11-01 13:44:28 -05:00
Thomas Huth 12bf86e6e4
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-11-01 13:44:27 -05:00
Thomas Huth cef603ba88
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-11-01 13:44:27 -05:00
Thomas Huth 326c1c2207
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-11-01 13:44:27 -05:00
Thomas Huth 450f819585
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-11-01 13:44:27 -05:00
Thomas Huth 138ed8b942
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-11-01 13:44:27 -05:00
Thomas Huth 03f611c638
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-11-01 13:44:27 -05:00
CKI Gitlab bfdf2eb38b
[redhat] New configs in arch/arm64 2021-11-01 13:44:27 -05:00
Fedora Kernel Team b572aa54d6
[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-11-01 13:44:26 -05:00
Vladis Dronov ad1ae4c91d
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-11-01 13:44:26 -05:00
Fedora Kernel Team b62bab8662
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:26 -05:00
Fedora Kernel Team e610f4cb37
[redhat] AUTOMATIC: New configs 2021-11-01 13:44:26 -05:00
Justin M. Forbes 7f334332fe
Fix typos in fedora filters
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:26 -05:00
Justin M. Forbes 0848334ab5
More filtering for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:26 -05:00
Justin M. Forbes 7ca0e1cf2c
Fix Fedora module filtering for spi-altera-dfl
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:26 -05:00
Justin M. Forbes b10ce2aff7
Fedora 5.13 config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:25 -05:00
Peter Robinson 27016de281
fedora: cleanup TCG_TIS_I2C_CR50
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:44:25 -05:00
Peter Robinson f6f396ca5b
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-11-01 13:44:25 -05:00
Justin M. Forbes cb5ef3902a
More Fedora config updates for 5.13
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:25 -05:00
Alaa Hleihel 73eeb3264b
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-11-01 13:44:25 -05:00
Prarit Bhargava 4df61293ac
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-11-01 13:44:25 -05:00
Marcelo Ricardo Leitner 465f192981
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-11-01 13:44:25 -05:00
Tom Stellard d9759307b6
[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-11-01 13:44:24 -05:00
Patrick Talbert 455c5d5ebd
[redhat] configs: Add a generic facility for providing custom config options
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-11-01 13:44:24 -05:00
Jiri Olsa 5cda3e0c67
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-11-01 13:44:24 -05:00
Don Zickus 2b82bdffb8
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-11-01 13:44:24 -05:00
Jiri Olsa b74e927977
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-11-01 13:44:24 -05:00
Fedora Kernel Team 7e3a2d610f
[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-11-01 13:44:24 -05:00
Justin M. Forbes bb6191bc49
Turn off DRM_XEN_FRONTEND for Fedora as we had DRM_XEN off already
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:24 -05:00
Fedora Kernel Team 3d74634a22
[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-11-01 13:44:23 -05:00
Fedora Kernel Team 4e6915b1b4
[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-11-01 13:44:23 -05:00
Fedora Kernel Team d696f4c722
[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-11-01 13:44:23 -05:00
Fedora Kernel Team 3dac765dce
[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-11-01 13:44:23 -05:00
Fedora Kernel Team f9f8d55639
[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-11-01 13:44:23 -05:00
Fedora Kernel Team 635ec4d1a8
[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-11-01 13:44:23 -05:00
Fedora Kernel Team f5c71ee590
[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-11-01 13:44:23 -05:00
Justin M. Forbes ec1a40f738
Fedora 5.13 config updates pt 3
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:22 -05:00
Fedora Kernel Team 9eabf963e7
[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-11-01 13:44:22 -05:00
Peter Robinson 2e34e88c59
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-11-01 13:44:22 -05:00
Peter Robinson 86f91472f8
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-11-01 13:44:22 -05:00
Jiri Olsa 4625397e65
spec: Enable sefltests rpm build
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-11-01 13:44:22 -05:00
Jiri Olsa e074497e16
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-11-01 13:44:22 -05:00
Jiri Benc 251a25af56
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-11-01 13:44:22 -05:00
Jiri Benc 6530e820ae
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-11-01 13:44:21 -05:00
Jiri Benc f564062cbe
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-11-01 13:44:21 -05:00
Jiri Benc d88c43a6c8
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-11-01 13:44:21 -05:00
Jiri Benc 2b15415f39
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-11-01 13:44:21 -05:00
Jiri Benc 56561cddbe
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-11-01 13:44:21 -05:00
Jiri Benc 1d61d4e8fd
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-11-01 13:44:21 -05:00
Jiri Benc 20988053fa
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-11-01 13:44:21 -05:00
Jiri Benc 7cadd33886
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-11-01 13:44:20 -05:00
Jiri Benc 3237d54836
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-11-01 13:44:20 -05:00
Jiri Benc e4cc6d8bef
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-11-01 13:44:20 -05:00
Jiri Benc 7ec730234e
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-11-01 13:44:20 -05:00
Jiri Benc 527ecb7f29
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-11-01 13:44:20 -05:00
Jiri Benc dcbee5c9e0
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-11-01 13:44:20 -05:00
Jiri Benc ba5862a898
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-11-01 13:44:20 -05:00
Jiri Benc 21bd013bae
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-11-01 13:44:20 -05:00
Jiri Benc 11f53a4ef2
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-11-01 13:44:19 -05:00
Jiri Benc d0afe83ce0
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-11-01 13:44:19 -05:00
Jiri Benc ec4ab9d794
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-11-01 13:44:19 -05:00
Jiri Benc c9a1a04fc9
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-11-01 13:44:19 -05:00
Jiri Benc baed5bf6d7
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-11-01 13:44:19 -05:00
Jiri Benc 49c0826729
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-11-01 13:44:19 -05:00
Jiri Benc 15aa25f29a
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-11-01 13:44:19 -05:00
Jiri Benc 9bc8425dca
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-11-01 13:44:19 -05:00
Jiri Benc 3f30bc4717
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-11-01 13:44:18 -05:00
Jiri Benc 798328c6d0
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-11-01 13:44:18 -05:00
Jiri Benc 391af1a0c7
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-11-01 13:44:18 -05:00
Jiri Benc df8fa7fa1f
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-11-01 13:44:18 -05:00
Phil Sutter 09bb5bb0ee
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-11-01 13:44:18 -05:00
Phil Sutter 975e93384f
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-11-01 13:44:18 -05:00
Justin M. Forbes 4780d38b2b
Fedora 5.13 config updates pt 2
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:17 -05:00
Fedora Kernel Team f7caed47ce
[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-11-01 13:44:17 -05:00
Justin M. Forbes 457853f577
Move CONFIG_ARCH_INTEL_SOCFPGA up a level for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:17 -05:00
Peter Robinson 57ca85d03d
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-11-01 13:44:17 -05:00
Justin M. Forbes 88ba4cc77e
Fedora 5.13 config updates pt 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:44:17 -05:00
Justin M. Forbes a6f5bd990e
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-11-01 13:44:17 -05:00
Philipp Rudo 364fbc92e1
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-11-01 13:44:17 -05:00
Philipp Rudo ecb6e61e74
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-11-01 13:44:16 -05:00
Philipp Rudo 9edffefe4f
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-11-01 13:44:16 -05:00
Philipp Rudo f7916e77a0
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-11-01 13:44:16 -05:00
Philipp Rudo 5af44cdaec
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-11-01 13:44:16 -05:00
Mark Salter f4cc76c69a
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-11-01 13:44:16 -05:00
Mark Salter e48d5092c7
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-11-01 13:44:16 -05:00
Fedora Kernel Team 3f20e289df
[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-11-01 13:44:16 -05:00
Bruno Meneguele c1ab12fcd8
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-11-01 13:44:15 -05:00
Bruno Meneguele e03611e529
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-11-01 13:44:15 -05:00
Prarit Bhargava be4705ab4d
RHMAINTAINERS: Update for June 11 2021
Update RHMAINTAINERS.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:44:15 -05:00
Benjamin Tissoires 8e83ad889b
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-11-01 13:44:15 -05:00
Fedora Kernel Team ad62ef4c34
[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-11-01 13:44:15 -05:00
Fedora Kernel Team aa3ec46d38
[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-11-01 13:44:15 -05:00
Michael Petlan c7d025404d
[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-11-01 13:44:15 -05:00
Fedora Kernel Team d1c37c941c
[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-11-01 13:44:14 -05:00
Fedora Kernel Team f5dc6263dd
[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-11-01 13:44:14 -05:00
Jeff Moyer 2d123caf19
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-11-01 13:44:14 -05:00
CKI Gitlab 9a9f9caf93
[redhat] New configs in drivers/hwtracing 2021-11-01 13:44:14 -05:00
CKI Gitlab 7ea51a7b55
[redhat] New configs in drivers/hid 2021-11-01 13:44:14 -05:00
Frank Ramsay 0b1df86646
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-11-01 13:44:14 -05:00
Fedora Kernel Team 47e592a9b1
[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-11-01 13:44:14 -05:00
Vitaly Kuznetsov d2d75bff87
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-11-01 13:44:13 -05:00
David Ward c058165b9d
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-11-01 13:44:13 -05:00
Eric Auger 1e4a9e0fbd
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-11-01 13:44:13 -05:00
Jiri Olsa ce8aabe528
Enable CONFIG_BPF_UNPRIV_DEFAULT_OFF
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
2021-11-01 13:42:16 -05:00
Fedora Kernel Team 0667d2a0da
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:16 -05:00
Fedora Kernel Team b482640b51
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:16 -05:00
Thomas Huth 72e5450189
[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-11-01 13:42:16 -05:00
Philipp Rudo 34a9cac568
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-11-01 13:42:16 -05:00
Antoine Tenart 4fdef83755
[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-11-01 13:42:16 -05:00
Vladis Dronov 71542aa4f3
[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-11-01 13:42:15 -05:00
Mike Snitzer 00a022572b
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-11-01 13:42:15 -05:00
Fedora Kernel Team 1df9c05416
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:15 -05:00
Fedora Kernel Team ef320a0cc4
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:15 -05:00
Michael Petlan 3db0654736
[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-11-01 13:42:15 -05:00
Simo Sorce a551e91d5a
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-11-01 13:42:15 -05:00
David Ward 84036ad06e
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-11-01 13:42:14 -05:00
David Ward ed70981889
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-11-01 13:42:14 -05:00
David Ward c2af02f84a
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-11-01 13:42:14 -05:00
Pavel Reichl 2f5af825b2
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-11-01 13:42:14 -05:00
Vladis Dronov e66e77dfbf
Revert s390x/zfcpdump part of a9d179c40281 and ecbfddd98621
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
2021-11-01 13:42:14 -05:00
Vladis Dronov 48572397eb
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-11-01 13:42:14 -05:00
Mohammed Gamal 8342b6b0c5
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-11-01 13:42:14 -05:00
David Hildenbrand 79de70352c
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-11-01 13:42:13 -05:00
Herton R. Krzesinski 086786a74f
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-11-01 13:42:13 -05:00
Aristeu Rozanski c98157bef5
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-11-01 13:42:13 -05:00
Michael Petlan eb93f1180e
[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-11-01 13:42:13 -05:00
Hans de Goede 5e81a5adcb
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-11-01 13:42:13 -05:00
CKI Gitlab c4e13a842e
[redhat] New configs in drivers/gpu 2021-11-01 13:42:13 -05:00
Mike Snitzer fdf1d90509
[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-11-01 13:42:13 -05:00
Herton R. Krzesinski 824cf98a3c
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-11-01 13:42:12 -05:00
Herton R. Krzesinski 9579c84abd
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-11-01 13:42:12 -05:00
Damien Le Moal 1d3b619e95
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-11-01 13:42:12 -05:00
CKI Gitlab 35542e458f
[redhat] New configs in fs/netfs 2021-11-01 13:42:12 -05:00
Bruno Meneguele 22c5614958
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-11-01 13:42:12 -05:00
Bruno Meneguele 405f38c1b5
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-11-01 13:42:12 -05:00
Bruno Meneguele 700ac85278
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-11-01 13:42:12 -05:00
Bruno Meneguele 8bf3b5389e
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-11-01 13:42:11 -05:00
Tom Stellard 5091ad6c35
[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-11-01 13:42:11 -05:00
Fedora Kernel Team 4f565a4517
[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-11-01 13:42:11 -05:00
Phil Sutter d28bca759c
[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-11-01 13:42:11 -05:00
David Ward 79722f9623
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-11-01 13:42:11 -05:00
Alaa Hleihel e0e9150541
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-11-01 13:42:11 -05:00
Fedora Kernel Team aa69f96cfd
[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-11-01 13:42:10 -05:00
Justin M. Forbes 29593a3378
Force DWARF4 because crash does not support DWARF5 yet
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:42:10 -05:00
Fedora Kernel Team 3a701aeaf6
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:10 -05:00
Fedora Kernel Team 5afb7494ec
[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-11-01 13:42:10 -05:00
Fedora Kernel Team 0cb7523197
[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-11-01 13:42:10 -05:00
Peter Robinson 1bdd38205e
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-11-01 13:42:10 -05:00
Fedora Kernel Team 69a26ddaae
[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-11-01 13:42:09 -05:00
Michael Petlan 146c6b81fd
[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-11-01 13:42:09 -05:00
Peter Robinson ed23249e69
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-11-01 13:42:09 -05:00
Peter Robinson 5eef825d7d
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-11-01 13:42:09 -05:00
Justin M. Forbes fc4bb0801d
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-11-01 13:42:09 -05:00
Herton R. Krzesinski b185f847a7
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-11-01 13:42:09 -05:00
Fedora Kernel Team 23295c98b3
[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-11-01 13:42:09 -05:00
Fedora Kernel Team 830386face
[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-11-01 13:42:08 -05:00
Fedora Kernel Team 5b2a52f330
[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-11-01 13:42:08 -05:00
Fedora Kernel Team 10160ae161
[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-11-01 13:42:08 -05:00
Fedora Kernel Team 882157993a
[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-11-01 13:42:08 -05:00
Fedora Kernel Team b4c1b1f940
[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-11-01 13:42:08 -05:00
Peter Robinson d875e02c8a
fedora: arm updates for 5.13
Initial updates for the 5.13 window

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:42:08 -05:00
Peter Robinson 284ba23950
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-11-01 13:42:07 -05:00
Justin Forbes dcea4cd254
Update CONFIG_MODPROBE_PATH to /usr/sbin
Technically both paths exist, but /sbin is a link to /usr/sbin
2021-11-01 13:42:07 -05:00
Fedora Kernel Team b593beb941
[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-11-01 13:42:07 -05:00
Justin M. Forbes 9e1e96037c
Fedora set modprobe path
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:42:07 -05:00
Fedora Kernel Team d3bf8f834a
[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-11-01 13:42:07 -05:00
Fedora Kernel Team a4b2589246
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:07 -05:00
Fedora Kernel Team 0fa01bf50c
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:06 -05:00
Don Zickus f35b8056f5
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-11-01 13:42:06 -05:00
Don Zickus 4e32876b4d
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-11-01 13:42:06 -05:00
Hans de Goede b776e11e97
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-11-01 13:42:06 -05:00
Fedora Kernel Team a49d30d2bd
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:06 -05:00
Fedora Kernel Team 992b206440
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:06 -05:00
CKI Gitlab fd040dcb89
[redhat] New configs in drivers/cxl 2021-11-01 13:42:06 -05:00
Fedora Kernel Team 3346cf7a71
[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-11-01 13:42:05 -05:00
Fedora Kernel Team 34d97ac728
[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-11-01 13:42:05 -05:00
Justin M. Forbes 0a4fffa314
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-11-01 13:42:05 -05:00
Fedora Kernel Team 5259df2d61
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-11-01 13:42:05 -05:00
David Gibson e618762eb2
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-11-01 13:42:05 -05:00
Michael Petlan 47ac5ecd43
[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-11-01 13:42:05 -05:00
Fedora Kernel Team 8aa4c3a267
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:05 -05:00
Fedora Kernel Team 6d156d6720
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:05 -05:00
Justin M. Forbes 40ae7035f5
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-11-01 13:42:04 -05:00
Justin M. Forbes 89d92b4520
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-11-01 13:42:04 -05:00
Justin M. Forbes ece79d87dc
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-11-01 13:42:04 -05:00
Fedora Kernel Team b64a280940
[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-11-01 13:42:04 -05:00
Justin M. Forbes d79fa67a54
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-11-01 13:42:04 -05:00
Justin M. Forbes e5433056fb
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-11-01 13:42:04 -05:00
Justin M. Forbes a6d372c91a
Update pending-common configs, preparing to set correctly
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:42:03 -05:00
Justin M. Forbes b8a6edb9e9
Update fedora filters for surface
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:42:03 -05:00
Justin M. Forbes 77b47a18a5
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-11-01 13:42:03 -05:00
Fedora Kernel Team 03d5700eb8
[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-11-01 13:42:03 -05:00
Fedora Kernel Team 2cf2210444
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:03 -05:00
Fedora Kernel Team 8340cdb7bf
[redhat] AUTOMATIC: New configs 2021-11-01 13:42:03 -05:00
David Ward 01018dd559
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-11-01 13:42:03 -05:00
David Ward eed1302f84
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-11-01 13:42:02 -05:00
David Ward 6d9af91b6e
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-11-01 13:42:02 -05:00
David Ward 5845f37bec
Change description of --without-vdso-install to fix typo
Signed-off-by: David Ward <david.ward@ll.mit.edu>
2021-11-01 13:42:02 -05:00
Fedora Kernel Team f84e33512e
[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-11-01 13:42:02 -05:00
Justin M. Forbes 8f39abbef7
Config updates to work around mismatches
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:42:02 -05:00
Justin M. Forbes 6331713737
CONFIG_SND_SOC_FSL_ASOC_CARD selects CONFIG_MFD_WM8994 now
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:42:02 -05:00
Hangbin Liu 89e7c979ad
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-11-01 13:42:02 -05:00
Fedora Kernel Team c6cbd82381
[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-11-01 13:42:01 -05:00
Justin M. Forbes c3cd86bc2e
Enable mtdram for fedora (rhbz 1955916)
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:42:01 -05:00
Fedora Kernel Team 869dfbef25
[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-11-01 13:42:01 -05:00
Fedora Kernel Team bdcaf4ca90
[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-11-01 13:42:01 -05:00
Vladis Dronov 2c0d26b3bc
[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-11-01 13:42:01 -05:00
Fedora Kernel Team f824102595
[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-11-01 13:42:01 -05:00
Fedora Kernel Team 6fd8854efb
[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-11-01 13:42:01 -05:00
Fedora Kernel Team 3cae3758ac
[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-11-01 13:42:00 -05:00
Fedora Kernel Team a19f0984da
[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-11-01 13:42:00 -05:00
Justin M. Forbes 20d96a0e2d
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-11-01 13:42:00 -05:00
Fedora Kernel Team 53bcca7259
[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-11-01 13:42:00 -05:00
Fedora Kernel Team 23e607810d
[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-11-01 13:42:00 -05:00
Fedora Kernel Team 34d7e57cfd
[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-11-01 13:42:00 -05:00
CKI Gitlab 1a04aa369a
[redhat] New configs in arch/x86 2021-11-01 13:42:00 -05:00
Prarit Bhargava b3ab561bb0
RHMAINTAINERS: Update for Apr 30 2021
Update RHMAINTAINERS.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:41:59 -05:00
Dave Olsthoorn 2f3879e9c4
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-11-01 13:41:59 -05:00
Fedora Kernel Team 4a6a3dd996
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:59 -05:00
Fedora Kernel Team 8e88a46921
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:59 -05:00
Fedora Kernel Team e13f9385ce
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:59 -05:00
Fedora Kernel Team 5c78386f39
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:59 -05:00
Justin M. Forbes 25ad5b298d
Fix Fedora config mismatch for CONFIG_FSL_ENETC_IERB
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:59 -05:00
Fedora Kernel Team 6749cce535
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:58 -05:00
Fedora Kernel Team 95037e5974
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:58 -05:00
Justin M. Forbes 2a43173795
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-11-01 13:41:58 -05:00
Justin M. Forbes 8800b61a6a
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-11-01 13:41:58 -05:00
Fedora Kernel Team 5fbd28eeea
[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-11-01 13:41:58 -05:00
Fedora Kernel Team 1d0017d821
[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-11-01 13:41:58 -05:00
Fedora Kernel Team 167615a61e
[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-11-01 13:41:57 -05:00
Fedora Kernel Team 1649e65eda
[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-11-01 13:41:57 -05:00
David Ward b18a03dcaf
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-11-01 13:41:57 -05:00
David Ward 05d3355ca3
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-11-01 13:41:57 -05:00
Don Zickus 319482cac2
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-11-01 13:41:57 -05:00
Fedora Kernel Team 5742eb539c
[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-11-01 13:41:57 -05:00
Fedora Kernel Team 3679a365ec
[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-11-01 13:41:57 -05:00
Fedora Kernel Team 8c5e7a772e
[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-11-01 13:41:56 -05:00
Fedora Kernel Team a063aa4482
[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-11-01 13:41:56 -05:00
Fedora Kernel Team eaa3e0fda7
[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-11-01 13:41:56 -05:00
Mike Snitzer d8a00d60a5
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-11-01 13:41:56 -05:00
Mike Snitzer f904b60b4c
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-11-01 13:41:56 -05:00
Mike Snitzer c0e1a06b73
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-11-01 13:41:56 -05:00
Justin M. Forbes e4afef29df
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-11-01 13:41:56 -05:00
Fedora Kernel Team 36c12ab708
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:56 -05:00
Fedora Kernel Team a420660ead
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:55 -05:00
Don Zickus 4672ff8862
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-11-01 13:41:55 -05:00
David Ward 71989e79ef
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-11-01 13:41:55 -05:00
Fedora Kernel Team fca124d156
[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-11-01 13:41:55 -05:00
Dave Airlie e4f7c38ac3
[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-11-01 13:41:55 -05:00
Fedora Kernel Team 536be110e0
[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-11-01 13:41:55 -05:00
Justin M. Forbes 25eb5d81fc
Turn off ADI_AXI_ADC and AD9467 which now require CONFIG_OF
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:54 -05:00
Patrick Talbert 4e5f1b1fa2
[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-11-01 13:41:54 -05:00
Don Zickus ece886dc03
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-11-01 13:41:54 -05:00
Jeremy Cline c9fa4c9398
[redhat] New configs in drivers/virtio 2021-11-01 13:41:54 -05:00
Jeremy Cline e9591e25ad
[redhat] New configs in drivers/gpu 2021-11-01 13:41:54 -05:00
Don Zickus 3f2c5a6a16
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-11-01 13:41:54 -05:00
Don Zickus 59f16360ca
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-11-01 13:41:54 -05:00
Hans de Goede 94f435985c
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-11-01 13:41:53 -05:00
Paul Bolle 0ae5199335
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-11-01 13:41:53 -05:00
Paul Bolle cf5fcda598
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-11-01 13:41:53 -05:00
Paul Bolle 9cf29f297a
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-11-01 13:41:53 -05:00
Paul Bolle c78181c202
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-11-01 13:41:53 -05:00
Paul Bolle 3f1da738c4
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-11-01 13:41:53 -05:00
Paul Bolle 525955111c
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-11-01 13:41:53 -05:00
Paul Bolle c361f90ad6
filter-modules.sh.fedora: drop unused list "iiodrvs"
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
2021-11-01 13:41:52 -05:00
Fedora Kernel Team 19d33c46d2
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:52 -05:00
Prarit Bhargava 6a421c9696
RHMAINTAINERS: Update Apr 15 2021
Update RHMAINTAINERS to latest.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:41:52 -05:00
Nico Pache 719e07ae16
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-11-01 13:41:52 -05:00
Tom Stellard ca68dc8973
[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-11-01 13:41:52 -05:00
Fedora Kernel Team 85ece6fd94
[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-11-01 13:41:52 -05:00
Jeremy Cline 81c671fddd
[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-11-01 13:41:52 -05:00
Jeremy Cline e7a7f90052
[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-11-01 13:41:51 -05:00
Justin Forbes a12c92cecd
[redhat] New configs in drivers/vdpa 2021-11-01 13:41:51 -05:00
Vladis Dronov 06e62ee5ba
[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-11-01 13:41:51 -05:00
Justin M. Forbes bf8f168f5f
Turn on CONFIG_VDPA_SIM_NET (rhbz 1942343)
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:51 -05:00
Fedora Kernel Team 2514b8055e
[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-11-01 13:41:51 -05:00
Fedora Kernel Team 634f2016ef
[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-11-01 13:41:51 -05:00
Fedora Kernel Team c54269ba77
[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-11-01 13:41:50 -05:00
Fedora Kernel Team 44ec240ed0
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-11-01 13:41:50 -05:00
Fedora Kernel Team 058cb99d37
[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-11-01 13:41:50 -05:00
Justin M. Forbes e71ef3b63d
Turn on CONFIG_NOUVEAU_DEBUG_PUSH for debug configs
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:50 -05:00
Fedora Kernel Team 26a12f9e95
[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-11-01 13:41:50 -05:00
Fedora Kernel Team 1861c603c5
[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-11-01 13:41:50 -05:00
Fedora Kernel Team 34798e0068
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:50 -05:00
Justin M. Forbes 2d98ae56a2
Turn off KFENCE sampling by default for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:49 -05:00
Justin M. Forbes 71a07c26fa
Fedora config updates round 2
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:49 -05:00
Jeremy Cline 3cfd0cb627
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-11-01 13:41:49 -05:00
Fedora Kernel Team 68f63421f6
[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-11-01 13:41:49 -05:00
Fedora Kernel Team 79d7933939
[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-11-01 13:41:49 -05:00
Paul Bolle 7da6651c77
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-11-01 13:41:49 -05:00
Justin M. Forbes 5122720c17
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-11-01 13:41:49 -05:00
Fedora Kernel Team 9266337b47
[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-11-01 13:41:48 -05:00
Fedora Kernel Team 30836833da
[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-11-01 13:41:48 -05:00
Fedora Kernel Team bea093ae09
[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-11-01 13:41:48 -05:00
Fedora Kernel Team aa8faefc81
[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-11-01 13:41:48 -05:00
Fedora Kernel Team 7f7efe9057
[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-11-01 13:41:48 -05:00
Mark Mielke 6ee826aa7e
Fix genlog.py to ensure that comments retain "%" characters. 2021-11-01 13:41:48 -05:00
Patrick Talbert a57cfe9ace
[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-11-01 13:41:48 -05:00
Fedora Kernel Team d0ce766ff1
[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-11-01 13:41:47 -05:00
Fedora Kernel Team 1f50428c60
[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-11-01 13:41:47 -05:00
Fedora Kernel Team a5f7317cda
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-11-01 13:41:47 -05:00
David Ward f2716235c4
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-11-01 13:41:47 -05:00
Fedora Kernel Team 9bffd3b4bb
[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-11-01 13:41:47 -05:00
Fedora Kernel Team ec9800d1f7
[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-11-01 13:41:47 -05:00
Fedora Kernel Team f710049676
[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-11-01 13:41:47 -05:00
Peter Robinson 371b837d4a
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-11-01 13:41:46 -05:00
Fedora Kernel Team f48d6e8137
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:46 -05:00
Justin M. Forbes ddde9adc0c
Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:46 -05:00
Don Zickus ae65bab562
[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-11-01 13:41:46 -05:00
Hangbin Liu d973a8fc7d
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-11-01 13:41:46 -05:00
Hangbin Liu 61482a98d8
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-11-01 13:41:46 -05:00
Don Zickus f65f412767
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-11-01 13:41:45 -05:00
Don Zickus a700f18570
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-11-01 13:41:45 -05:00
Peter Robinson 3b445a6025
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-11-01 13:41:45 -05:00
Jerry Snitselaar 6e88a4607b
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-11-01 13:41:45 -05:00
Jeremy Linton 94a3927f95
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-11-01 13:41:45 -05:00
CKI@GitLab 9a38669e84
[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-11-01 13:41:45 -05:00
Fedora Kernel Team 8f794c1e39
[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-11-01 13:41:45 -05:00
Rafael Aquini ed0973d036
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-11-01 13:41:44 -05:00
Justin M. Forbes 430b468ab7
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-11-01 13:41:44 -05:00
Fedora Kernel Team 175f0dbe8c
[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-11-01 13:41:44 -05:00
Fedora Kernel Team b683c90b43
[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-11-01 13:41:44 -05:00
Fedora Kernel Team ef38d9a353
[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-11-01 13:41:44 -05:00
Hans de Goede 802726d4d1
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-11-01 13:41:44 -05:00
Fedora Kernel Team 89970c293a
[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-11-01 13:41:43 -05:00
Fedora Kernel Team a3a8192592
[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-11-01 13:41:43 -05:00
Patrick Talbert 7ff1f5ca9c
[redhat] configs: Enable CONFIG_DEBUG_IRQFLAGS for debug builds.
Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-11-01 13:41:43 -05:00
Fedora Kernel Team 98d3cc3bb0
[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-11-01 13:41:43 -05:00
Fedora Kernel Team 10c9b384f7
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:43 -05:00
Fedora Kernel Team 43532ceae5
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:43 -05:00
Fedora Kernel Team 49571b86c4
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:43 -05:00
CKI@GitLab 17970f5b5e
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-11-01 13:41:42 -05:00
Fedora Kernel Team 029f600c8c
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-11-01 13:41:42 -05:00
Ondrej Mosnacek 94b3baa511
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-11-01 13:41:42 -05:00
Ondrej Mosnacek c821e6f910
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-11-01 13:41:42 -05:00
Vladis Dronov dfdced8e85
[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-11-01 13:41:42 -05:00
Fedora Kernel Team 02e4be6e3f
[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-11-01 13:41:42 -05:00
CKI@GitLab 42fde748ab
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-11-01 13:41:42 -05:00
CKI@GitLab d221e4c719
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-11-01 13:41:41 -05:00
Jeremy Cline c0b459bed0
[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-11-01 13:41:41 -05:00
Fedora Kernel Team c21b3a91c9
[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-11-01 13:41:41 -05:00
Fedora Kernel Team 0c86185582
[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-11-01 13:41:41 -05:00
Ben Crocker 40c096dea6
[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-11-01 13:41:41 -05:00
CKI Gitlab df1fc5ec47
[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-11-01 13:41:41 -05:00
Fedora Kernel Team 304e19c742
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-11-01 13:41:41 -05:00
Justin M. Forbes 2ec98c1c67
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-11-01 13:41:40 -05:00
Fedora Kernel Team 0089225569
[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-11-01 13:41:40 -05:00
Vladis Dronov ab1eb7a97b
[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-11-01 13:41:40 -05:00
Augusto Caringi d407eee3d8
Update CONFIG_DM_MULTIPATH_IOA 2021-11-01 13:41:40 -05:00
Fedora Kernel Team 20a059bbfe
[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-11-01 13:41:40 -05:00
CKI@GitLab 64489de6b5
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-11-01 13:41:40 -05:00
Jeremy Cline 7cb186d8a6
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-11-01 13:41:39 -05:00
Jeremy Cline 13646242d4
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-11-01 13:41:39 -05:00
Fedora Kernel Team 96ad8a17ae
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-11-01 13:41:39 -05:00
Justin M. Forbes 4cd1ff57e8
[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-11-01 13:41:39 -05:00
Justin M. Forbes 337d3a4f7d
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-11-01 13:41:39 -05:00
Fedora Kernel Team fe24a2102d
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-11-01 13:41:39 -05:00
Jeremy Cline 34b3c81b4d
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-11-01 13:41:38 -05:00
CKI Gitlab 57acf90647
[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-11-01 13:41:38 -05:00
Tom Stellard b9f34bf761
[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-11-01 13:41:38 -05:00
Fedora Kernel Team be278579b4
[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-11-01 13:41:38 -05:00
Herton R. Krzesinski 2b366dc3c6
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-11-01 13:41:38 -05:00
Peter Robinson 333a5206a3
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-11-01 13:41:38 -05:00
Peter Robinson 6f97afc385
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-11-01 13:41:38 -05:00
Peter Robinson 07ca88eb7d
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-11-01 13:41:37 -05:00
Paulo E. Castro 6b19d547d4
Correct kernel-devel make prepare build for 5.12.
Add requirements without which `prepare` won't work.
2021-11-01 13:41:37 -05:00
Herton R. Krzesinski 6bd66b062a
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-11-01 13:41:37 -05:00
Josh Poimboeuf 59db233670
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-11-01 13:41:37 -05:00
Justin M. Forbes 8670cfc261
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-11-01 13:41:37 -05:00
Justin M. Forbes 96d9e6e657
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-11-01 13:41:37 -05:00
Prarit Bhargava d36d6d936b
RHMAINTAINERS: update for March 15 2021
Update RHMAINTAINERS.

v2: Update jforbes address

Signed-off-by: Prarit Bhargava <prarit@redhat.com>
2021-11-01 13:41:36 -05:00
Herton R. Krzesinski 298639032e
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-11-01 13:41:36 -05:00
Peter Robinson f7d0320593
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-11-01 13:41:36 -05:00
Peter Robinson 1b111dffab
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-11-01 13:41:36 -05:00
Fedora Kernel Team 872a655227
[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-11-01 13:41:36 -05:00
Patrick Talbert 2ad47b9460
[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-11-01 13:41:36 -05:00
Jeremy Linton 6bcb58aace
[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-11-01 13:41:36 -05:00
Jeremy Linton 42d64b6c2d
[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-11-01 13:41:35 -05:00
Jeremy Linton 68800e597a
[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-11-01 13:41:35 -05:00
Jeremy Linton 0dc270bf04
[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-11-01 13:41:35 -05:00
Jeremy Linton f739049f5a
[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-11-01 13:41:35 -05:00
Jeremy Linton d91de63820
[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-11-01 13:41:35 -05:00
Jeremy Linton 37f100b475
[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-11-01 13:41:35 -05:00
Jeremy Linton 0b8742bdd5
[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-11-01 13:41:35 -05:00
Jeremy Linton 87459565e7
[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-11-01 13:41:34 -05:00
Jeremy Linton 81c61e18a5
[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-11-01 13:41:34 -05:00
Prarit Bhargava 9a6ce08927
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-11-01 13:41:34 -05:00
Peter Robinson 79baf808eb
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-11-01 13:41:34 -05:00
Peter Robinson 292a8b77e0
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-11-01 13:41:34 -05:00
Peter Robinson e716de4e53
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-11-01 13:41:34 -05:00
Peter Robinson d3389bf84b
fedora: the PCH_CAN driver is x86-32 only
No functional change

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:33 -05:00
Peter Robinson c551f4aed1
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-11-01 13:41:33 -05:00
Peter Robinson d6fa17bb47
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-11-01 13:41:33 -05:00
Peter Robinson 728017f024
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-11-01 13:41:33 -05:00
Peter Robinson 111911fc28
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-11-01 13:41:33 -05:00
Peter Robinson 77e89d82b8
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-11-01 13:41:33 -05:00
Peter Robinson 1350eca1d1
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-11-01 13:41:33 -05:00
Peter Robinson 486c4336d1
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-11-01 13:41:32 -05:00
Hans de Goede 8f9d656411
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-11-01 13:41:32 -05:00
Dave Olsthoorn 6db090d221
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-11-01 13:41:32 -05:00
Justin M. Forbes dd1861a86f
Turn on SND_SOC_INTEL_SOUNDWIRE_SOF_MACH for Fedora again
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:32 -05:00
Peter Robinson c8d2704235
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-11-01 13:41:32 -05:00
Fedora Kernel Team 6114f23cbd
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:32 -05:00
Fedora Kernel Team a808a2c430
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:32 -05:00
Peter Robinson 701f483e91
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-11-01 13:41:31 -05:00
Peter Robinson ad52f8939e
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-11-01 13:41:31 -05:00
Peter Robinson e19f47fdbf
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-11-01 13:41:31 -05:00
Peter Robinson ff438ad1b0
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-11-01 13:41:31 -05:00
Peter Robinson c47fb6042c
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-11-01 13:41:31 -05:00
Peter Robinson b687865914
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-11-01 13:41:31 -05:00
Peter Robinson ae87fce9b6
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-11-01 13:41:30 -05:00
Peter Robinson e8d029ddd9
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-11-01 13:41:30 -05:00
Peter Robinson 118f7ec666
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-11-01 13:41:30 -05:00
Peter Robinson afffc1a551
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-11-01 13:41:30 -05:00
Peter Robinson 4d2afead4e
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-11-01 13:41:30 -05:00
Vladis Dronov 89a95c7f9b
[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-11-01 13:41:30 -05:00
Fedora Kernel Team 89e1c83359
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:30 -05:00
Fedora Kernel Team 8a9a97b88f
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:29 -05:00
Vladis Dronov 3807f56789
[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-11-01 13:41:29 -05:00
Fedora Kernel Team 408c4e5c6a
[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-11-01 13:41:29 -05:00
Fedora Kernel Team 6ad72d1410
[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-11-01 13:41:29 -05:00
Fedora Kernel Team eb40d19e86
[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-11-01 13:41:29 -05:00
Fedora Kernel Team 67c2d5e29a
[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-11-01 13:41:29 -05:00
Fedora Kernel Team 1a875e8312
[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-11-01 13:41:28 -05:00
Fedora Kernel Team 9eab0c5f08
[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-11-01 13:41:28 -05:00
Fedora Kernel Team 99683462dd
[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-11-01 13:41:28 -05:00
Fedora Kernel Team 352d92e6ac
[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-11-01 13:41:28 -05:00
Fedora Kernel Team 99a8720f0e
[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-11-01 13:41:28 -05:00
Fedora Kernel Team 0fea2092fe
[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-11-01 13:41:28 -05:00
Fedora Kernel Team acdd09a2b4
[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-11-01 13:41:28 -05:00
Herton R. Krzesinski f4e51d6c4f
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-11-01 13:41:27 -05:00
Fedora Kernel Team e7b80bafb6
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:27 -05:00
Fedora Kernel Team ecbb0bb308
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-11-01 13:41:27 -05:00
Fedora Kernel Team 864ef2a443
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:27 -05:00
Fedora Kernel Team 5f4ebdbecb
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:27 -05:00
Justin M. Forbes e65792ccf4
Turn on CONFIG_PPC_QUEUED_SPINLOCKS as it is default upstream now
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:27 -05:00
Fedora Kernel Team 36e5349990
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:27 -05:00
Fedora Kernel Team 7206ef8153
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:26 -05:00
Fedora Kernel Team cc8508382c
[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-11-01 13:41:26 -05:00
Prarit Bhargava 13a6d514cf
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-11-01 13:41:26 -05:00
Fedora Kernel Team b911b775ab
[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-11-01 13:41:26 -05:00
Fedora Kernel Team 867c962d01
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:26 -05:00
Fedora Kernel Team 7a069a5891
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:26 -05:00
Patrick Talbert de54b43b3a
[redhat] configs: Enable CONFIG_SND_JACK_INJECTION_DEBUG for the debug
variant

Signed-off-by: Patrick Talbert <ptalbert@redhat.com>
2021-11-01 13:41:26 -05:00
Fedora Kernel Team 12e22b84f1
[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-11-01 13:41:25 -05:00
Fedora Kernel Team ab9a45fcbd
[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-11-01 13:41:25 -05:00
Fedora Kernel Team 5974bcf3a3
[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-11-01 13:41:25 -05:00
Fedora Kernel Team 30cdfddffb
[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-11-01 13:41:25 -05:00
Fedora Kernel Team c19d074d4f
[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-11-01 13:41:25 -05:00
Fedora Kernel Team b8723d359c
[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-11-01 13:41:25 -05:00
Fedora Kernel Team fc5ff61218
[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-11-01 13:41:25 -05:00
Justin M. Forbes 1c01226ec7
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-11-01 13:41:24 -05:00
Herton R. Krzesinski 488278a9be
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-11-01 13:41:24 -05:00
Fedora Kernel Team 262f24ff2d
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:24 -05:00
Fedora Kernel Team 9f31eaa4f0
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:24 -05:00
Fedora Kernel Team be9e7cb884
[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-11-01 13:41:24 -05:00
Jeremy Cline d27bf4c9af
[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-11-01 13:41:24 -05:00
Justin M. Forbes 851f87e062
Removed description text as a comment confuses the config generation
Signed-off-by: Justin M. Forbes <jforbes@redhat.com>
2021-11-01 13:41:24 -05:00
Jeremy Cline 4e9d4f55f5
[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-11-01 13:41:23 -05:00
Fedora Kernel Team 94d70575b0
[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-11-01 13:41:23 -05:00
Jeremy Cline 876eb3bdd3
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-11-01 13:41:23 -05:00
CKI Gitlab 6ee2ef215e
[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-11-01 13:41:23 -05:00
Peter Robinson 4a1cdb9ca0
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-11-01 13:41:23 -05:00
Peter Robinson e99526cf8b
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-11-01 13:41:23 -05:00
Ondrej Mosnacek ef6c87b13b
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-11-01 13:41:23 -05:00
Kamal Heib 9018238c37
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-11-01 13:41:22 -05:00
Kamal Heib f4409cee0c
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-11-01 13:41:22 -05:00
Kamal Heib 090002c75c
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-11-01 13:41:22 -05:00
Kamal Heib c565f947cb
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-11-01 13:41:22 -05:00
Kamal Heib 358f881d44
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-11-01 13:41:22 -05:00
Justin M. Forbes 78fb21ef80
Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:22 -05:00
Peter Robinson 228c4891f6
fedora: minor arm sound config updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:22 -05:00
Justin M. Forbes 1c3bcc05a1
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-11-01 13:41:21 -05:00
Hans de Goede 739386e781
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-11-01 13:41:21 -05:00
Hans de Goede dabbce487a
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-11-01 13:41:21 -05:00
Hans de Goede d49eb46f0a
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:21 -05:00
Waiman Long 2fac3e7e2e
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-11-01 13:41:21 -05:00
Marcelo Ricardo Leitner 9372212b8f
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-11-01 13:41:21 -05:00
Prarit Bhargava 98348c46a8
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-11-01 13:41:21 -05:00
Veronika Kabatova c72deca741
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-11-01 13:41:20 -05:00
Philipp Rudo f04c915469
[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-11-01 13:41:20 -05:00
Herton R. Krzesinski 3b93990263
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-11-01 13:41:20 -05:00
Justin M. Forbes 1b5c204334
The comments in CONFIG_USB_RTL8153_ECM actually turn off CONFIG_USB_RTL8152
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:20 -05:00
Veronika Kabatova 38254afb3b
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-11-01 13:41:20 -05:00
Justin M. Forbes 3370d86cd6
Turn off additional KASAN options for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:20 -05:00
Justin M. Forbes b0d5460ee3
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-11-01 13:41:20 -05:00
Ben Crocker 3c3ef2c61d
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-11-01 13:41:20 -05:00
Justin M. Forbes 3b08d347fd
Turn off KASAN for rawhide debug builds
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:19 -05:00
Fedora Kernel Team 3c5339b085
[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-11-01 13:41:19 -05:00
Justin Forbes b001106da8
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-11-01 13:41:19 -05:00
Peter Robinson 904083df3a
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-11-01 13:41:19 -05:00
Herton R. Krzesinski 55cb7b70df
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-11-01 13:41:19 -05:00
Herton R. Krzesinski 92bd24d092
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-11-01 13:41:19 -05:00
Ben Crocker 12c876ca51
kernel.spec.template - fix use_vdso usage
Signed-off-by: Ben Crocker <bcrocker@redhat.com>
2021-11-01 13:41:19 -05:00
Ben Crocker 95f9231631
[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-11-01 13:41:19 -05:00
Justin M. Forbes ec3424c561
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-11-01 13:41:18 -05:00
Fedora Kernel Team cf43d4fa02
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:18 -05:00
Fedora Kernel Team e9dcee36f6
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:18 -05:00
Jiri Olsa 70b01e3511
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-11-01 13:41:18 -05:00
Ben Crocker 5eed50f941
[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-11-01 13:41:18 -05:00
Fedora Kernel Team 592fb2f4e7
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-11-01 13:41:18 -05:00
Jeremy Cline 86ff2f0cb5
[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-11-01 13:41:17 -05:00
Fedora Kernel Team d9c746ce65
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:17 -05:00
Justin M. Forbes 2627758a24
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-11-01 13:41:17 -05:00
Justin M. Forbes 10102bd693
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-11-01 13:41:17 -05:00
Jakub Čajka 7b2e1e490e
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-11-01 13:41:17 -05:00
Jeremy Cline 94104e088d
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-11-01 13:41:17 -05:00
Jeremy Cline 369cd55155
[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-11-01 13:41:17 -05:00
Jeremy Cline 558133ada7
[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-11-01 13:41:16 -05:00
Fedora Kernel Team cf079665c3
[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-11-01 13:41:16 -05:00
Fedora Kernel Team 3665643823
[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-11-01 13:41:16 -05:00
Jeremy Cline ea0b7d5101
[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-11-01 13:41:16 -05:00
CKI Gitlab 3ef08e0cad
[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-11-01 13:41:16 -05:00
CKI Gitlab ff1c6b1fd3
[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-11-01 13:41:16 -05:00
Fedora Kernel Team b570d7b6cc
[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-11-01 13:41:16 -05:00
Fedora Kernel Team 1d57be844b
[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-11-01 13:41:15 -05:00
Fedora Kernel Team 0f30c63f70
[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-11-01 13:41:15 -05:00
Justin M. Forbes 2315b06c36
Fedora 5.11 config updates part 4
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:15 -05:00
Justin M. Forbes 944049fff3
Fedora 5.11 config updates part 3
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:15 -05:00
Justin M. Forbes 76eadd3a01
Fedora 5.11 config updates part 2
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:15 -05:00
Joe Lawrence 8250eef761
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-11-01 13:41:15 -05:00
Fedora Kernel Team 0014183b37
[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-11-01 13:41:15 -05:00
CKI Gitlab b92830bdbd
[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-11-01 13:41:14 -05:00
Fedora Kernel Team 9aca6b8d6f
[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-11-01 13:41:14 -05:00
Fedora Kernel Team 83d2963054
[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-11-01 13:41:14 -05:00
Justin M. Forbes 084175dee1
Fix USB_XHCI_PCI regression
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:14 -05:00
Peter Robinson c16ffe6580
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-11-01 13:41:14 -05:00
Justin M. Forbes 13d85cf34b
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-11-01 13:41:14 -05:00
Fedora Kernel Team f24aa5bde3
[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-11-01 13:41:14 -05:00
Fedora Kernel Team d5f93b4fdb
[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-11-01 13:41:13 -05:00
Dan Horák 8548c75fa4
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-11-01 13:41:13 -05:00
Fedora Kernel Team a58eaee8d3
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:13 -05:00
Justin M. Forbes 9c19e7caae
Fedora 5.11 configs pt 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:13 -05:00
Herton R. Krzesinski d7cda40fd6
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-11-01 13:41:13 -05:00
Herton R. Krzesinski d383bae606
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-11-01 13:41:13 -05:00
Denys Vlasenko 2f6c8ff613
specfile: add %{?_smp_mflags} to "make headers_install" in tools/testing/selftests
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
2021-11-01 13:41:13 -05:00
Denys Vlasenko 41fd302213
specfile: add %{?_smp_mflags} to "make samples/bpf/"
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
2021-11-01 13:41:12 -05:00
CKI Gitlab 1bacf27f91
[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-11-01 13:41:12 -05:00
CKI Gitlab bf5e65a7fb
[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-11-01 13:41:12 -05:00
Veronika Kabatova 9ef194ba8e
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-11-01 13:41:12 -05:00
Nicolas Chauvet c5a95ef006
Reword comment 2021-11-01 13:41:12 -05:00
Nicolas Chauvet 36bf549079
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-11-01 13:41:12 -05:00
Nicolas Chauvet d20d9ff4e1
Redefines __strip if with_cross
Signed-off-by: Nicolas Chauvet <kwizart@gmail.com>
2021-11-01 13:41:11 -05:00
Patrick Talbert bb2ef66992
[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-11-01 13:41:11 -05:00
Fedora Kernel Team 945b6630b4
[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-11-01 13:41:11 -05:00
Ben Crocker 4717bd1ee3
[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-11-01 13:41:11 -05:00
Ben Crocker b88e3c2325
[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-11-01 13:41:11 -05:00
Peter Robinson 3b0dc35576
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-11-01 13:41:11 -05:00
Peter Robinson 41e6a3abe5
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-11-01 13:41:11 -05:00
Peter Robinson 96f45b4c1c
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-11-01 13:41:11 -05:00
Peter Robinson 6356cd89e0
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-11-01 13:41:10 -05:00
Peter Robinson 2892f8c552
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-11-01 13:41:10 -05:00
Peter Robinson 7bc6ff52d1
all: all ACPI platforms enable ATA_ACPI so move it to common
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:10 -05:00
Peter Robinson 9bb318ed9a
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-11-01 13:41:10 -05:00
Peter Robinson 714e207705
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-11-01 13:41:10 -05:00
Peter Robinson bbe1a8f4b6
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-11-01 13:41:10 -05:00
Peter Robinson bfacd23145
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-11-01 13:41:10 -05:00
Peter Robinson 49d08206c0
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-11-01 13:41:09 -05:00
Peter Robinson 4a62fe6f8c
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-11-01 13:41:09 -05:00
Peter Robinson ab5cfa99fc
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-11-01 13:41:09 -05:00
Peter Robinson 6eb61baaaf
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-11-01 13:41:09 -05:00
Jeremy Cline 40256364b1
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-11-01 13:41:09 -05:00
Guillaume Nault a3b7fc00b8
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-11-01 13:41:09 -05:00
Brian Masney 1e0174e2d9
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-11-01 13:41:08 -05:00
Brian Masney 6871c7cb3b
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-11-01 13:41:08 -05:00
Prarit Bhargava 90cd085236
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-11-01 13:41:08 -05:00
Prarit Bhargava 83957e12b2
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-11-01 13:41:08 -05:00
Vitaly Kuznetsov 1cc06ba8b7
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-11-01 13:41:08 -05:00
CKI Gitlab f75905dc7e
[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-11-01 13:41:08 -05:00
Fedora Kernel Team d3d5205094
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:08 -05:00
Fedora Kernel Team 52cca71b1a
[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-11-01 13:41:08 -05:00
CKI Gitlab b67400f83d
[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-11-01 13:41:07 -05:00
Jeremy Cline 32d78aaf4d
[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-11-01 13:41:07 -05:00
Peter Robinson b75457a212
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-11-01 13:41:07 -05:00
Justin M. Forbes cc8a45a898
Add gcc-c++ to BuildRequires
This is required for some of the gcc plugins.

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:07 -05:00
Justin M. Forbes 8e93b132f8
Update CONFIG_KASAN_HW_TAGS
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:07 -05:00
Peter Robinson 3dcfc1af74
fedora: arm: move generic power off/reset to all arm
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:07 -05:00
Peter Robinson d38d61d123
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-11-01 13:41:07 -05:00
Peter Robinson 5cdb1e40eb
fedora: cleanup joystick_adc
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:07 -05:00
Peter Robinson 88c3b77a50
fedora: update some display options
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:06 -05:00
Peter Robinson c58797b753
fedora: arm: enable TI PRU options
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:06 -05:00
Peter Robinson 3f0572bc80
fedora: arm: minor exynos plaform updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:06 -05:00
Peter Robinson be1648bf4b
arm: SoC: disable Toshiba Visconti SoC 2021-11-01 13:41:06 -05:00
Peter Robinson 14b80f766c
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-11-01 13:41:06 -05:00
Peter Robinson b9a544c217
fedora: minor arm config updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:06 -05:00
Peter Robinson 82b3b3ff49
fedora: enable Tegra 234 SoC
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:06 -05:00
Peter Robinson dbdb5f0ae1
fedora: arm: enable new Hikey 3xx options
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:05 -05:00
Peter Robinson 7171214bc5
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-11-01 13:41:05 -05:00
Peter Robinson 8da7fd5ab0
fedora: enable the GNSS receiver subsystem
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:05 -05:00
Peter Robinson dcd0a26177
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-11-01 13:41:05 -05:00
Peter Robinson 741e949d6a
Cleanup RESET_RASPBERRYPI
We want this for Fedora so clean up this config

Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:05 -05:00
Peter Robinson 3d4996c360
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-11-01 13:41:05 -05:00
Peter Robinson c7aa32a697
fedora: arm crypto updates
Signed-off-by: Peter Robinson <pbrobinson@redhat.com>
2021-11-01 13:41:05 -05:00
Justin M. Forbes 3948c0e403
CONFIG_KASAN_HW_TAGS for aarch64
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:41:04 -05:00
Peter Robinson c60691abbd
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-11-01 13:41:04 -05:00
Fedora Kernel Team 859014725a
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:04 -05:00
Fedora Kernel Team 51ab81faac
[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-11-01 13:41:04 -05:00
Fedora Kernel Team 8cc80cdae0
[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-11-01 13:41:04 -05:00
Fedora Kernel Team b495df13b2
[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-11-01 13:41:04 -05:00
Fedora Kernel Team 231c44a294
[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-11-01 13:41:04 -05:00
Fedora Kernel Team f04154d753
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:03 -05:00
Fedora Kernel Team fe961e3805
[redhat] AUTOMATIC: New configs 2021-11-01 13:41:03 -05:00
Fedora Kernel Team 59ee315228
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-11-01 13:41:03 -05:00
Jeremy Cline a62775cc55
[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-11-01 13:41:03 -05:00
Josh Poimboeuf 3a9698c9b7
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-11-01 13:41:03 -05:00
Josh Poimboeuf a8c4a7b50b
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-11-01 13:41:03 -05:00
Josh Poimboeuf 0e70ad29fa
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-11-01 13:41:03 -05:00
Josh Poimboeuf 90323e48c2
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-11-01 13:41:02 -05:00
Fedora Kernel Team 20f384da3f
[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-11-01 13:41:02 -05:00
Fedora Kernel Team e62046b4a2
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-11-01 13:41:02 -05:00
Ben Crocker 38e68ed4a9
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-11-01 13:41:02 -05:00
Ben Crocker 65127d17ba
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-11-01 13:41:02 -05:00
Ben Crocker 13bcce26de
[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-11-01 13:41:02 -05:00
Ben Crocker aa709b8848
[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-11-01 13:41:02 -05:00
Ben Crocker e332846985
[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-11-01 13:41:01 -05:00
Ben Crocker f1548f7dc7
[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-11-01 13:41:01 -05:00
Ben Crocker 42342ccdae
[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-11-01 13:41:01 -05:00
Ben Crocker 83f6596196
[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-11-01 13:41:01 -05:00
Ben Crocker d8c264873c
[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-11-01 13:41:01 -05:00
Ben Crocker a1cc52d0e1
[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-11-01 13:41:01 -05:00
Ben Crocker 4f5ecd2eda
[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-11-01 13:41:01 -05:00
Ben Crocker 3b08fe59e2
[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-11-01 13:41:01 -05:00
Ben Crocker 661df70385
[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-11-01 13:41:00 -05:00
Ben Crocker a689bf9bd1
[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-11-01 13:41:00 -05:00
Ben Crocker 68ea746b81
[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-11-01 13:41:00 -05:00
Ben Crocker 58c6fda646
[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-11-01 13:41:00 -05:00
Ben Crocker 5c88365607
[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-11-01 13:41:00 -05:00
Ben Crocker bcdb07ef38
[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-11-01 13:41:00 -05:00
Ben Crocker e44f5a466a
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-11-01 13:41:00 -05:00
Ben Crocker 7aaf8b1078
[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-11-01 13:40:59 -05:00
Justin M. Forbes fae64654ec
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-11-01 13:40:59 -05:00
Fedora Kernel Team 4c0652e961
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-11-01 13:40:59 -05:00
CKI Gitlab 3601f3a3f4
[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-11-01 13:40:59 -05:00
Justin M. Forbes 48ee77b654
Fix fedora config mismatch due to dep changes
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:59 -05:00
Fedora Kernel Team cc6534108b
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:59 -05:00
Jeremy Cline 05f2f142a5
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-11-01 13:40:59 -05:00
Peter Robinson 1a84ecad52
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-11-01 13:40:58 -05:00
Fedora Kernel Team e7c4569bb4
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:58 -05:00
Fedora Kernel Team 19ff18f607
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:58 -05:00
Fedora Kernel Team cf9378abda
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:58 -05:00
Fedora Kernel Team ba336ff700
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:58 -05:00
Fedora Kernel Team b822865ddb
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:58 -05:00
Fedora Kernel Team d0463e1029
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:58 -05:00
Justin M. Forbes 36ebc127f2
This is selected by PCIE_QCOM so must match
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:57 -05:00
Fedora Kernel Team e36c93f987
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:57 -05:00
Fedora Kernel Team be46c92d96
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:57 -05:00
Fedora Kernel Team 1637a3553f
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:57 -05:00
Fedora Kernel Team 1e1cd66d3c
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:57 -05:00
Fedora Kernel Team 5e813dd73a
[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-11-01 13:40:57 -05:00
Peter Robinson 72aa37f9bb
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-11-01 13:40:57 -05:00
Fedora Kernel Team bce9e39f4a
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:56 -05:00
Fedora Kernel Team e3b700ad66
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:56 -05:00
Jeremy Cline 27e7fa2cc2
[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-11-01 13:40:56 -05:00
Jeremy Cline a4a3053839
[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-11-01 13:40:56 -05:00
Paulo E. Castro 3bc20aea22
Remove cp instruction already handled in instruction below.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-11-01 13:40:56 -05:00
Paulo E. Castro 79abc09240
Add all the dependencies gleaned from running `make prepare` on a bloated devel kernel.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-11-01 13:40:56 -05:00
Paulo E. Castro d882f2cc9a
Add tools to path mangling script.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-11-01 13:40:56 -05:00
Paulo E. Castro 1c459dcec5
Remove duplicate cp statement which is also not specific to x86.
Signed-off-by: Paulo E. Castro <pecastro@wormholenet.com>
2021-11-01 13:40:56 -05:00
Paulo E. Castro 89ae8dee54
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-11-01 13:40:55 -05:00
Jiri Olsa 6325ed1d88
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-11-01 13:40:55 -05:00
Prarit Bhargava 4451490044
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-11-01 13:40:55 -05:00
Augusto Caringi 7c050c94f6
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-11-01 13:40:55 -05:00
Don Zickus 8c7526d477
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-11-01 13:40:55 -05:00
Fedora Kernel Team a2545286c9
[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-11-01 13:40:55 -05:00
Justin M. Forbes 99e75ce68d
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-11-01 13:40:55 -05:00
Fedora Kernel Team c93edeaee7
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:55 -05:00
Fedora Kernel Team fb17388aa6
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:54 -05:00
Fedora Kernel Team 98a10761ac
[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-11-01 13:40:54 -05:00
CKI@GitLab b6dab28b62
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-11-01 13:40:54 -05:00
Fedora Kernel Team 7c01a38836
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-11-01 13:40:54 -05:00
Fedora Kernel Team 7bd12c1cc0
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-11-01 13:40:54 -05:00
Justin M. Forbes 779069934b
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-11-01 13:40:54 -05:00
Bruno Meneguele 96bc8d050e
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-11-01 13:40:54 -05:00
Bruno Meneguele 34503c8318
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-11-01 13:40:53 -05:00
Bruno Meneguele 8327769fe4
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-11-01 13:40:53 -05:00
Bruno Meneguele 493f739c0c
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-11-01 13:40:53 -05:00
Bruno Meneguele 9607b77205
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-11-01 13:40:53 -05:00
Bruno Meneguele c3d9a26df7
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-11-01 13:40:53 -05:00
Bruno Meneguele f1bf429f5b
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-11-01 13:40:53 -05:00
Bruno Meneguele af6f84eb02
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-11-01 13:40:53 -05:00
Bruno Meneguele 8ca4fcc653
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-11-01 13:40:52 -05:00
Bruno Meneguele b5fa596f9b
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-11-01 13:40:52 -05:00
Bruno Meneguele 7b06f8d3e9
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-11-01 13:40:52 -05:00
Bruno Meneguele fd01cda11d
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-11-01 13:40:52 -05:00
Bruno Meneguele 35b963768a
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-11-01 13:40:52 -05:00
Bruno Meneguele b78a65e5ee
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-11-01 13:40:52 -05:00
Bruno Meneguele 25ca3a675e
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-11-01 13:40:51 -05:00
Bruno Meneguele 03b5b225ba
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-11-01 13:40:51 -05:00
Ben Crocker 9e49dadc6f
[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-11-01 13:40:51 -05:00
Ben Crocker c0a2b7b96b
[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-11-01 13:40:51 -05:00
Ben Crocker 9a69c8b618
[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-11-01 13:40:51 -05:00
Ben Crocker e54a6fd2ff
[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-11-01 13:40:51 -05:00
Jeremy Linton 930845e4ca
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-11-01 13:40:51 -05:00
Jeremy Linton 16156ecd58
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-11-01 13:40:51 -05:00
Justin Forbes c87f3a49cc
Update CONFIG_INET6_ESPINTCP 2021-11-01 13:40:50 -05:00
Justin M. Forbes 6fe9819056
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-11-01 13:40:50 -05:00
Peter Robinson 7164821c9f
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-11-01 13:40:50 -05:00
Don Zickus 36a07abd72
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-11-01 13:40:50 -05:00
Jeremy Cline 554e336416
[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-11-01 13:40:50 -05:00
Peter Robinson f253f7efc8
fedora: some minor arm audio config tweaks
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-11-01 13:40:50 -05:00
Bastien Nocera c66c98a376
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-11-01 13:40:50 -05:00
Peter Robinson 68b2660e49
Fedora: Only enable legacy serial/game port joysticks on x86
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2021-11-01 13:40:49 -05:00
Peter Robinson b729a6e66d
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-11-01 13:40:49 -05:00
Justin M. Forbes 50b66bc92c
Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:49 -05:00
Justin M. Forbes 5ee4eed5e2
Fedora config change because CONFIG_FSL_DPAA2_ETH now selects CONFIG_FSL_XGMAC_MDIO
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:49 -05:00
Herton R. Krzesinski 0570102d46
[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-11-01 13:40:49 -05:00
Herton R. Krzesinski 17eb1caab4
[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-11-01 13:40:49 -05:00
Herton R. Krzesinski ab7234c784
[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-11-01 13:40:49 -05:00
Herton R. Krzesinski bfedfdf9d3
[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-11-01 13:40:48 -05:00
Davide Caratti 40f376bcff
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-11-01 13:40:48 -05:00
Justin M. Forbes 01932a1a76
Fedora config update
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:48 -05:00
Fedora Kernel Team f63d1bf259
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:48 -05:00
Justin M. Forbes 1f4a7417fc
Enable NANDSIM for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:48 -05:00
Justin M. Forbes d4473437a4
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-11-01 13:40:48 -05:00
Justin M. Forbes 38208ec8d5
Ath11k related config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:48 -05:00
Fedora Kernel Team b3546cf6e9
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:47 -05:00
Justin M. Forbes 794a9e30bc
Fedora config updates for ath11k
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:47 -05:00
Fedora Kernel Team 8741537921
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:47 -05:00
Justin M. Forbes 630b60742c
Turn on ATH11K for Fedora
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:47 -05:00
Fedora Kernel Team 7cef5b02f5
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:47 -05:00
Jerry Snitselaar 72ca211752
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-11-01 13:40:47 -05:00
Justin M. Forbes a6d38a8f9e
More Fedora config fixes
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:47 -05:00
Justin M. Forbes be274b68ef
Fedora 5.10 config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:46 -05:00
Fedora Kernel Team b14a520006
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:46 -05:00
Justin M. Forbes e49c204b8c
Fedora 5.10 configs round 1
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:46 -05:00
Justin M. Forbes cb31643506
Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:46 -05:00
Fedora Kernel Team 5f02f0ed1e
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:46 -05:00
Fedora Kernel Team 31f8b5727a
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:46 -05:00
Don Zickus 1c292468a9
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-11-01 13:40:46 -05:00
Don Zickus bb8db2b6f8
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-11-01 13:40:46 -05:00
Davide Caratti 9b650f0eab
redhat: ark: disable CONFIG_NET_ACT_CTINFO
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti befbee7661
redhat: ark: disable CONFIG_NET_SCH_TEQL
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti 5e2c0e4ade
redhat: ark: disable CONFIG_NET_SCH_SFB
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti d966c6434c
redhat: ark: disable CONFIG_NET_SCH_QFQ
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti b280b1bf52
redhat: ark: disable CONFIG_NET_SCH_PLUG
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti 491e087da3
redhat: ark: disable CONFIG_NET_SCH_PIE
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti 52ce3f758f
redhat: ark: disable CONFIG_NET_SCH_HHF
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti 746e6b2250
redhat: ark: disable CONFIG_NET_SCH_DSMARK
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:45 -05:00
Davide Caratti 6538c0b673
redhat: ark: disable CONFIG_NET_SCH_DRR
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:44 -05:00
Davide Caratti b5e74b2134
redhat: ark: disable CONFIG_NET_SCH_CODEL
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:44 -05:00
Davide Caratti 23bac6fa0c
redhat: ark: disable CONFIG_NET_SCH_CHOKE
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:44 -05:00
Davide Caratti 0b0641dd92
redhat: ark: disable CONFIG_NET_SCH_CBQ
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:44 -05:00
Davide Caratti d76d926555
redhat: ark: disable CONFIG_NET_SCH_ATM
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:44 -05:00
Davide Caratti cbd9527048
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-11-01 13:40:44 -05:00
Davide Caratti b5f550cd41
redhat: ark: disable CONFIG_NET_CLS_TCINDEX
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:44 -05:00
Davide Caratti ba2c42090c
redhat: ark: disable CONFIG_NET_CLS_RSVP6
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:43 -05:00
Davide Caratti 630eae1e11
redhat: ark: disable CONFIG_NET_CLS_RSVP
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:43 -05:00
Davide Caratti 5ea47898b3
redhat: ark: disable CONFIG_NET_CLS_ROUTE4
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:43 -05:00
Davide Caratti 0d722fb67a
redhat: ark: disable CONFIG_NET_CLS_BASIC
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:43 -05:00
Davide Caratti f43ec73315
redhat: ark: disable CONFIG_NET_ACT_SKBMOD
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:43 -05:00
Davide Caratti c03452109f
redhat: ark: disable CONFIG_NET_ACT_SIMP
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:43 -05:00
Davide Caratti f2f3270a97
redhat: ark: disable CONFIG_NET_ACT_NAT
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
2021-11-01 13:40:43 -05:00
Fedora Kernel Team 50a0f68d17
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:42 -05:00
Bhupesh Sharma 03285c6d0b
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-11-01 13:40:42 -05:00
Prarit Bhargava 07afbbadd4
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-11-01 13:40:42 -05:00
Fedora Kernel Team b3ea7881b8
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-11-01 13:40:42 -05:00
Fedora Kernel Team 2b74673abc
[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-11-01 13:40:42 -05:00
Fedora Kernel Team bbc58663f8
[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-11-01 13:40:42 -05:00
Fedora Kernel Team 957b0c4a06
[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-11-01 13:40:42 -05:00
Fedora Kernel Team 21459b8b36
[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-11-01 13:40:42 -05:00
Don Zickus ce0efa668c
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-11-01 13:40:41 -05:00
Justin M. Forbes d4e3dc8f4d
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-11-01 13:40:41 -05:00
Ondrej Mosnacek 0045357c2a
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-11-01 13:40:41 -05:00
Fedora Kernel Team ab76529393
[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-11-01 13:40:41 -05:00
Fedora Kernel Team c75abf83ef
[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-11-01 13:40:41 -05:00
Fedora Kernel Team 5f1f292294
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:41 -05:00
Fedora Kernel Team b0439e087f
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:41 -05:00
Don Zickus ed1bc7deb3
[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-11-01 13:40:41 -05:00
Fedora Kernel Team 770976b7db
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:40 -05:00
Fedora Kernel Team f20840f958
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:40 -05:00
Fedora Kernel Team b6301b1f42
[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-11-01 13:40:40 -05:00
Fedora Kernel Team 8ae892f294
[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-11-01 13:40:40 -05:00
Fedora Kernel Team e09ca97fc6
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:40 -05:00
Fedora Kernel Team 5a5253e1fe
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:40 -05:00
Brian Masney 799d6cd638
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-11-01 13:40:40 -05:00
Prarit Bhargava ed32acd79d
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-11-01 13:40:39 -05:00
Jan Stancek 8db57fc21d
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-11-01 13:40:39 -05:00
Jerry Snitselaar e5f33de3ae
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-11-01 13:40:39 -05:00
Fedora Kernel Team c1a9be1980
[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-11-01 13:40:39 -05:00
Fedora Kernel Team ec7f9b3585
[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-11-01 13:40:39 -05:00
Fedora Kernel Team 423e0a6dea
[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-11-01 13:40:39 -05:00
Fedora Kernel Team 63f86a8de9
[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-11-01 13:40:39 -05:00
Fedora Kernel Team 6b3f78305d
[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-11-01 13:40:38 -05:00
Fedora Kernel Team 2238e2db00
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-11-01 13:40:38 -05:00
Justin M. Forbes 8b3ffb4225
Fix Fedora config locations
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:38 -05:00
Justin M. Forbes 18b531248a
Fedora config updates
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:38 -05:00
Fedora Kernel Team b7d76b8fbf
[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-11-01 13:40:38 -05:00
Fedora Kernel Team 5303f06409
[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-11-01 13:40:38 -05:00
Fedora Kernel Team 36cb4ebb99
[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-11-01 13:40:38 -05:00
Fedora Kernel Team 25557542c6
[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-11-01 13:40:37 -05:00
Fedora Kernel Team 252cdfce5f
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:37 -05:00
Fedora Kernel Team 768d3f80fa
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:37 -05:00
Vladis Dronov 87b742030c
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-11-01 13:40:37 -05:00
Fedora Kernel Team 1af6366b67
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:37 -05:00
Fedora Kernel Team fd6bfeacda
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:37 -05:00
Don Zickus ef7149202e
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-11-01 13:40:37 -05:00
Don Zickus c7c40ecdc7
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-11-01 13:40:37 -05:00
Prarit Bhargava e61bfc4039
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-11-01 13:40:36 -05:00
Justin M. Forbes 07863633ae
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-11-01 13:40:36 -05:00
Fedora Kernel Team de28aaf59b
[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-11-01 13:40:36 -05:00
Fedora Kernel Team 51d292d575
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:36 -05:00
Fedora Kernel Team aba8e32a20
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:36 -05:00
Prarit Bhargava 71074aabc4
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-11-01 13:40:36 -05:00
Justin M. Forbes 112ba1b8a9
Disable Speakup synth DECEXT
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:36 -05:00
Justin M. Forbes 1bd2ed82ba
Enable Speakup for Fedora since it is out of staging
Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
2021-11-01 13:40:35 -05:00
Don Zickus fac1cc6949
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-11-01 13:40:35 -05:00
Tony Camuso be64c52df0
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-11-01 13:40:35 -05:00
Prarit Bhargava acaff3431b
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-11-01 13:40:35 -05:00
Prarit Bhargava 4a000c7fee
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-11-01 13:40:35 -05:00
Prarit Bhargava af428bb744
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-11-01 13:40:35 -05:00
Ben Crocker 857c3336b7
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-11-01 13:40:35 -05:00
Ben Crocker b903f36f2a
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-11-01 13:40:34 -05:00
Ben Crocker 2044839e99
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-11-01 13:40:34 -05:00
Fedora Kernel Team 3e2f932d1e
[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-11-01 13:40:34 -05:00
Fedora Kernel Team ba95fa3011
[redhat] AUTOMATIC: New configs 2021-11-01 13:40:34 -05:00
Robert Holmes 44a99ce019
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-11-01 13:40:34 -05:00
Benjamin Tissoires a542b3b414
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-11-01 13:40:34 -05:00
Peter Robinson 36cf4f744b
ARM: tegra: usb no reset
Patch for disconnect issues with storage attached to a
 tegra-ehci controller
2021-11-01 13:40:34 -05:00
Jon Masters 3668c10324
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-11-01 13:40:34 -05:00
Peter Robinson 288c6720af
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-11-01 13:40:33 -05:00
Jeremy Cline 85f19dfc97
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-11-01 13:40:33 -05:00
David Howells 733a0da553
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-11-01 13:40:33 -05:00
David Howells 5cd6fe00f5
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-11-01 13:40:33 -05:00
Jeremy Cline edccd4be79
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-11-01 13:40:33 -05:00
Peter Jones 539e9d5a95
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-11-01 13:40:33 -05:00
Peter Jones 83e49272fa
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-11-01 13:40:32 -05:00
Jeremy Cline eb9f5f1c8e
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-11-01 13:40:32 -05:00
Laura Abbott 75a010f21e
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-11-01 13:40:32 -05:00
Laura Abbott 4acf659b77
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-11-01 13:40:32 -05:00
Maurizio Lombardi 80d5f0db72
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-11-01 13:40:32 -05:00
Robert Richter c7b85bdbc4
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-11-01 13:40:32 -05:00
Robert Richter efd31cf493
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-11-01 13:40:32 -05:00
Jeremy Cline 5a76c52ea7
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-11-01 13:40:32 -05:00
Mark Salter e73b49e13f
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-11-01 13:40:31 -05:00
Mark Salter df55336771
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-11-01 13:40:31 -05:00
Mark Salter a741b5a56f
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-11-01 13:40:31 -05:00
Al Stone 91069002cf
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-11-01 13:40:31 -05:00
3286 changed files with 14888 additions and 5734 deletions

View File

@ -1,10 +1,284 @@
# CI definitions for ark-patches and internal are maintained in a single file
# outside the main repository because the two branches are regularly merged
# together in release branches. Rather than trying to keep the two branches in
# sync or have merge conflicts each time we merge the two branches, the
# definition is stored externally and included in each branch.
#
# To update any CI jobs, please submit any merge requests to
# https://gitlab.com/cki-project/kernel-ark-ci/.
# 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:
- remote: 'https://gitlab.com/cki-project/kernel-ark-ci/raw/master/gitlab-ci.yml'
- 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

@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 15
SUBLEVEL = 0
SUBLEVEL = 1
EXTRAVERSION =
NAME = Trick or Treat

View File

@ -1,4 +1,4 @@
RHEL_MAJOR = 8
RHEL_MAJOR = 9
RHEL_MINOR = 99
#

View File

@ -1470,9 +1470,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,7 @@ int acpi_pci_disabled = 1; /* skip ACPI PCI scan and IRQ initialization */
EXPORT_SYMBOL(acpi_pci_disabled);
static bool param_acpi_off __initdata;
static bool param_acpi_on __initdata;
static bool param_acpi_on __initdata = true;
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

@ -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>
@ -929,6 +930,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 +1102,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();

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

@ -377,9 +377,6 @@ static int amba_device_try_add(struct amba_device *dev, struct resource *parent)
void __iomem *tmp;
int i, ret;
WARN_ON(dev->irq[0] == (unsigned int)-1);
WARN_ON(dev->irq[1] == (unsigned int)-1);
ret = request_resource(parent, &dev->res);
if (ret)
goto err_out;

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

@ -1078,8 +1078,6 @@ struct amdgpu_device {
char product_name[32];
char serial[20];
struct amdgpu_autodump autodump;
atomic_t throttling_logging_enabled;
struct ratelimit_state throttling_logging_rs;
uint32_t ras_hw_enabled;

View File

@ -27,7 +27,6 @@
#include <linux/pci.h>
#include <linux/uaccess.h>
#include <linux/pm_runtime.h>
#include <linux/poll.h>
#include "amdgpu.h"
#include "amdgpu_pm.h"
@ -37,85 +36,7 @@
#include "amdgpu_securedisplay.h"
#include "amdgpu_fw_attestation.h"
int amdgpu_debugfs_wait_dump(struct amdgpu_device *adev)
{
#if defined(CONFIG_DEBUG_FS)
unsigned long timeout = 600 * HZ;
int ret;
wake_up_interruptible(&adev->autodump.gpu_hang);
ret = wait_for_completion_interruptible_timeout(&adev->autodump.dumping, timeout);
if (ret == 0) {
pr_err("autodump: timeout, move on to gpu recovery\n");
return -ETIMEDOUT;
}
#endif
return 0;
}
#if defined(CONFIG_DEBUG_FS)
static int amdgpu_debugfs_autodump_open(struct inode *inode, struct file *file)
{
struct amdgpu_device *adev = inode->i_private;
int ret;
file->private_data = adev;
ret = down_read_killable(&adev->reset_sem);
if (ret)
return ret;
if (adev->autodump.dumping.done) {
reinit_completion(&adev->autodump.dumping);
ret = 0;
} else {
ret = -EBUSY;
}
up_read(&adev->reset_sem);
return ret;
}
static int amdgpu_debugfs_autodump_release(struct inode *inode, struct file *file)
{
struct amdgpu_device *adev = file->private_data;
complete_all(&adev->autodump.dumping);
return 0;
}
static unsigned int amdgpu_debugfs_autodump_poll(struct file *file, struct poll_table_struct *poll_table)
{
struct amdgpu_device *adev = file->private_data;
poll_wait(file, &adev->autodump.gpu_hang, poll_table);
if (amdgpu_in_reset(adev))
return POLLIN | POLLRDNORM | POLLWRNORM;
return 0;
}
static const struct file_operations autodump_debug_fops = {
.owner = THIS_MODULE,
.open = amdgpu_debugfs_autodump_open,
.poll = amdgpu_debugfs_autodump_poll,
.release = amdgpu_debugfs_autodump_release,
};
static void amdgpu_debugfs_autodump_init(struct amdgpu_device *adev)
{
init_completion(&adev->autodump.dumping);
complete_all(&adev->autodump.dumping);
init_waitqueue_head(&adev->autodump.gpu_hang);
debugfs_create_file("amdgpu_autodump", 0600,
adev_to_drm(adev)->primary->debugfs_root,
adev, &autodump_debug_fops);
}
/**
* amdgpu_debugfs_process_reg_op - Handle MMIO register reads/writes
@ -1588,7 +1509,6 @@ int amdgpu_debugfs_init(struct amdgpu_device *adev)
}
amdgpu_ras_debugfs_create_all(adev);
amdgpu_debugfs_autodump_init(adev);
amdgpu_rap_debugfs_init(adev);
amdgpu_securedisplay_debugfs_init(adev);
amdgpu_fw_attestation_debugfs_init(adev);

View File

@ -26,10 +26,6 @@
/*
* Debugfs
*/
struct amdgpu_autodump {
struct completion dumping;
struct wait_queue_head gpu_hang;
};
int amdgpu_debugfs_regs_init(struct amdgpu_device *adev);
int amdgpu_debugfs_init(struct amdgpu_device *adev);
@ -37,4 +33,3 @@ void amdgpu_debugfs_fini(struct amdgpu_device *adev);
void amdgpu_debugfs_fence_init(struct amdgpu_device *adev);
void amdgpu_debugfs_firmware_init(struct amdgpu_device *adev);
void amdgpu_debugfs_gem_init(struct amdgpu_device *adev);
int amdgpu_debugfs_wait_dump(struct amdgpu_device *adev);

View File

@ -2432,10 +2432,6 @@ static int amdgpu_device_ip_init(struct amdgpu_device *adev)
if (!adev->gmc.xgmi.pending_reset)
amdgpu_amdkfd_device_init(adev);
r = amdgpu_amdkfd_resume_iommu(adev);
if (r)
goto init_failed;
amdgpu_fru_get_product_info(adev);
init_failed:
@ -4466,10 +4462,6 @@ int amdgpu_device_pre_asic_reset(struct amdgpu_device *adev,
if (reset_context->reset_req_dev == adev)
job = reset_context->job;
/* no need to dump if device is not in good state during probe period */
if (!adev->gmc.xgmi.pending_reset)
amdgpu_debugfs_wait_dump(adev);
if (amdgpu_sriov_vf(adev)) {
/* stop the data exchange thread */
amdgpu_virt_fini_data_exchange(adev);

View File

@ -924,6 +924,9 @@ bool kgd2kfd_device_init(struct kfd_dev *kfd,
svm_migrate_init((struct amdgpu_device *)kfd->kgd);
if(kgd2kfd_resume_iommu(kfd))
goto device_iommu_error;
if (kfd_resume(kfd))
goto kfd_resume_error;

View File

@ -247,6 +247,7 @@ static ssize_t dp_link_settings_write(struct file *f, const char __user *buf,
{
struct amdgpu_dm_connector *connector = file_inode(f)->i_private;
struct dc_link *link = connector->dc_link;
struct dc *dc = (struct dc *)link->dc;
struct dc_link_settings prefer_link_settings;
char *wr_buf = NULL;
const uint32_t wr_buf_size = 40;
@ -313,7 +314,7 @@ static ssize_t dp_link_settings_write(struct file *f, const char __user *buf,
prefer_link_settings.lane_count = param[0];
prefer_link_settings.link_rate = param[1];
dp_retrain_link_dp_test(link, &prefer_link_settings, false);
dc_link_set_preferred_training_settings(dc, &prefer_link_settings, NULL, link, true);
kfree(wr_buf);
return size;

View File

@ -2140,10 +2140,6 @@ static void __execlists_unhold(struct i915_request *rq)
if (p->flags & I915_DEPENDENCY_WEAK)
continue;
/* Propagate any change in error status */
if (rq->fence.error)
i915_request_set_error_once(w, rq->fence.error);
if (w->engine != rq->engine)
continue;

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

@ -1165,7 +1165,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length)
read_pos += program_info_length;
write_pos += program_info_length;
}
while (read_pos < length) {
while (read_pos + 4 < length) {
if (write_pos + 4 >= sizeof(c->operand) - 4) {
ret = -EINVAL;
goto out;
}
c->operand[write_pos++] = msg[read_pos++];
c->operand[write_pos++] = msg[read_pos++];
c->operand[write_pos++] = msg[read_pos++];
@ -1177,13 +1181,17 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length)
c->operand[write_pos++] = es_info_length >> 8;
c->operand[write_pos++] = es_info_length & 0xff;
if (es_info_length > 0) {
if (read_pos >= length) {
ret = -EINVAL;
goto out;
}
pmt_cmd_id = msg[read_pos++];
if (pmt_cmd_id != 1 && pmt_cmd_id != 4)
dev_err(fdtv->device, "invalid pmt_cmd_id %d at stream level\n",
pmt_cmd_id);
if (es_info_length > sizeof(c->operand) - 4 -
write_pos) {
if (es_info_length > sizeof(c->operand) - 4 - write_pos ||
es_info_length > length - read_pos) {
ret = -EINVAL;
goto out;
}

View File

@ -134,6 +134,8 @@ static int fdtv_ca_pmt(struct firedtv *fdtv, void *arg)
} else {
data_length = msg->msg[3];
}
if (data_length > sizeof(msg->msg) - data_pos)
return -EINVAL;
return avc_ca_pmt(fdtv, &msg->msg[data_pos], data_length);
}

View File

@ -563,20 +563,14 @@ int efx_ethtool_get_link_ksettings(struct net_device *net_dev,
{
struct efx_nic *efx = netdev_priv(net_dev);
struct efx_link_state *link_state = &efx->link_state;
u32 supported;
mutex_lock(&efx->mac_lock);
efx_mcdi_phy_get_link_ksettings(efx, cmd);
mutex_unlock(&efx->mac_lock);
/* Both MACs support pause frames (bidirectional and respond-only) */
ethtool_convert_link_mode_to_legacy_u32(&supported,
cmd->link_modes.supported);
supported |= SUPPORTED_Pause | SUPPORTED_Asym_Pause;
ethtool_convert_legacy_u32_to_link_mode(cmd->link_modes.supported,
supported);
ethtool_link_ksettings_add_link_mode(cmd, supported, Pause);
ethtool_link_ksettings_add_link_mode(cmd, supported, Asym_Pause);
if (LOOPBACK_INTERNAL(efx)) {
cmd->base.speed = link_state->speed;

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

@ -604,15 +604,6 @@ static int wcn36xx_set_key(struct ieee80211_hw *hw, enum set_key_cmd cmd,
}
}
}
/* FIXME: Only enable bmps support when encryption is enabled.
* For any reasons, when connected to open/no-security BSS,
* the wcn36xx controller in bmps mode does not forward
* 'wake-up' beacons despite AP sends DTIM with station AID.
* It could be due to a firmware issue or to the way driver
* configure the station.
*/
if (vif->type == NL80211_IFTYPE_STATION)
vif_priv->allow_bmps = true;
break;
case DISABLE_KEY:
if (!(IEEE80211_KEY_FLAG_PAIRWISE & key_conf->flags)) {
@ -913,7 +904,6 @@ static void wcn36xx_bss_info_changed(struct ieee80211_hw *hw,
vif->addr,
bss_conf->aid);
vif_priv->sta_assoc = false;
vif_priv->allow_bmps = false;
wcn36xx_smd_set_link_st(wcn,
bss_conf->bssid,
vif->addr,

View File

@ -23,10 +23,7 @@ int wcn36xx_pmc_enter_bmps_state(struct wcn36xx *wcn,
{
int ret = 0;
struct wcn36xx_vif *vif_priv = wcn36xx_vif_to_priv(vif);
if (!vif_priv->allow_bmps)
return -ENOTSUPP;
/* TODO: Make sure the TX chain clean */
ret = wcn36xx_smd_enter_bmps(wcn, vif);
if (!ret) {
wcn36xx_dbg(WCN36XX_DBG_PMC, "Entered BMPS\n");

View File

@ -128,7 +128,6 @@ struct wcn36xx_vif {
enum wcn36xx_hal_bss_type bss_type;
/* Power management */
bool allow_bmps;
enum wcn36xx_power_state pw_state;
u8 bss_index;

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)
@ -814,8 +820,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

@ -157,12 +157,14 @@ 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)},

View File

@ -244,6 +244,8 @@ static int imx_pgc_power_up(struct generic_pm_domain *genpd)
goto out_regulator_disable;
}
reset_control_assert(domain->reset);
if (domain->bits.pxx) {
/* request the domain to power up */
regmap_update_bits(domain->regmap, GPC_PU_PGC_SW_PUP_REQ,
@ -266,8 +268,6 @@ static int imx_pgc_power_up(struct generic_pm_domain *genpd)
GPC_PGC_CTRL_PCR);
}
reset_control_assert(domain->reset);
/* delay for reset to propagate */
udelay(5);

View File

@ -2795,7 +2795,6 @@ int usb_add_hcd(struct usb_hcd *hcd,
{
int retval;
struct usb_device *rhdev;
struct usb_hcd *shared_hcd;
if (!hcd->skip_phy_initialization && usb_hcd_is_primary_hcd(hcd)) {
hcd->phy_roothub = usb_phy_roothub_alloc(hcd->self.sysdev);
@ -2956,26 +2955,13 @@ int usb_add_hcd(struct usb_hcd *hcd,
goto err_hcd_driver_start;
}
/* starting here, usbcore will pay attention to the shared HCD roothub */
shared_hcd = hcd->shared_hcd;
if (!usb_hcd_is_primary_hcd(hcd) && shared_hcd && HCD_DEFER_RH_REGISTER(shared_hcd)) {
retval = register_root_hub(shared_hcd);
if (retval != 0)
goto err_register_root_hub;
if (shared_hcd->uses_new_polling && HCD_POLL_RH(shared_hcd))
usb_hcd_poll_rh_status(shared_hcd);
}
/* starting here, usbcore will pay attention to this root hub */
if (!HCD_DEFER_RH_REGISTER(hcd)) {
retval = register_root_hub(hcd);
if (retval != 0)
goto err_register_root_hub;
retval = register_root_hub(hcd);
if (retval != 0)
goto err_register_root_hub;
if (hcd->uses_new_polling && HCD_POLL_RH(hcd))
usb_hcd_poll_rh_status(hcd);
}
if (hcd->uses_new_polling && HCD_POLL_RH(hcd))
usb_hcd_poll_rh_status(hcd);
return retval;
@ -3013,7 +2999,6 @@ EXPORT_SYMBOL_GPL(usb_add_hcd);
void usb_remove_hcd(struct usb_hcd *hcd)
{
struct usb_device *rhdev = hcd->self.root_hub;
bool rh_registered;
dev_info(hcd->self.controller, "remove, state %x\n", hcd->state);
@ -3024,7 +3009,6 @@ void usb_remove_hcd(struct usb_hcd *hcd)
dev_dbg(hcd->self.controller, "roothub graceful disconnect\n");
spin_lock_irq (&hcd_root_hub_lock);
rh_registered = hcd->rh_registered;
hcd->rh_registered = 0;
spin_unlock_irq (&hcd_root_hub_lock);
@ -3034,8 +3018,7 @@ void usb_remove_hcd(struct usb_hcd *hcd)
cancel_work_sync(&hcd->died_work);
mutex_lock(&usb_bus_idr_lock);
if (rh_registered)
usb_disconnect(&rhdev); /* Sets rhdev to NULL */
usb_disconnect(&rhdev); /* Sets rhdev to NULL */
mutex_unlock(&usb_bus_idr_lock);
/*

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

@ -692,7 +692,6 @@ int xhci_run(struct usb_hcd *hcd)
if (ret)
xhci_free_command(xhci, command);
}
set_bit(HCD_FLAG_DEFER_RH_REGISTER, &hcd->flags);
xhci_dbg_trace(xhci, trace_xhci_dbg_init,
"Finished xhci_run for USB2 roothub");

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

@ -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

@ -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;

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

@ -124,7 +124,6 @@ struct usb_hcd {
#define HCD_FLAG_RH_RUNNING 5 /* root hub is running? */
#define HCD_FLAG_DEAD 6 /* controller has died? */
#define HCD_FLAG_INTF_AUTHORIZED 7 /* authorize interfaces? */
#define HCD_FLAG_DEFER_RH_REGISTER 8 /* Defer roothub registration */
/* The flags can be tested using these macros; they are likely to
* be slightly faster than test_bit().
@ -135,7 +134,6 @@ struct usb_hcd {
#define HCD_WAKEUP_PENDING(hcd) ((hcd)->flags & (1U << HCD_FLAG_WAKEUP_PENDING))
#define HCD_RH_RUNNING(hcd) ((hcd)->flags & (1U << HCD_FLAG_RH_RUNNING))
#define HCD_DEAD(hcd) ((hcd)->flags & (1U << HCD_FLAG_DEAD))
#define HCD_DEFER_RH_REGISTER(hcd) ((hcd)->flags & (1U << HCD_FLAG_DEFER_RH_REGISTER))
/*
* Specifies if interfaces are authorized by default

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

@ -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;
}

4
redhat/.gitignore vendored
View File

@ -4,5 +4,5 @@ configs/*-merged
kabi/Module.kabi_*
kabi/kabi-current
kabi/kabi-rhel8*
kabi/kabi-rhel8*/*
kabi/kabi-rhel*
kabi/kabi-rhel*/*

View File

@ -1,3 +1,4 @@
GIT ?= git
include Makefile.common
include Makefile.rhpkg
@ -32,8 +33,8 @@ 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)
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 := ..
@ -53,14 +54,8 @@ include Makefile.cross
default: dist-help
dist-python-check:
@if [ ! -f /usr/libexec/platform-python ]; then \
if ! which python3 > /dev/null 2>&1; then \
echo "ERROR: Python 3 is needed." ; \
exit 1; \
fi; \
echo "ERROR: your build environment is not compatible with this distribution."; \
echo "To fix this, run:"; \
echo "ln -s `which python3` /usr/libexec/platform-python"; \
@if [ ! -x /usr/bin/python3 ]; then \
echo "ERROR: Python 3 is needed." ; \
exit 1; \
fi
@ -71,7 +66,7 @@ dist-kabi: dist-python-check
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_whitelist_$$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)
@ -106,7 +101,7 @@ 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_whitelist_$(CURARCH) \
$(REDHAT)/kabi/kabi-current/kabi_stablelist_$(CURARCH) \
$(_OUTPUT) $(KABIDW)/base/$(CURARCH)/
dist-kabi-dw-check: dist-kabi
@ -118,7 +113,7 @@ dist-kabi-dw-check: dist-kabi
fi
@echo "**** GENERATING DWARF-based kABI dataset ****"
@$(KABIDW)/run_kabi-dw.sh generate \
$(REDHAT)/kabi/kabi-current/kabi_whitelist_$(CURARCH) \
$(REDHAT)/kabi/kabi-current/kabi_stablelist_$(CURARCH) \
$(_OUTPUT) $(KABIDW)/base/$(CURARCH).tmp/
@echo "**** KABI DWARF-based comparison report ****"
@$(KABIDW)/run_kabi-dw.sh compare \
@ -134,16 +129,19 @@ 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)
fedora-configs: FLAVOR = fedora
fedora-configs: dist-configs
dist-fedora-configs: FLAVOR = fedora
dist-fedora-configs: dist-configs
fedora-configs: dist-fedora-configs
rh-configs: FLAVOR = rhel
rh-configs: dist-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-configs-prep: dist-clean-configs dist-buildreq-check
cd $(REDHAT)/configs; ./build_configs.sh "partial" "$(ARCH_MACH)" "snip"
cd $(REDHAT)/configs; ./build_configs.sh "$(PACKAGE_NAME)" "$(ARCH_MACH)" "$(FLAVOR)"
dist-configs-arch: ARCH_MACH = $(MACH)
@ -165,7 +163,10 @@ dist-clean-rpmdirs:
rm -rf $$i; \
done;
dist-clean: dist-clean-sources dist-clean-configs dist-clean-rpmdirs
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";
@ -196,16 +197,39 @@ $(KABIDW_TARBALL):
@(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); \
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 \
@ -213,34 +237,35 @@ setup-source: dist-git-version-check dist-clean-sources
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) $(BUILDID)
@$(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/
sources-rh: $(TARBALL)
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)
@git diff --no-renames HEAD > $(TESTPATCH).tmp
@# 1) filterdiff will return crap from the patches it just filtered,
@# that's why egrep is needed so if there're changes under redhat/
@# but not everywhere else, it will be empty just like
@# linux-kernel-test.patch
@# 2) egrep -v will return "1" if it sucessfully removed index and diff
@# lines, which will be considered an error
@($(FILTERDIFF) $(TESTPATCH).tmp | egrep -v "^index|^diff" >$(TESTPATCH).tmp2; true)
@mv $(TESTPATCH).tmp2 $(TESTPATCH).tmp
@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
@cp fedora_files/* $(SOURCES);
@cp rhel_files/* $(SOURCES);
@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 \
keys/*.cer \
configs/partial*.config \
gating.yaml \
rpminspect.yaml \
update_scripts.sh \
mod-blacklist.sh \
kvm_stat.logrotate \
mod-denylist.sh \
mod-internal.list \
mod-sign.sh \
configs/flavors \
@ -248,10 +273,17 @@ sources-rh: $(TARBALL)
configs/merge.pl \
configs/process_configs.sh \
parallel_xz.sh \
generate_bls_conf.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)/; \
@ -262,72 +294,79 @@ sources-rh: $(TARBALL)
fi
@(cd kabi-dwarf && tar cjf $(SOURCES)/$(KABIDW_TARFILE) base run_kabi-dw.sh)
dist-sources: setup-source dist-configs-check dist-kabi dist-kabi-dup sources-rh
dist-sources: dist-kabi dist-kabi-dup sources-rh
dist-test-patch:
@git diff --no-renames HEAD > $(TESTPATCH);
@($(FILTERDIFF) $(TESTPATCH) | egrep -v "^index|^diff" >$(TESTPATCH).tmp; true)
dist-test-patch: generate-testpatch-tmp
@mv $(TESTPATCH).tmp $(TESTPATCH);
dist-all-rpms: 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)" --target $(MACH) -ba $(RPM)/SOURCES/$(PACKAGE_NAME).spec
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-srpm: 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)" --nodeps -bs $(RPM)/SOURCES/$(PACKAGE_NAME).spec
dist-all-rpms: RPMBUILDOPTS=--target $(MACH) -ba
dist-all-rpms: dist-sources do-rpmbuild
dist-srpm-gcov:
make dist-sources BUILDID=".gcov" BUILDOPTS="+gcov"
$(RPMBUILD) --define "_sourcedir $(SOURCES)" --define "_builddir $(RPM)/BUILD" --define "_srcrpmdir $(RPM)/SRPMS" --define "_rpmdir $(RPM)/RPMS" --define "_specdir $(RPM)/SPECS" --define "dist $(DIST)" --nodeps -bs $(RPM)/SOURCES/$(PACKAGE_NAME).spec
dist-srpm: RPMBUILDOPTS=--nodeps -bs
dist-srpm: dist-sources do-rpmbuild
dist-rpms: 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)" --target $(MACH) -bb $(RPM)/SOURCES/$(PACKAGE_NAME).spec
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
$(RPMBUILD) --define "_sourcedir $(SOURCES)" --define "_builddir $(RPM)/BUILD" --define "_srcrpmdir $(RPM)/SRPMS" --define "_rpmdir $(RPM)/RPMS" --define "_specdir $(RPM)/SPECS" --define "dist $(DIST)" --target $(MACH) --with $* --without vdso_install --without perf --without tools -bb $(RPM)/SOURCES/$(PACKAGE_NAME).spec
RPMBUILDOPTS="--target $(MACH) --with $* -bb" make do-rpmbuild
dist-prep: 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)" --nodeps --target noarch -bp $(RPM)/SOURCES/$(PACKAGE_NAME).spec
dist-prep: RPMBUILDOPTS=--nodeps --target noarch -bp
dist-prep: dist-sources do-rpmbuild
dist-perf: 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)" --without up --without smp --without zfcpdump --without debug --without doc --without headers --without --without doc --without debuginfo --target $(MACH) -bb $(RPM)/SOURCES/$(PACKAGE_NAME).spec
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: 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)" --target $(MACH) --without debug --without debuginfo --without vdso_install --without bpftool --without perf --without tools -bb $(RPM)/SOURCES/$(PACKAGE_NAME).spec
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 three ones
# 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 diff-index --quiet HEAD && (echo "Nothing changed, skipping updates"; exit 0) || true
$(REDHAT)/scripts/new_release.sh $(REDHAT) $(__YSTREAM) $(__ZSTREAM); \
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)"; \
@$(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-finish
@$(MAKE) dist-release-changed
dist-release-tag:
@git tag -a -m "$(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE)" $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE)
@$(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 \
@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 || \
@$(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 \
@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)
@$(GIT) checkout $(DIST_BRANCH)
@cd ..; $(REDHAT)/scripts/ci/ark-update-configs.sh $(TAG)
dist-merge-upstream-push: export DIST_PUSH="1"
@ -349,10 +388,10 @@ distg-brew: BUILD_FLAGS ?= $(BREW_FLAGS) $(TEST_FLAGS)
distg-koji: BUILD_FLAGS ?= $(KOJI_FLAGS) $(TEST_FLAGS)
dist-brew dist-koji: dist-%: dist-srpm
$* build $(BUILD_FLAGS) $(BUILD_TARGET) $(SRPMS)/$(PACKAGE_NAME)-$(KVERSION)-$(PKGRELEASE)$(DIST).src.rpm $(OUTPUT_FILE)
$* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) $(SRPMS)/$(PACKAGE_NAME)-$(KVERSION)-$(PKGRELEASE)$(DIST).src.rpm $(OUTPUT_FILE)
distg-brew distg-koji: distg-%:
$* build $(BUILD_FLAGS) $(BUILD_TARGET) "$(RHGITURL)?redhat/koji#$(RHGITCOMMIT)"
$* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) "$(RHGITURL)?redhat/koji#$(RHGITCOMMIT)"
.PHONY: $(REDHAT)/rpm/SOURCES/$(PACKAGE_NAME).spec
$(REDHAT)/rpm/SOURCES/$(PACKAGE_NAME).spec:
@ -366,6 +405,12 @@ 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
@ -381,6 +426,20 @@ dist-get-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.'
@ -464,20 +523,20 @@ dist-full-help:
@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 ' rh-configs - build ELN configs'
@echo ' fedora-configs - build Fedora configs'
@echo ' dist-rhel-configs - build ELN configs'
@echo ' dist-fedora-configs - build Fedora configs'
@echo ''
@echo 'kABI targets:'
@echo ' dist-kabi - Create kABI whitelist files in redhat/kabi/kabi-rhel*/'
@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 whitelisted symbols.'
@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 whitelist.'
@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.'
@ -493,9 +552,11 @@ dist-full-help:
@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 ''

View File

@ -1,49 +1,62 @@
TOPDIR:=$(shell git rev-parse --show-toplevel)
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)
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 ?= 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.
MARKER:=v$(RPMKVERSION).$(RPMKPATCHLEVEL)$(RPMKEXTRAVERSION)
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
DIST ?=.fc33
IS_FEDORA:=$(shell ! echo $(DIST) | grep -q fc; echo $$?)
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.
ifeq ("$(DIST)", ".elrdy")
VERSION_ON_UPSTREAM:=1
else ifeq ("$(IS_FEDORA)", "1")
VERSION_ON_UPSTREAM:=1
else
VERSION_ON_UPSTREAM:=0
ifndef VERSION_ON_UPSTREAM
ifeq ("$(DISTRO)", "fedora")
VERSION_ON_UPSTREAM:=1
else
VERSION_ON_UPSTREAM:=0
endif
endif
ifeq ($(VERSION_ON_UPSTREAM),1)
# master is expected to track mainline.
MERGE_BASE:=$(shell git merge-base HEAD master)
_TAG:=$(shell git describe $(MERGE_BASE))
# 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
@ -62,9 +75,10 @@ ifeq ($(SNAPSHOT),1)
PREBUILD:=0$(KEXTRAVERSION).
RPMKPATCHLEVEL:=$(shell expr $(RPMKPATCHLEVEL) + 1)
endif
# Follow the packaging guidelines to include the date + git snapshot
PREBUILD:=$(PREBUILD)$(shell date +%Y%m%d)git$(MARKER).
UPSTREAM_TARBALL_NAME:=$(shell date +%Y%m%d)git$(MARKER)
# 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
@ -81,29 +95,18 @@ RPM:=$(REDHAT)/rpm
SRPMS:=$(RPM)/SRPMS
SOURCES:=$(RPM)/SOURCES
TESTPATCH:=$(REDHAT)/linux-kernel-test.patch
FILTERDIFF:=/usr/bin/filterdiff -x '*redhat/*' -x '*/.gitignore' -x '*/makefile' -x '*/Makefile'
ARCH_LIST=aarch64 ppc64le s390x x86_64
# 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 ("$(IS_FEDORA)", "1")
ifeq ("$(DISTRO)", "fedora")
SINGLE_TARBALL:=0
else
SINGLE_TARBALL:=1
endif
# RELEASED_KERNEL: swaps between the pre-release secureboot keys and
# the release one, for vmlinux signing.
#
# 0 : pre-release (devel) secureboot keys are used for signing
# 1 : release (RC/GA) secureboot keys are used for signing
#
RELEASED_KERNEL:=0
STAMP_VERSION:=$(KVERSION)
LOCVERFILE:=../localversion
@ -129,7 +132,7 @@ 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-whitelists-$(KVERSION)-$(DISTRO_BUILD).tar.bz2
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)
@ -137,18 +140,19 @@ 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 ("$(IS_FEDORA)", "1")
RHPRODUCT:=master
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 ("$(IS_FEDORA)", "1")
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

View File

@ -1,11 +1,13 @@
# variables that can be overrided by ~/.rhel8git.mk or $(TOPDIR)/.rhel8git.mk
# variables that can be overrided by ~/.rhpkg.mk or $(TOPDIR)/.rhpkg.mk
#
# Command to invoke rhpkg
ifeq ("$(IS_FEDORA)", "1")
ifeq ("$(DISTRO)", "fedora")
RHPKG_BIN:=fedpkg
else ifeq ("$(DISTRO)", "centos")
RHPKG_BIN:=centpkg
else
RHPKG_BIN:=rhpkg-sha512
RHPKG_BIN:=rhpkg
endif
# Kerberos username for pkgs.devel.redhat.com
RHDISTGIT_USER:="$(shell whoami)"
@ -19,12 +21,21 @@ RHDISTGIT_BRANCH:=${RHPRODUCT}
# load configuration, starting with home directory then local
ifeq ("$(RHDISTGIT_CACHE)", "")
ifneq ("$(wildcard ${HOME}/.rhel8git.mk)", "")
include ${HOME}/.rhel8git.mk
ifneq ("$(wildcard ${HOME}/.rhpkg.mk)", "")
include ${HOME}/.rhpkg.mk
endif
ifneq ("$(wildcard $(TOPDIR)/.rhel8git.mk)", "")
include $(TOPDIR)/.rhel8git.mk
ifneq ("$(wildcard $(TOPDIR)/.rhpkg.mk)", "")
include $(TOPDIR)/.rhpkg.mk
endif
endif
RHDISTGIT:="ssh://$(RHDISTGIT_USER)@pkgs.devel.redhat.com/rpms/$(PACKAGE_NAME)"
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 ?= "fedora-5.15"
# 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 ?= linux-5.15.y
# 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:=0
# 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:=1
# 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:=no
# 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

View File

@ -1,5 +1,6 @@
*merged
config-*
kernel*config
partial*config
*.old
*.tmp

View File

@ -41,6 +41,13 @@ 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.

View File

@ -1 +0,0 @@
CONFIG_PAGE_EXTENSION=y

View File

@ -1 +0,0 @@
CONFIG_LOCK_TORTURE_TEST=m

View File

@ -0,0 +1 @@
CONFIG_NVRAM=m

View File

@ -1 +0,0 @@
# CONFIG_ARCH_AGILEX is not set

View File

@ -1 +0,0 @@
# CONFIG_ARCH_ZX is not set

View File

@ -1 +1 @@
# CONFIG_BCMGENET is not set
CONFIG_BCMGENET=m

View File

@ -1 +0,0 @@
# CONFIG_BLK_CGROUP_IOLATENCY is not set

View File

@ -1 +0,0 @@
# CONFIG_BLK_DEV_SKD is not set

View File

@ -1 +0,0 @@
# CONFIG_BLK_DEV_ZONED is not set

View File

@ -0,0 +1 @@
# CONFIG_BRIDGE_NETFILTER is not set

View File

@ -0,0 +1,2 @@
# This CONFIG has been disabled in RHEL by RHEL Engineering. Please contact Red Hat Support for further assistance.
# CONFIG_BRIDGE_NF_EBTABLES is not set

View File

@ -1 +0,0 @@
# CONFIG_BUG_ON_DATA_CORRUPTION is not set

View File

@ -1 +0,0 @@
CONFIG_CAN_LEDS=y

View File

@ -1 +0,0 @@
# CONFIG_CAN_M_CAN is not set

View File

@ -1 +0,0 @@
# CONFIG_CAN_PEAK_PCIEFD is not set

View File

@ -1 +0,0 @@
# CONFIG_CAN_VXCAN is not set

View File

@ -1 +0,0 @@
CONFIG_CAVIUM_PTP=y

View File

@ -1 +0,0 @@
# CONFIG_CRYPTO_CFB is not set

View File

@ -1 +0,0 @@
CONFIG_CRYPTO_CHACHA20_NEON=m

View File

@ -1 +0,0 @@
CONFIG_CRYPTO_CTS=m

View File

@ -1 +0,0 @@
CONFIG_CRYPTO_SM3_ARM64_CE=m

View File

@ -1 +0,0 @@
CONFIG_CRYPTO_SM4_ARM64_CE=m

View File

@ -1 +0,0 @@
CONFIG_CRYPTO_XTS=m

View File

@ -0,0 +1 @@
# CONFIG_DMABUF_HEAPS_CMA is not set

View File

@ -1 +0,0 @@
# CONFIG_DM_VERITY_FEC is not set

View File

@ -1 +0,0 @@
# CONFIG_DRM_AMDGPU_USERPTR is not set

View File

@ -1 +0,0 @@
CONFIG_DRM_LEGACY=y

View File

@ -1 +0,0 @@
CONFIG_DVB_AV7110_IR=y

View File

@ -1 +0,0 @@
CONFIG_ENCRYPTED_KEYS=m

View File

@ -1 +0,0 @@
CONFIG_ENERGY_MODEL=y

Some files were not shown because too many files have changed in this diff Show More