Select Git revision
Search by author
- Any Author
- authors
-
72162444 72162444 gaochangning
-
Aakash Dave aakash.dave
-
Aaron Kim akim
-
Aaron Kloc akloc
-
Aaron Lan aaron.lan
-
Aaron Nabil aaronna
-
Aaron Pohle aaron.pohle
-
Abbott Chung chung.abbott
-
Abdallah Omar abdallah_omar
-
Abdessamii Chalbi abdessamii.chalbi
-
Abdul Hussain Sirajudeen abdul.hussain
-
Abdullah Alghamdi a.alghamdi
-
Abdullah Elmarghany abdullah_elmarghany
-
Abel Fang abel_fang
-
Abhijeet Badurkar abhijeet.badurkar
-
Abhijit Adsule adsule
-
Abhijit Murthy abhijit
-
Abhi Khanal akhanal
-
Abhilash Sahoo abhilashsahoo
-
Abhimanyu Raj abhimanyu.raj
- Mar 20, 2025
-
-
Augusto Caringi authored
Signed-off-by:Augusto Caringi <acaringi@redhat.com>
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6429 JIRA: https://issues.redhat.com/browse/RHEL-80802 CVE: CVE-2022-49643 ``` commit d2ee2cfc4aa85ff6a2a3b198a3a524ec54e3d999 Author: Huaxin Lu <luhuaxin1@huawei.com> Date: Tue Jul 5 13:14:17 2022 +0800 ima: Fix a potential integer overflow in ima_appraise_measurement When the ima-modsig is enabled, the rc passed to evm_verifyxattr() may be negative, which may cause the integer overflow problem. Fixes: 39b07096 ("ima: Implement support for module-style appended signatures") Signed-off-by:
Huaxin Lu <luhuaxin1@huawei.com> Signed-off-by:
Mimi Zohar <zohar@linux.ibm.com>```> Signed-off-by:
CKI Backport Bot <cki-ci-bot+cki-gitlab-backport-bot@redhat.com> --- <small>Created 2025-02-26 11:32 UTC by backporter - [KWF FAQ](https://red.ht/kernel_workflow_doc) - [Slack #team-kernel-workflow](https://redhat-internal.slack.com/archives/C04LRUPMJQ5) - [Source](https://gitlab.com/cki-project/kernel-workflow/-/blob/main/webhook/utils/backporter.py) - [Documentation](https://gitlab.com/cki-project/kernel-workflow/-/blob/main/docs/README.backporter.md) - [Report an issue](https://gitlab.com/cki-project/kernel-workflow/-/issues/new?issue%5Btitle%5D=backporter%20webhook%20issue)</small > Approved-by:
Coiby Xu <coxu@redhat.com> Approved-by:
Vladis Dronov <vdronov@redhat.com> Approved-by:
CKI KWF Bot <cki-ci-bot+kwf-gitlab-com@redhat.com> Merged-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6588 JIRA: https://issues.redhat.com/browse/RHEL-60023 Tested: Ran the test on s390x and x86-64, with the expected output. Let's make the test also work as expected on architectures that have a different hugepage size than 2 MiB -- such as s390x. While at it, backport the test output cleanup part of the same upstream series. Signed-off-by:
David Hildenbrand <david@redhat.com> Approved-by:
Rafael Aquini <raquini@redhat.com> Approved-by:
mcasquer <mcasquer@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6461 JIRA: https://issues.redhat.com/browse/RHEL-81375 CVE: CVE-2024-57988 ``` commit b88655bc6593c6a7fdc1248b212d17e581c4334e Author: Charles Han <hanchunchao@inspur.com> Date: Fri Dec 27 17:20:46 2024 +0800 Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() devm_kstrdup() can return a NULL pointer on failure,but this returned value in btbcm_get_board_name() is not checked. Add NULL check in btbcm_get_board_name(), to handle kernel NULL pointer dereference error. Fixes: f9183eaad915 ("Bluetooth: btbcm: Use devm_kstrdup()") Signed-off-by:
Charles Han <hanchunchao@inspur.com> Signed-off-by:
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>```> Signed-off-by:
Bastien Nocera <bnocera@redhat.com> Approved-by:
José Ignacio Tornos Martínez <jtornosm@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6522 JIRA: https://issues.redhat.com/browse/RHEL-80985 CVE: CVE-2022-49443 Upstream Status: linux.git commit d679ae94fdd5d3ab00c35078f5af5f37e068b03d Author: Kuniyuki Iwashima <kuniyu@amazon.co.jp> Date: Fri Apr 29 14:38:01 2022 -0700 ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next. Commit bf3b9f63 ("epoll: Add busy poll support to epoll with socket fds.") added the first lockless ep_events_available(), and commit c5a282e9 ("fs/epoll: reduce the scope of wq lock in epoll_wait()") made some ep_events_available() calls lockless and added single call under a lock, finally commit e59d3c64 ("epoll: eliminate unnecessary lock for zero timeout") made the last ep_events_available() lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40 fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281 [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80 fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40 fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281 [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80 fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 -> 0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted: G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Link: https://lkml.kernel.org/r/20220322002653.33865-3-kuniyu@amazon.co.jp Fixes: e59d3c64 ("epoll: eliminate unnecessary lock for zero timeout") Fixes: c5a282e9 ("fs/epoll: reduce the scope of wq lock in epoll_wait()") Fixes: bf3b9f63 ("epoll: Add busy poll support to epoll with socket fds.") Signed-off-by:
Kuniyuki Iwashima <kuniyu@amazon.co.jp> Reported-by:
<syzbot+bdd6e38a1ed5ee58d8bd@syzkaller.appspotmail.com> Cc: Al Viro <viro@zeniv.linux.org.uk>, Andrew Morton <akpm@linux-foundation.org> Cc: Kuniyuki Iwashima <kuniyu@amazon.co.jp> Cc: Kuniyuki Iwashima <kuni1840@gmail.com> Cc: "Soheil Hassas Yeganeh" <soheil@google.com> Cc: Davidlohr Bueso <dave@stgolabs.net> Cc: "Sridhar Samudrala" <sridhar.samudrala@intel.com> Cc: Alexander Duyck <alexander.h.duyck@intel.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Jan Stancek <jstancek@redhat.com> Approved-by:
Waiman Long <longman@redhat.com> Approved-by:
Herton R. Krzesinski <herton@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6456 JIRA: https://issues.redhat.com/browse/RHEL-81268 CVE: CVE-2024-57987 ``` commit 3c15082f3567032d196e8760753373332508c2ca Author: Max Chou <max.chou@realtek.com> Date: Tue Dec 31 14:57:19 2024 +0800 Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() If insert an USB dongle which chip is not maintained in ic_id_table, it will hit the NULL point accessed. Add a null point check to avoid the Kernel Oops. Fixes: b39910bb54d9 ("Bluetooth: Populate hci_set_hw_info for Intel and Realtek") Reviewed-by:
Alex Lu <alex_lu@realsil.com.cn> Signed-off-by:
Max Chou <max.chou@realtek.com> Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6348 Description: ============ This patch set updates the RDMA core and RDMA ULPs to upstream kernel v6.13. Upstream: ========= Linus's master tree. Issues: ======= JIRA: https://issues.redhat.com/browse/RHEL-77880 Brew: ===== https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66571801 Testing: ======== https://beaker.engineering.redhat.com/jobs/10588482 https://beaker.engineering.redhat.com/jobs/10588462 https://beaker.engineering.redhat.com/jobs/10588459 https://beaker.engineering.redhat.com/jobs/10588457 https://beaker.engineering.redhat.com/jobs/10588455 https://beaker.engineering.redhat.com/jobs/10588452 Signed-off-by:
Kamal Heib <kheib@redhat.com> Approved-by:
Ivan Vecera <ivecera@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6442 JIRA: https://issues.redhat.com/browse/RHEL-80989 CVE: CVE-2022-49357 ``` commit 155ca952c7ca19aa32ecfb7373a32bbc2e1ec6eb Author: Aditya Garg <gargaditya08@live.com> Date: Fri Apr 15 17:02:46 2022 +0000 efi: Do not import certificates from UEFI Secure Boot for T2 Macs On Apple T2 Macs, when Linux attempts to read the db and dbx efi variables at early boot to load UEFI Secure Boot certificates, a page fault occurs in Apple firmware code and EFI runtime services are disabled with the following logs: [Firmware Bug]: Page fault caused by firmware at PA: 0xffffb1edc0068000 WARNING: CPU: 3 PID: 104 at arch/x86/platform/efi/quirks.c:735 efi_crash_gracefully_on_page_fault+0x50/0xf0 (Removed some logs from here) Call Trace: <TASK> page_fault_oops+0x4f/0x2c0 ? search_bpf_extables+0x6b/0x80 ? search_module_extables+0x50/0x80 ? search_exception_tables+0x5b/0x60 kernelmode_fixup_or_oops+0x9e/0x110 __bad_area_nosemaphore+0x155/0x190 bad_area_nosemaphore+0x16/0x20 do_kern_addr_fault+0x8c/0xa0 exc_page_fault+0xd8/0x180 asm_exc_page_fault+0x1e/0x30 (Removed some logs from here) ? __efi_call+0x28/0x30 ? switch_mm+0x20/0x30 ? efi_call_rts+0x19a/0x8e0 ? process_one_work+0x222/0x3f0 ? worker_thread+0x4a/0x3d0 ? kthread+0x17a/0x1a0 ? process_one_work+0x3f0/0x3f0 ? set_kthread_struct+0x40/0x40 ? ret_from_fork+0x22/0x30 </TASK> ---[ end trace 1f82023595a5927f ]--- efi: Froze efi_rts_wq and disabled EFI Runtime Services integrity: Couldn't get size: 0x8000000000000015 integrity: MODSIGN: Couldn't get UEFI db list efi: EFI Runtime Services are disabled! integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get UEFI dbx list integrity: Couldn't get size: 0x8000000000000015 integrity: Couldn't get mokx list integrity: Couldn't get size: 0x80000000 So we avoid reading these UEFI variables and thus prevent the crash. Cc: stable@vger.kernel.org Signed-off-by:
Aditya Garg <gargaditya08@live.com> Reviewed-by:
Mimi Zohar <zohar@linux.ibm.com> Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6505 JIRA: https://issues.redhat.com/browse/RHEL-81291 CVE: CVE-2025-21795 Signed-off-by:
Olga Kornievskaia <okorniev@redhat.com> Approved-by:
Benjamin Coddington <bcodding@redhat.com> Approved-by:
Scott Mayhew <smayhew@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6470 JIRA: https://issues.redhat.com/browse/RHEL-81439 CVE: CVE-2024-58012 ``` commit 569922b82ca660f8b24e705f6cf674e6b1f99cc7 Author: Bard Liao <yung-chuan.liao@linux.intel.com> Date: Tue Dec 3 18:48:53 2024 +0800 ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params Each cpu DAI should associate with a widget. However, the topology might not create the right number of DAI widgets for aggregated amps. And it will cause NULL pointer deference. Check that the DAI widget associated with the CPU DAI is valid to prevent NULL pointer deference due to missing DAI widgets in topologies with aggregated amps. Signed-off-by:
Bard Liao <yung-chuan.liao@linux.intel.com> Reviewed-by:
Ranjani Sridharan <ranjani.sridharan@linux.intel.com> Reviewed-by:
Péter Ujfalusi <peter.ujfalusi@linux.intel.com> Reviewed-by:
Liam Girdwood <liam.r.girdwood@intel.com> Link: https://patch.msgid.link/20241203104853.56956-1-yung-chuan.liao@linux.intel.com Signed-off-by:
Mark Brown <broonie@kernel.org>```> Signed-off-by:
Jaroslav Kysela <jkysela@redhat.com> Approved-by:
Tony Camuso <tcamuso@redhat.com> Approved-by:
John W. Linville <linville@redhat.com> Approved-by:
-
Augusto Caringi authored
Merge: CVE-2025-21826: netfilter: nf_tables: reject mismatching sum of field_len with set key length MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6532 JIRA: https://issues.redhat.com/browse/RHEL-82489 CVE: CVE-2025-21826 ``` commit 1b9335a8000fb70742f7db10af314104b6ace220 Author: Pablo Neira Ayuso <pablo@netfilter.org> Date: Tue Jan 28 12:26:33 2025 +0100 netfilter: nf_tables: reject mismatching sum of field_len with set key length The field length description provides the length of each separated key field in the concatenation, each field gets rounded up to 32-bits to calculate the pipapo rule width from pipapo_init(). The set key length provides the total size of the key aligned to 32-bits. Register-based arithmetics still allows for combining mismatching set key length and field length description, eg. set key length 10 and field description [ 5, 4 ] leading to pipapo width of 12. Cc: stable@vger.kernel.org Fixes: 3ce67e3793f4 ("netfilter: nf_tables: do not allow mismatch field size and set key length") Reported-by:
Noam Rathaus <noamr@ssd-disclosure.com> Reviewed-by:
Florian Westphal <fw@strlen.de> Signed-off-by:
Pablo Neira Ayuso <pablo@netfilter.org>```> Signed-off-by:
Florian Westphal <fwestpha@redhat.com> Approved-by:
Xin Long <lxin@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6436 JIRA: https://issues.redhat.com/browse/RHEL-80848 CVE: CVE-2022-49657 ``` commit b55a21b764c1e182014630fa5486d717484ac58f Author: Oliver Neukum <oneukum@suse.com> Date: Tue Jul 5 14:53:51 2022 +0200 usbnet: fix memory leak in error case usbnet_write_cmd_async() mixed up which buffers need to be freed in which error case. v2: add Fixes tag v3: fix uninitialized buf pointer Fixes: 877bd862 ("usbnet: introduce usbnet 3 command helpers") Signed-off-by:
Oliver Neukum <oneukum@suse.com> Link: https://lore.kernel.org/r/20220705125351.17309-1-oneukum@suse.com Signed-off-by:
Jakub Kicinski <kuba@kernel.org>```> Signed-off-by:
Desnes Nunes <desnesn@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6531 JIRA: https://issues.redhat.com/browse/RHEL-82476 CVE: CVE-2024-58075 commit 15589bda46830695a3261518bb7627afac61f519 Author: Chen Ridong <chenridong@huawei.com> Date: Mon Nov 11 01:28:27 2024 +0000 crypto: tegra - do not transfer req when tegra init fails The tegra_cmac_init or tegra_sha_init function may return an error when memory is exhausted. It should not transfer the request when they return an error. Fixes: 0880bb3b00c8 ("crypto: tegra - Add Tegra Security Engine driver") Signed-off-by:
Chen Ridong <chenridong@huawei.com> Acked-by:
Akhil R <akhilrajeev@nvidia.com> Acked-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au>```> Signed-off-by:
Herbert Xu <zxu@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/5856 JIRA: https://issues.redhat.com/browse/RHEL-22697 Signed-off-by:
Aristeu Rozanski <arozansk@redhat.com> Approved-by:
Joel Savitz <jsavitz@redhat.com> Approved-by:
Jiri Dluhos <jdluhos@redhat.com> Approved-by:
-
- Mar 19, 2025
-
-
Jan Stancek authored
This brings all the post-branching changes from 9.6 into c9s, Makefile.rhelver were hunks omitted. Signed-off-by:
-
- Mar 18, 2025
-
-
Aristeu Rozanski authored
JIRA: https://issues.redhat.com/browse/RHEL-22697 Tested: sanity commit f4c0cd1870afd57181e8087c6cf8da3d7fa2cebe Author: John Allen <john.allen@amd.com> Date: Thu Jun 6 20:33:13 2024 +0000 RAS/AMD/FMPM: Use atl internal.h for INVALID_SPA Both the AMD ATL and the FMPM driver define INVALID_SPA. Include the definition from the ATL internal.h header in the FMPM driver. Signed-off-by:
John Allen <john.allen@amd.com> Signed-off-by:
Borislav Petkov (AMD) <bp@alien8.de> Link: https://lore.kernel.org/r/20240606203313.51197-7-john.allen@amd.com Signed-off-by:
-
Aristeu Rozanski authored
JIRA: https://issues.redhat.com/browse/RHEL-22697 Tested: sanity commit e0372d6969bca2bc57e1a24129473694ff65641c Author: John Allen <john.allen@amd.com> Date: Thu Jun 6 20:33:12 2024 +0000 RAS/AMD/ATL: Implement DF 4.5 NP2 denormalization Unlike with previous Data Fabric versions, with Data Fabric 4.5 non-power-of-2 denormalization, there are bits of the system physical address that can't be fully reconstructed from the normalized address. To determine the proper combination of missing system physical address bits, iterate through each possible combination of these bits, normalize the resulting system physical address, and compare to the original address that is being translated. If the addresses match, then the correct permutation of bits has been found. Signed-off-by:
Yazen Ghannam <yazen.ghannam@amd.com> Link: https://lore.kernel.org/r/20240606203313.51197-6-john.allen@amd.com Signed-off-by:
-
Aristeu Rozanski authored
JIRA: https://issues.redhat.com/browse/RHEL-22697 Tested: sanity commit d5811a165caf63a69cd8ae11156b8587cc57d1d1 Author: John Allen <john.allen@amd.com> Date: Thu Jun 6 20:33:11 2024 +0000 RAS/AMD/ATL: Validate address map when information is gathered Validate address maps at the time the information is gathered as the address map will not change during translation. Signed-off-by:
-
Aristeu Rozanski authored
JIRA: https://issues.redhat.com/browse/RHEL-22697 Tested: sanity commit 6cce048cb31f272ca2c9b772cf541715b9ff6ca1 Author: John Allen <john.allen@amd.com> Date: Thu Jun 6 20:33:10 2024 +0000 RAS/AMD/ATL: Expand helpers for adding and removing base and hole The ret_addr field in struct addr_ctx contains the intermediate value of the returned address as it passes through multiple steps in the translation process. Currently, adding the DRAM base and legacy hole is only done once, so it operates directly on the intermediate value. However, for DF 4.5 non-power-of-2 denormalization, adding and removing the DRAM base and legacy hole needs to be done for multiple temporary address values. During this process, the intermediate value should not be lost so the ret_addr value can't be reused. Update the existing 'add' helper to operate on an arbitrary address and introduce a new 'remove' helper to do the inverse operations. Signed-off-by:
-
Aristeu Rozanski authored
JIRA: https://issues.redhat.com/browse/RHEL-22697 Tested: sanity commit 1233aa3fb342ca4e63d398c6a3de8ed32ce796ea Author: John Allen <john.allen@amd.com> Date: Thu Jun 6 20:33:09 2024 +0000 RAS/AMD/ATL: Read DRAM hole base early Read DRAM hole base when constructing the address map as the value will not change during run time. Signed-off-by:
-
Aristeu Rozanski authored
JIRA: https://issues.redhat.com/browse/RHEL-22697 Tested: sanity commit efdbe82a216191d77c8edd5e4dabc7cff7d790d9 Author: John Allen <john.allen@amd.com> Date: Thu Jun 6 20:33:08 2024 +0000 RAS/AMD/ATL: Add amd_atl pr_fmt() prefix Prefix all AMD ATL pr_* statements with "amd_atl:". Signed-off-by:
-
CKI KWF Bot authored
Signed-off-by: -
CKI KWF Bot authored
MR: https://gitlab.com/redhat/rhel/src/kernel/rhel-9/-/merge_requests/3516 Backport and enable the ivpu driver JIRA: https://issues.redhat.com/browse/RHEL-38583 Upstream Status: RHEL only Omitted-fix: f2bc2afe34c107a02ce829a4039e85514feafe55 (backported from 6.12 stable tree version of the same: a468d0585d98466f2faeeb513440fb944c928ff9) Signed-off-by:
Karol Herbst <kherbst@redhat.com> Closes RHEL-38583 Approved-by:
David Airlie <airlied@redhat.com> Approved-by:
Jocelyn Falempe <jfalempe@redhat.com> Approved-by:
-
- Mar 17, 2025
-
-
Augusto Caringi authored
Signed-off-by: -
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6585 This brings all the post-branching changes from 9.6 into c9s. Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/5855 JIRA: https://issues.redhat.com/browse/RHEL-22695 Signed-off-by:
Mark Langsdorf <mlangsdo@redhat.com> Approved-by:
Lenny Szubowicz <lszubowi@redhat.com> Approved-by:
David Arcari <darcari@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6555 Fix data corruption issue in hyperV storvsc driver JIRA: https://issues.redhat.com/browse/RHEL-82537 Signed-off-by:
Cathy Avery <cavery@redhat.com> Approved-by:
Maxim Levitsky <mlevitsk@redhat.com> Approved-by:
Vitaly Kuznetsov <vkuznets@redhat.com> Approved-by:
Ewan D. Milne <emilne@redhat.com> Approved-by:
-
Augusto Caringi authored
Merge: test packetdrill/tcp/cubic/cubic-rack-reo-timeout-retrans-failed-incoming-data.pkt fails on aarch64 using default CONFIG_HZ=100 MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6582 JIRA: https://issues.redhat.com/browse/RHEL-83546 ``` commit 1c2709cfff1dedbb9591e989e2f001484208d914 Author: Neal Cardwell <ncardwell@google.com> Date: Sun Oct 15 13:47:00 2023 -0400 tcp: fix excessive TLP and RACK timeouts from HZ rounding We discovered from packet traces of slow loss recovery on kernels with the default HZ=250 setting (and min_rtt < 1ms) that after reordering, when receiving a SACKed sequence range, the RACK reordering timer was firing after about 16ms rather than the desired value of roughly min_rtt/4 + 2ms. The problem is largely due to the RACK reorder timer calculation adding in TCP_TIMEOUT_MIN, which is 2 jiffies. On kernels with HZ=250, this is 2*4ms = 8ms. The TLP timer calculation has the exact same issue. This commit fixes the TLP transmit timer and RACK reordering timer floor calculation to more closely match the intended 2ms floor even on kernels with HZ=250. It does this by adding in a new TCP_TIMEOUT_MIN_US floor of 2000 us and then converting to jiffies, instead of the current approach of converting to jiffies and then adding th TCP_TIMEOUT_MIN value of 2 jiffies. Our testing has verified that on kernels with HZ=1000, as expected, this does not produce significant changes in behavior, but on kernels with the default HZ=250 the latency improvement can be large. For example, our tests show that for HZ=250 kernels at low RTTs this fix roughly halves the latency for the RACK reorder timer: instead of mostly firing at 16ms it mostly fires at 8ms. Suggested-by:
Eric Dumazet <edumazet@google.com> Signed-off-by:
Neal Cardwell <ncardwell@google.com> Signed-off-by:
Yuchung Cheng <ycheng@google.com> Fixes: bb4d991a ("tcp: adjust tail loss probe timeout") Reviewed-by:
Davide Caratti <dcaratti@redhat.com> Approved-by:
Alessandro Carminati <acarmina@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6422 JIRA: https://issues.redhat.com/browse/RHEL-80660 Signed-off-by:
Steve Best <sbest@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6134 JIRA: https://issues.redhat.com/browse/RHEL-73049 Tested: by me Signed-off-by:
Eder Zulian <ezulian@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6545 ``` JIRA: https://issues.redhat.com/browse/RHEL-47438 Add new VMD Device ID and while at it, include a VMD related bug fix. Signed-off-by:
Myron Stowe <mstowe@redhat.com> ``` Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6513 JIRA: https://issues.redhat.com/browse/RHEL-80832 CVE: CVE-2022-49269 Backport upstream fix for CVE-2022-49269. While at it, backport a few other commits, so that the CVE fix applies cleanly and all commit series are complete. Signed-off-by:
Radu Rendec <rrendec@redhat.com> Approved-by:
Brian Masney <bmasney@redhat.com> Approved-by:
Jared Kangas <jkangas@redhat.com> Approved-by:
Eric Chanudet <echanude@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6511 JIRA: https://issues.redhat.com/browse/RHEL-80215 A small series of fixes for the RHEL9.7 livepatch subsystem. Signed-off-by:
Denis Aleksandrov <daleksan@redhat.com> Approved-by:
Ryan Sullivan <rysulliv@redhat.com> Approved-by:
Joe Lawrence <joe.lawrence@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/5869 JIRA: https://issues.redhat.com/browse/RHEL-52657 Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6476 JIRA: https://issues.redhat.com/browse/RHEL-81472 CVE: CVE-2025-21786 ``` commit e76946110137703c16423baf6ee177b751a34b7e Author: Lai Jiangshan <jiangshan.ljs@antgroup.com> Date: Thu Jan 23 16:25:35 2025 +0800 workqueue: Put the pwq after detaching the rescuer from the pool The commit 68f83057b913("workqueue: Reap workers via kthread_stop() and remove detach_completion") adds code to reap the normal workers but mistakenly does not handle the rescuer and also removes the code waiting for the rescuer in put_unbound_pool(), which caused a use-after-free bug reported by Cheung Wall. To avoid the use-after-free bug, the pool’s reference must be held until the detachment is complete. Therefore, move the code that puts the pwq after detaching the rescuer from the pool. Reported-by:
cheung wall <zzqq0103.hey@gmail.com> Cc: cheung wall <zzqq0103.hey@gmail.com> Link: https://lore.kernel.org/lkml/CAKHoSAvP3iQW+GwmKzWjEAOoPvzeWeoMO0Gz7Pp3_4kxt-RMoA@mail.gmail.com/ Fixes: 68f83057b913("workqueue: Reap workers via kthread_stop() and remove detach_completion") Signed-off-by:
Lai Jiangshan <jiangshan.ljs@antgroup.com> Signed-off-by:
Tejun Heo <tj@kernel.org>```> Signed-off-by:
Phil Auld <pauld@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6249 JIRA: https://issues.redhat.com/browse/RHEL-73892 Tested: by HPE Conflicts: implement numa_valid_node() manually as we don't have it in rhel9 Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6246 JIRA: https://issues.redhat.com/browse/RHEL-70669 CVE: CVE-2024-53241 Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6500 # Merge Request Required Information JIRA: https://issues.redhat.com/browse/RHEL-81911 ## Summary of Changes Re-order code in `event_hist_trigger_func` so that `hist_trigger_enable` is called before `cmd_ops->unreg`, enabling the latter to function correctly and remove a histogram with failed trigger parsing from the list. The patch has been adjusted for two things where RHEL 9's ftrace triggers are behind upstream: - Upstream bugfix commit 6018b585e8c6f ("tracing/histograms: Add histograms to hist_vars if they have referenced variables") which changes the code for detection of the existence of histogram variables is not applied in RHEL 9; I included it in the MR, too. - `event_trigger_register`/`event_trigger_unregister` is not present; `cmd_ops->reg`/`cmd_ops->unreg` is called directly. The patch does not touch this part, but due to the way it was formatted by diff (as removing `event_trigger_register` and restoring it in place of a `tracing_map_init`), manual intervention was needed to make it apply. ## Approved Development Ticket(s) All submissions to CentOS Stream must reference a ticket in [Red Hat Jira](https://issues.redhat.com/). <details><summary>Click for formatting instructions</summary> Please follow the CentOS Stream [contribution documentation](https://docs.centos.org/en-US/stream-contrib/quickstart/ ) for how to file this ticket and have it approved. List tickets each on their own line of this description using the format "Resolves: RHEL-76229", "Related: RHEL-76229" or "Reverts: RHEL-76229", as appropriate. </details> Signed-off-by:
Tomas Glozar <tglozar@redhat.com> Approved-by:
Jerome Marchand <jmarchan@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6399 JIRA: https://issues.redhat.com/browse/RHEL-11707 commit e129fdc599093457648eccf981d672fade55a9c8 Author: Phil Auld <pauld@redhat.com> Date: Tue Jan 14 14:05:25 2025 -0500 Documentation/sysctl: Add timer_migration to kernel.rst There is no mention of timer_migration in the docs. Add a short description. Signed-off-by:
Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250114190525.169022-1-pauld@redhat.com Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6402 JIRA: https://issues.redhat.com/browse/RHEL-80104 Upstream Status: commit 631a4b3ddc78 Updated nft_queue.sh kselftest can trigger a WARN splat. Note that upstream "Fixes" tag is incorrect, the problem does exist in 9.x releases. Signed-off-by:
Hangbin Liu <haliu@redhat.com> Approved-by:
Antoine Tenart <atenart@redhat.com> Approved-by:
-
