- 17 Aug, 2022 2 commits
-
-
Herton R. Krzesinski authored
MR: !1194 This is a backport of 5.18.14 ALSA changes for RHEL 9.1. Bugzilla: https://bugzilla.redhat.com/2065578 Depends: https://bugzilla.redhat.com/2065572 Signed-off-by:
Jaroslav Kysela <jkysela@redhat.com>
Approved-by: 
Prarit Bhargava <prarit@redhat.com>
Approved-by: 
Tony Camuso <tcamuso@redhat.com>
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
-
Herton R. Krzesinski authored
MR: !920 This is a backport of ALSA changes up to 5.18 kernel for RHEL 9.1. Bugzilla: https://bugzilla.redhat.com/2065572 This upstream patchset updates the ALSA driver code: - ALSA core - ALSA HDA - ALSA USB - ALSA PCI - ALSA SoC (mainly SOF including SoundWire drivers) - Soundwire bus - ALSA Firewire The other components are touched to get things in sync with the current upstream: Some touched drivers are for hardware platforms which are not used in RHEL. The purpose to merge those upstream commits is to keep the future code sync more easy. Signed-off-by:
Jaroslav Kysela <jkysela@redhat.com>
Approved-by: Tony Camuso <tcamuso@redhat.com>
Approved-by: Prarit Bhargava <prarit@redhat.com>
Approved-by: Torez Smith <torez@redhat.com> Signed-off-by:
-
- 16 Aug, 2022 4 commits
-
-
Herton R. Krzesinski authored
Signed-off-by: -
Herton R. Krzesinski authored
MR: !1012 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2072976 Omitted-fix: 6215a5de9e9138fda60f4f1d72f86dd52e4be02b This fix for the mediatek cpufreq driver did not apply and we don't support the mediatek cpufreq driver anyway. I didn't bother finding and applying multiple commits for an unsupported driver. Update most of drivers/cpufreq to match v5.18. The Intel and AMD P-state drivers had already been updated. Signed-off-by:
Mark Langsdorf <mlangsdo@redhat.com> Approved-by:
David Arcari <darcari@redhat.com> Approved-by:
Steve Best <sbest@redhat.com> Approved-by:
Prarit Bhargava <prarit@redhat.com>
Signed-off-by: -
Herton R. Krzesinski authored
MR: !805 BZ: ===== Bugzilla: https://bugzilla.redhat.com/2080656 Upstream: ========== Upstream Status: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git commit 059d9f413efe3ed954e2df37511a4c0e514662f7 Author: Prabhakar Kushwaha <pkushwaha@marvell.com> Date: Sat Apr 30 04:05:13 2022 +0300 qede: Reduce verbosity of ptp tx timestamp Reduce verbosity of ptp tx timestamp error to reduce excessive log messages. Signed-off-by:
Manish Chopra <manishc@marvell.com> Signed-off-by:
Alok Prasad <palok@marvell.com> Signed-off-by:
Ariel Elior <aelior@marvell.com> Signed-off-by:
Prabhakar Kushwaha <pkushwaha@marvell.com> Signed-off-by:
David S. Miller <davem@davemloft.net> Testing: Fix was tested and verified Signed-off-by:
Manish Chopra <mchopra@redhat.com> Approved-by:
Ken Cox <jkc@redhat.com> Approved-by:
Jarod Wilson <jarod@redhat.com>
Approved-by: 
Kamal Heib <kheib@redhat.com>
Approved-by: 
José Ignacio Tornos Martínez <jtornosm@redhat.com>
Signed-off-by: -
Herton R. Krzesinski authored
MR: redhat/centos-stream/src/kernel/centos-stream-9!755 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2041740 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2042261 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2042239 Upstream Status: merged into the linux.git 3 commits are from herbert/cryptodev-2.6.git 1 RHEL-ONLY commit (configs, scripts) Update Marvell OcteonTX2 device drivers to v5.18 upstream. All the patches except one apply cleanly. There is an unrelated upstream commit which results in context differences. RPM build script update is needed to filter new modules properly. Signed-off-by:
Vladis Dronov <vdronov@redhat.com> Approved-by:
Jarod Wilson <jarod@redhat.com>
Approved-by: 
Bruno Meneguele <bmeneg@heredoc.io>
Approved-by: Phil Auld <pauld@redhat.com> Approved-by:
Kamal Heib <kheib@redhat.com>
Signed-off-by:
-
- 10 Aug, 2022 9 commits
-
-
Jan Stancek authored
Signed-off-by:Jan Stancek <jstancek@redhat.com>
-
Jan Stancek authored
MR: !1231 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2115238 Backport stable KVM/x86 fixes since 5.18 rebase. Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com>
Approved-by: Paolo Bonzini <pbonzini@redhat.com> Approved-by:
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Approved-by: 
Bandan Das <bsd@redhat.com>
Signed-off-by: -
Jan Stancek authored
MR: !1227 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2000425 Build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=46953458 Tested by me this is sync for virtio-ring, the other commits for this sync are already merged Signed-off-by:
Cindy Lu <lulu@redhat.com> Approved-by:
Eugenio Pérez <eperezma@redhat.com>
Approved-by: Laurent Vivier <lvivier@redhat.com> Signed-off-by:
-
Jan Stancek authored
MR: !1197 Description: This series of patches pull bug fixes for Chelsio iWARP (iw_cxgb4) driver till 5.19-rc4 Bugzilla: https://bugzilla.redhat.com/2109523 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=46707868 Tested: Sanity testing had been run by Chelsio with above brew build. Upstream Status: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Signed-off-by:
Rahul Lakkireddy <rlakkire@redhat.com> Approved-by:
Jonathan Toppins <jtoppins@redhat.com> Approved-by:
Kamal Heib <kheib@redhat.com>
Approved-by: 
Corinna Vinschen <vinschen@redhat.com>
Signed-off-by: -
Jan Stancek authored
MR: !1196 Description: This series of patches pull bug fixes for Chelsio NIC (cxgb4/cxgb4vf/libcxgb) drivers till 5.19-rc4 Bugzilla: https://bugzilla.redhat.com/2109520 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=46664435 Tested: Sanity testing had been run by Chelsio with above brew build. Upstream Status: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Conflicts: Small conflicts are described in individual patches. Signed-off-by:
Jarod Wilson <jarod@redhat.com>
Approved-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: -
Jan Stancek authored
MR: !1193 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2112378 This shows when a specific driver option is selected but likely may cause other issues as well. Signed-off-by:
Tomas Henzl <thenzl@redhat.com> Approved-by:
Maurizio Lombardi <mlombard@redhat.com> Approved-by:
Ewan D. Milne <emilne@redhat.com> Signed-off-by:
-
Jan Stancek authored
MR: !1190 Bugzilla: https://bugzilla.redhat.com/2112031 Upstream Status: RHEL only Fix a dropped line from MR centos-stream-9/-/merge_requests/421 Fixes: 006ed2d9 ("nvme: code command_id with a genctr for use-after-free validation") Signed-off-by:
John Meneghini <jmeneghi@redhat.com>
Approved-by: Gopal Tiwari <gtiwari@redhat.com> Approved-by:
-
Jan Stancek authored
MR: !1187 ``` Bugzilla: http://bugzilla.redhat.com/2111502 Add additional commits to the bnxt driver for RHEL9.1 Ken Cox (5): eth: bnxt: make ulp_id unsigned to make GCC 12 happy bnxt_en: reclaim max resources if sriov enable fails bnxt_en: Fix bnxt_reinit_after_abort() code path bnxt_en: fix livepatch query bnxt_en: Fix bnxt_refclk_read() drivers/net/ethernet/broadcom/bnxt/bnxt.c | 5 +++-- drivers/net/ethernet/broadcom/bnxt/bnxt.h | 1 + drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 8 +++++--- drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c | 13 +++++++++++-- drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.c | 7 ++++++- drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 12 ++++++------ drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h | 12 ++++++------ 7 files changed, 38 insertions(+), 20 deletions(-) Signed-off-by:
Jarod Wilson <jarod@redhat.com>
Approved-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: -
Jan Stancek authored
MR: !1178 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2037987 Tested: Ethtool, connectivity, netperf. Signed-off-by:
Corinna Vinschen <vinschen@redhat.com>
5be3486e (Lennert Buytenhek)
igc: Reinstate IGC_REMOVED logic and implement it properly
9f8e9fea (Jilin Yuan)
intel/igc:fix repeated words in comments
85f50f59 (Jesse Brandeburg)
intel: remove unused macros
946a2830 (Sasha Neftin)
igc: Change type of the 'igc_check_downshift' method
f5778b2f (Sasha Neftin)
igc: Remove unused phy_type enum
ff02b50a (Sasha Neftin)
igc: Remove igc_set_spd_dplx method
bb519841 (Vinicius Costa Gomes)
igc: Fix suspending when PTM is active
a54fb8ea (Sasha Neftin)
igc: Fix BUG: scheduling while atomic
96774c43 (Sasha Neftin)
igc: Fix infinite loop in release_swfw_sync
54bd15e6 (Sasha Neftin)
igc: igc_write_phy_reg_gpy: drop premature return
1fdd954d (Corinna Vinschen)
igc: igc_read_phy_reg_gpy: drop premature return
dd059e55 (Alexander Lobakin)
igc: don't reserve excessive XDP_PACKET_HEADROOM on XSK Rx to skb
16929c65 (Christophe JAILLET)
igc: Remove useless DMA-32 fallback configuration
b609268d (Alexander Lobakin)
igc: switch to napi_build_skb()
4fdc70ac (Sasha Neftin)
igc: Remove obsolete define
b05cfd57 (Sasha Neftin)
igc: Remove obsolete mask
2b442d10 (Sasha Neftin)
igc: Remove obsolete nvm type
083b0e9a (Sasha Neftin)
igc: Remove unused phy type
ed667bff
(Sasha Neftin)
igc: Remove unused _I_PHY_ID define
drivers/net/ethernet/intel/igc/igc.h | 1 -
drivers/net/ethernet/intel/igc/igc_base.c | 2 -
drivers/net/ethernet/intel/igc/igc_defines.h | 7 ---
drivers/net/ethernet/intel/igc/igc_hw.h | 10 ----
drivers/net/ethernet/intel/igc/igc_i225.c | 13 +++--
drivers/net/ethernet/intel/igc/igc_mac.c | 2 +-
drivers/net/ethernet/intel/igc/igc_main.c | 87 ++++++----------------------
drivers/net/ethernet/intel/igc/igc_phy.c | 24 ++------
drivers/net/ethernet/intel/igc/igc_phy.h | 2 +-
drivers/net/ethernet/intel/igc/igc_ptp.c | 16 ++++-
drivers/net/ethernet/intel/igc/igc_regs.h | 5 +-
11 files changed, 51 insertions(+), 118 deletions(-)
Approved-by: Jarod Wilson <jarod@redhat.com>
Approved-by: 
Jerry Snitselaar <jsnitsel@redhat.com>
Approved-by: Kamal Heib <kheib@redhat.com>
Signed-off-by:
-
- 09 Aug, 2022 3 commits
-
-
Jaroslav Kysela authoredThe commit 5fb5f51185126 ("ASoC: SOF: Intel: hda-loader: add IMR restore support") introduced the fast IMR restore support. The code in 5.18 kernel is incomplete and the full backport of all upstream changes is not trivial. See upstream commit 58ecb11eab44 ("ASoC: SOF: Intel: disable IMR boot when resuming from ACPI S4 and S5 states"). Do not enable IMR boot by default for now. Use a new debug flag to enable this code (as a preview). Upstream status: RHEL-Only BugLink: https://github.com/thesofproject/sof/issues/5892 Signed-off-by:Jaroslav Kysela <jkysela@redhat.com>
Bugzilla: https://bugzilla.redhat.com/2065578 -
Jaroslav Kysela authored
Commit 657774acd00f ("ASoC: SOF: Make sof_suspend/resume IPC agnostic") did not marked ctx_store and ctx_restore as Optional. Fixes: 657774acd00f ("ASoC: SOF: Make sof_suspend/resume IPC agnostic") Signed-off-by:Peter Ujfalusi <peter.ujfalusi@linux.intel.com> Reviewed-by:
Ranjani Sridharan <ranjani.sridharan@linux.intel.com> Reviewed-by:
Bard Liao <yung-chuan.liao@linux.intel.com> Reviewed-by:
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Link: https://lore.kernel.org/r/20220610083549.16773-2-peter.ujfalusi@linux.intel.com
Signed-off-by: Mark Brown <broonie@kernel.org> Author: Peter Ujfalusi <peter.ujfalusi@linux.intel.com> Date: Fri Jun 10 11:35:44 2022 +0300 Signed-off-by:
Jaroslav Kysela <jkysela@redhat.com>
(cherry picked from commit 03f69725749f453b9a4d454a92805f8eb5f095c2)
Bugzilla: https://bugzilla.redhat.com/2065578 -
Jaroslav Kysela authored
We have sanity checks for byte controls and if any of the fail the locally allocated scontrol->ipc_control_data is freed up, but not set to NULL. On a rollback path of the error the higher level code will also try to free the scontrol->ipc_control_data which will eventually going to lead to memory corruption as double freeing memory is not a good thing. Fixes: b5cee8feb1d4 ("ASoC: SOF: topology: Make control parsing IPC agnostic") Reported-by:Seppo Ingalsuo <seppo.ingalsuo@linux.intel.com> Signed-off-by:
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Link: https://lore.kernel.org/r/20220712130103.31514-1-peter.ujfalusi@linux.intel.com
Signed-off-by: Jaroslav Kysela <jkysela@redhat.com>
(cherry picked from commit d5bd47f3ca124058a8e87eae4508afeda2132611)
Bugzilla: https://bugzilla.redhat.com/2065578
-
- 08 Aug, 2022 10 commits
-
-
Jan Stancek authored
Signed-off-by: -
Jan Stancek authored
MR: !1235 Bugzilla: https://bugzilla.redhat.com/2115117 Tested: lvm2-testsuite and cryptsetup tests Upstream Status: kernel/git/torvalds/linux.git Pull in dm bugfixes from upstream Signed-off-by:
Benjamin Marzinski <bmarzins@redhat.com> Approved-by:
Heinz Mauelshagen <heinzm@redhat.com>
Approved-by: 
Mike Snitzer <snitzer@redhat.com>
Approved-by: Mikuláš Patočka <mpatocka@redhat.com> Signed-off-by:
-
Jan Stancek authored
MR: !1234 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2114872 This fixes the handling of the 'noresvport' mount option. Signed-off-by:
Scott Mayhew <smayhew@redhat.com> Approved-by:
Jeffrey Layton <jlayton@redhat.com> Approved-by:
Steve Dickson <steved@redhat.com>
Signed-off-by: -
Jan Stancek authored
MR: !1215 ``` Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2102319 commit 3d092ef09303e615707dc5755cf0e29b4df7555f Author: Corey Minyard <cminyard@mvista.com> Date: Tue Apr 19 12:08:09 2022 -0500 ipmi: When handling send message responses, don't process the message A chunk was dropped when the code handling send messages was rewritten. Those messages shouldn't be processed normally, they are just an indication that the message was successfully sent and the timers should be started for the real response that should be coming later. Add back in the missing chunk to just discard the message and go on. Fixes: 059747c245f0 ("ipmi: Add support for IPMB direct messages") Reported-by:
Joe Wiese <jwiese@rackspace.com> Cc: stable@vger.kernel.org # v5.16+ Signed-off-by:
Corey Minyard <cminyard@mvista.com> Tested-by:
Tony Camuso <tcamuso@redhat.com>
Approved-by: Prarit Bhargava <prarit@redhat.com>
Approved-by: -
Jan Stancek authored
MR: !1205 # Merge Request Required Information ## Summary of Changes This updates the ena driver to upstream v5.18. There is just one commit: 7354a426e063e108c0a3590f13abc77573172576 net: ena: Do not waste napi skb cache ## Approved Bugzilla Ticket Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2097646 Signed-off-by:
Michal Schmidt <mschmidt@redhat.com> Approved-by:
Ivan Vecera <ivecera@redhat.com>
Approved-by: José Ignacio Tornos Martínez <jtornosm@redhat.com>
Approved-by: Corinna Vinschen <vinschen@redhat.com>
Approved-by: Jarod Wilson <jarod@redhat.com>
Approved-by: Kamal Heib <kheib@redhat.com>
Signed-off-by: -
Jan Stancek authored
MR: !1203 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2112431 Since MR !944 was pulled in, booting using DT has failed for the Nvidia Jetson platform. The backport of commit c016baf7dc58 "PM: domains: Add support for 'required-opps' to set default perf state" missed a dependency in drivers/opp which is backported in this MR. Signed-off-by:
Mark Salter <msalter@redhat.com>
Approved-by: 
Myron Stowe <mstowe@redhat.com>
Approved-by: Craig Magina <cmagina@redhat.com> Signed-off-by:
-
Jan Stancek authored
MR: !1179 Bugzilla: https://bugzilla.redhat.com/2101544 [rhkl_cover_letter_centos-stream-9_5.20-scsi-queue_bz2101544](/uploads/dafe327b99bdc6d1c048bc309869c309/rhkl_cover_letter_centos-stream-9_5.20-scsi-queue_bz2101544) Signed-off-by:
Don Brace <dbrace@redhat.com>
Approved-by: Jerry Snitselaar <jsnitsel@redhat.com>
Approved-by: -
Jan Stancek authored
MR: !1158 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2106569 Tested: sanity check with fstests -g auto; sanity check with ltp; SLOB .config; the repr. at [1] selinux-policy without temp fix [2] Conflicts: Minor conflict in xfs_getfsmap() (e811f326) [1]: https://bugzilla.redhat.com/show_bug.cgi?id=2059835#c21 [2]: https://github.com/fedora-selinux/selinux-policy/commit/bca021fb2bdd1ff12313f1273ffa0c9d03befa3c Signed-off-by:
Andrey Albershteyn <aalbersh@redhat.com>
> SELinux capability problem reproduced as:
> 1. git clone git@github.com:fedora-selinux/selinux-policy.git
> 2. git clone git@github.com:containers/container-selinux.git
> 3. cd container-selinux && cp container.* ../selinux-policy/policy/modules/contrib
> 4. cd ../selinux-policy
> 5. git revert bca021fb2bdd1ff12313f1273ffa0c9d03befa3c
> 6. make install-src && make conf && make policy && make install
> 7. semodule -DB
> 8. rm -f /etc/.updated
> 9. reboot
> 10. grep avc /var/log/audit/audit.log | grep denied
Approved-by: Carlos Maiolino <cmaiolino@redhat.com> Approved-by:
Brian Foster <bfoster@redhat.com> Signed-off-by:
-
Jan Stancek authored
MR: !1157 Bugzilla: http://bugzilla.redhat.com/2109000 Upstream Status: git://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git Testing: Perform basic sanity test to delete vports commit 63fa7f2644b4b48e1913af33092c044bf48e9321 Author: Quinn Tran <qutran@marvell.com> Date: Tue Jul 12 22:20:41 2022 -0700 scsi: qla2xxx: Fix imbalance vha->vref_count vref_count took an extra decrement in the task management path. Add an extra ref count to compensate the imbalance. Link: https://lore.kernel.org/r/20220713052045.10683-7-njavali@marvell.com Cc: stable@vger.kernel.org Reviewed-by:
Himanshu Madhani <himanshu.madhani@oracle.com> Signed-off-by:
Quinn Tran <qutran@marvell.com> Signed-off-by:
Nilesh Javali <njavali@marvell.com> Signed-off-by:
Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by:
Nilesh Javali <njavali@redhat.com> Approved-by:
John Meneghini <jmeneghi@redhat.com>
Signed-off-by: -
Jan Stancek authored
MR: !1087 # Merge Request Required Information Prevent possible use-after-free and spreading corruption when working with a corrupted directory. ## Summary of Changes ## Approved Bugzilla Ticket Bugzilla: https://bugzilla.redhat.com/2070213 CVE: CVE-2022 -1184 Signed-off-by:
Lukas Czerner <lczerner@redhat.com>
Approved-by: Pavel Reichl <preichl@redhat.com> Signed-off-by:
-
- 05 Aug, 2022 12 commits
-
-
Patrick Talbert authored
Signed-off-by:Patrick Talbert <ptalbert@redhat.com>
-
Patrick Talbert authored
MR: redhat/centos-stream/src/kernel/centos-stream-9!1222 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2104946 MR: redhat/centos-stream/src/kernel/centos-stream-9!1222 Upstream Status: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=sched/urgent&id=b6e8d40d43ae4dec00c8fea2593eeea3114b8f44 commit b6e8d40d43ae4dec00c8fea2593eeea3114b8f44 Author: Waiman Long <longman@redhat.com> Date: Tue, 2 Aug 2022 21:54:51 -0400 sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed With cgroup v2, the cpuset's cpus_allowed mask can be empty indicating that the cpuset will just use the effective CPUs of its parent. So cpuset_can_attach() can call task_can_attach() with an empty mask. This can lead to cpumask_any_and() returns nr_cpu_ids causing the call to dl_bw_of() to crash due to percpu value access o...
-
Patrick Talbert authored
MR: !1127 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2090231 MR: !1127 CVE: CVE-2022-23816 CVE: CVE-2022-23825 CVE: CVE-2022-29900 CVE: CVE-2022-29901 Depends: https://bugzilla.redhat.com/show_bug.cgi?id=2090254 Omitted-fix: fe83f5eae432 ("Fix SETcc emulation function offsets with SLS") This patch had already been merged as part of MR #762 to rebase KVM x86 to upstream v5.18. Omitted-fix: aa8e73eed7d3 ("crypto: x86/sm3 - Fixup SLS") Centos-stream-9 does have commit 930ab34d906d ("crypto: x86/sm3 - add AVX assembly implementation") and so this fix isn't needed. Omitted-fix: 291073a566b2 ("kvm: fix objtool relocation warning") This patch has been merged as RHEL commit 4d5cccc1 ("kvm: fix objtool relocation warning...
-
Patrick Talbert authored
MR: !1054 # Merge Request Required Information Testing: Tested booting Sapphire Rapids with various intel_iommu options (no kernel parameter, intel_iommu=on, and intel_iommu=on,sm_on). For non-scalable mode cases I verified idxd legacy support functioned with dmatest, and with scalable-mode ran dsa_user_test_runner.sh. ## Summary of Changes The commit a13e10b7 ("dmaengine: idxd: Separate user and kernel pasid enabling"), made a change where iommu_sva_bind_device was now being called whether or not iommu_dev_feature_enable succeeded in enabling the SVA feature. This results in a null pointer deref in iommu_sva_bind_device if intel_iommu hasn't been enabled. With looking further at the commit while trying to determine what the solution should be, I decided that there are potentially more issues with it, and until there is clarification and resolution of the issues upstream I am reverting it. This also pulls in a couple other commits that were fixing up some things, and fixes up an issue that was cleaned up in a merge commit by Linus. ``` Jerry Snitselaar (6): Revert "dmaengine: idxd: Separate user and kernel pasid enabling" dmaengine: idxd: fix device cleanup on disable dmaengine: idxd: add RO check for wq max_batch_size write dmaengine: idxd: add RO check for wq max_transfer_size write dmaengine: idxd: skip clearing device context when device is read-only dmaengine: idxd: Fixup upstream merge conflict resolution ``` ## Approved Bugzilla Ticket All submissions to CentOS Stream must reference an approved ticket in [Red Hat Bugzilla](https://bugzilla.redhat.com/). Please follow the CentOS Stream [contribution documentation](https://wiki.centos.org/Contribute/CentOSStream) for how to file this ticket and have it approved. Bugzilla: https://bugzilla.redhat.com/2100482 Signed-off-by:
Jerry Snitselaar <jsnitsel@redhat.com>
Approved-by: -
Lukas Czerner authoredBugzilla: https://bugzilla.redhat.com/2070213 Tested: xfstests Upstream Status: upstream commit b8a04fe77ef1360fbf73c80fddbdfeaa9407ed1b Author: Lukas Czerner <lczerner@redhat.com> ext4_append() must always allocate a new block, otherwise we run the risk of overwriting existing directory block corrupting the directory tree in the process resulting in all manner of problems later on. Add a sanity check to see if the logical block is already allocated and error out if it is. Cc: stable@kernel.org Signed-off-by:
Lukas Czerner <lczerner@redhat.com>
Reviewed-by: Andreas Dilger <adilger@dilger.ca> Link: https://lore.kernel.org/r/20220704142721.157985-2-lczerner@redhat.com Signed-off-by:
Theodore Ts'o <tytso@mit.edu> Signed-off-by:
Lukas Czerner <lczerner@redhat.com> -
Lukas Czerner authored
Bugzilla: https://bugzilla.redhat.com/2070213 Tested: xfstests Upstream Status: upstream commit 65f8ea4cd57dbd46ea13b41dc8bac03176b04233 Author: Lukas Czerner <lczerner@redhat.com> Currently ext4 directory handling code implicitly assumes that the directory blocks are always within the i_size. In fact ext4_append() will attempt to allocate next directory block based solely on i_size and the i_size is then appropriately increased after a successful allocation. However, for this to work it requires i_size to be correct. If, for any reason, the directory inode i_size is corrupted in a way that the directory tree refers to a valid directory block past i_size, we could end up corrupting parts of the directory tree structure by overwriting already used directory blocks when modifying the directory. Fix it by catching the corruption early in __ext4_read_dirblock(). Addresses Red-Hat-Bugzilla: #2070205 CVE: CVE-2022 -1184 Signed-off-by:
Lukas Czerner <lczerner@redhat.com>
Cc: stable@vger.kernel.org
Reviewed-by: Lukas Czerner <lczerner@redhat.com> -
Vitaly Kuznetsov authoredBugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2115238 Upstream Status: git://git.kernel.org/pub/scm/virt/kvm/kvm.git commit 90752dcef2e3d6c5db0d3cd3809d282918a6eef4 Author: Paolo Bonzini <pbonzini@redhat.com> Date: Thu Aug 4 15:28:32 2022 +0200 KVM: x86: do not report preemption if the steal time cache is stale Commit 7e2175ebd695 ("KVM: x86: Fix recording of guest steal time / preempted status", 2021-11-11) open coded the previous call to kvm_map_gfn, but in doing so it dropped the comparison between the cached guest physical address and the one in the MSR. This cause an incorrect cache hit if the guest modifies the steal time address while the memslots remain the same. This can happen with kexec, in which case the preempted bit is written at the address used by the old kernel instead of the old one. Cc: David Woodhouse <dwmw@amazon.co.uk> Cc: stable@vger.kernel.org Fixes: 7e2175ebd695 ("KVM: x86: Fix recording of guest steal time / preempted status") Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com> -
Vitaly Kuznetsov authored
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2115238 Upstream status: git://git.kernel.org/pub/scm/virt/kvm/kvm.git commit 017edebc86ec0b6eac4f48bdef133180148278c0 Author: Paolo Bonzini <pbonzini@redhat.com> Date: Thu Aug 4 15:28:32 2022 +0200 KVM: x86: revalidate steal time cache if MSR value changes Commit 7e2175ebd695 ("KVM: x86: Fix recording of guest steal time / preempted status", 2021-11-11) open coded the previous call to kvm_map_gfn, but in doing so it dropped the comparison between the cached guest physical address and the one in the MSR. This cause an incorrect cache hit if the guest modifies the steal time address while the memslots remain the same. This can happen with kexec, in which case the steal time data is written at the address used by the old kernel instead of the old one. While at it, rename the variable from gfn to gpa since it is a plain physical address and not a right-shifted one. Reported-by:
Dave Young <ruyang@redhat.com> Reported-by:
Xiaoying Yan <yiyan@redhat.com> Analyzed-by:
Dr. David Alan Gilbert <dgilbert@redhat.com>
Cc: David Woodhouse <dwmw@amazon.co.uk>
Cc: stable@vger.kernel.org
Fixes: 7e2175ebd695 ("KVM: x86: Fix recording of guest steal time / preempted status")
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> -
Vitaly Kuznetsov authored
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2115238 commit 99482726452bdf8be9325199022b17fa6d7d58fe Author: Vitaly Kuznetsov <vkuznets@redhat.com> Date: Tue Jul 12 15:50:09 2022 +0200 KVM: nVMX: Always enable TSC scaling for L2 when it was enabled for L1 Windows 10/11 guests with Hyper-V role (WSL2) enabled are observed to hang upon boot or shortly after when a non-default TSC frequency was set for L1. The issue is observed on a host where TSC scaling is supported. The problem appears to be that Windows doesn't use TSC frequency for its guests even when the feature is advertised and KVM filters SECONDARY_EXEC_TSC_SCALING out when creating L2 controls from L1's. This leads to L2 running with the default frequency (matching host's) while L1 is running with an altered one. Keep SECONDARY_EXEC_TSC_SCALING in secondary exec controls for L2 when it was set for L1. TSC_MULTIPLIER is already correctly computed and written by prepare_vmcs02(). Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com>
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com> Message-Id: <20220712135009.952805-1-vkuznets@redhat.com> Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com> -
Vitaly Kuznetsov authored
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2115238 commit 8a414f943f8b5f94bbaafdec863d6f3dbef33f8a Author: Vitaly Kuznetsov <vkuznets@redhat.com> Date: Fri Jul 8 14:51:47 2022 +0200 KVM: x86: Fully initialize 'struct kvm_lapic_irq' in kvm_pv_kick_cpu_op() 'vector' and 'trig_mode' fields of 'struct kvm_lapic_irq' are left uninitialized in kvm_pv_kick_cpu_op(). While these fields are normally not needed for APIC_DM_REMRD, they're still referenced by __apic_accept_irq() for trace_kvm_apic_accept_irq(). Fully initialize the structure to avoid consuming random stack memory. Fixes: a183b638 ("KVM: x86: make apic_accept_irq tracepoint more generic") Reported-by: syzbot+d6caa905917d353f0d07@syzkaller.appspotmail.com Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com>
Reviewed-by: Sean Christopherson <seanjc@google.com> Message-Id: <20220708125147.593975-1-vkuznets@redhat.com> Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com> -
Vitaly Kuznetsov authored
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2115238 commit 6defa24d3b12bbd418bc8526dea1cbc605265c06 Author: Peter Gonda <pgonda@google.com> Date: Thu Jun 23 10:34:06 2022 -0700 KVM: SEV: Init target VMCBs in sev_migrate_from The target VMCBs during an intra-host migration need to correctly setup for running SEV and SEV-ES guests. Add sev_init_vmcb() function and make sev_es_init_vmcb() static. sev_init_vmcb() uses the now private function to init SEV-ES guests VMCBs when needed. Fixes: 0b020f5af092 ("KVM: SEV: Add support for SEV-ES intra host migration") Fixes: b56639318bb2 ("KVM: SEV: Add support for SEV intra host migration") Signed-off-by:
Peter Gonda <pgonda@google.com> Cc: Marc Orr <marcorr@google.com> Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: Sean Christopherson <seanjc@google.com> Cc: Tom Lendacky <thomas.lendacky@amd.com> Cc: kvm@vger.kernel.org Cc: linux-kernel@vger.kernel.org Message-Id: <20220623173406.744645-1-pgonda@google.com> Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com> -
Vitaly Kuznetsov authored
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2115238 commit 11d39e8cc43e1c6737af19ca9372e590061b5ad2 Author: Maxim Levitsky <mlevitsk@redhat.com> Date: Mon Jun 6 21:11:49 2022 +0300 KVM: SVM: fix tsc scaling cache logic SVM uses a per-cpu variable to cache the current value of the tsc scaling multiplier msr on each cpu. Commit 1ab9287a ("KVM: X86: Add vendor callbacks for writing the TSC multiplier") broke this caching logic. Refactor the code so that all TSC scaling multiplier writes go through a single function which checks and updates the cache. This fixes the following scenario: 1. A CPU runs a guest with some tsc scaling ratio. 2. New guest with different tsc scaling ratio starts on this CPU and terminates almost immediately. This ensures that the short running guest had set the tsc scaling ratio just once when it was set via KVM_SET_TSC_KHZ. Due to the bug, the per-cpu cache is not updated. 3. The original guest continues to run, it doesn't restore the msr value back to its own value, because the cache matches, and thus continues to run with a wrong tsc scaling ratio. Fixes: 1ab9287a ("KVM: X86: Add vendor callbacks for writing the TSC multiplier") Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com>
-
