Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
g was tagged in special file, during lookup(), when f2fs runs into __recover_dot_dentries(), it will cause NULL pointer access once f2fs_add_regular_entry() calls a_ops->set_dirty_page(). References: - https://git.kernel.org/stable/c/250e5a6be52a6b9d82fe91976c83cc158868b4e9 - https://git.kernel.org/stable/c/34f48ce5d5936eea33e3b6415403e57eb84aff97 - https://git.kernel.org/stable/c/2f46160d0a19b13bfe96c0dd50eed5c5d253ab7a - https://git.kernel.org/stable/c/12662d19467b391b5b509ac5e9ab4f583c6dde16
CVE ID: CVE-2022-49429 State: PUBLISHED Published: 2025-02-26T02:12:48.646Z Last Updated: 2025-05-04T08:37:29.046Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent panic when SDMA is disabled If the hfi1 module is loaded with HFI1_CAP_SDMA off, a call to hfi1_write_iter() will dereference a NULL pointer and panic. A typical stack frame is: sdma_select_user_engine [hfi1] hfi1_user_sdma_process_request [hfi1] hfi1_write_iter [hfi1] do_iter_readv_writev do_iter_write vfs_writev do_writev do_syscall_64 The fix is to test for SDMA in hfi1_write_iter() and fail the I/O with EINVAL. References: - https://git.kernel.or
ll_64 The fix is to test for SDMA in hfi1_write_iter() and fail the I/O with EINVAL. References: - https://git.kernel.org/stable/c/33794e8e9bcb4affc0ebff9cdec85acc8b8a1762 - https://git.kernel.org/stable/c/0e4dda8b3f4c07ee9ea670a10ea3171a5e63a86f - https://git.kernel.org/stable/c/e60ad83f645ee6fadd5a8057ba267aeec54f08fe - https://git.kernel.org/stable/c/cc80d3c37cec9d6ddb140483647901bc7cc6c31d - https://git.kernel.org/stable/c/32e6aea33944f364d51cd263e4cd236393a188b6 - https://git.kernel.org/stable/c/29952ab85d6c3fe0b7909d9a737f10c58bf6824d - https://git.kernel.org/stable/c/22e7e400fd1a890db2ea13686324aff50e972f4f - https://git.kernel.org/stable/c/629e052d0c98e46dde9f0824f0aa437f678d9b8f
CVE ID: CVE-2022-49430 State: PUBLISHED Published: 2025-02-26T02:12:49.114Z Last Updated: 2025-05-04T08:37:30.249Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: Input: gpio-keys - cancel delayed work only in case of GPIO gpio_keys module can either accept gpios or interrupts. The module initializes delayed work in case of gpios only and is only used if debounce timer is not used, so make sure cancel_delayed_work_sync() is called only when its gpio-backed and debounce_use_hrtimer is false. This fixes the issue seen below when the gpio_keys module is unloaded and an interrupt pin is used instead of GPIO: [ 360.297569] ----------
seen below when the gpio_keys module is unloaded and an interrupt pin is used instead of GPIO: [ 360.297569] ------------[ cut here ]------------ [ 360.302303] WARNING: CPU: 0 PID: 237 at kernel/workqueue.c:3066 __flush_work+0x414/0x470 [ 360.310531] Modules linked in: gpio_keys(-) [ 360.314797] CPU: 0 PID: 237 Comm: rmmod Not tainted 5.18.0-rc5-arm64-renesas-00116-g73636105874d-dirty #166 [ 360.324662] Hardware name: Renesas SMARC EVK based on r9a07g054l2 (DT) [ 360.331270] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 360.338318] pc : __flush_work+0x414/0x470 [ 360.342385] lr : __cancel_work_timer+0x140/0x1b0 [ 360.347065] sp : ffff80000a7fba00 [ 360.350423] x29: ffff8
14/0x470 [ 360.342385] lr : __cancel_work_timer+0x140/0x1b0 [ 360.347065] sp : ffff80000a7fba00 [ 360.350423] x29: ffff80000a7fba00 x28: ffff000012b9c5c0 x27: 0000000000000000 [ 360.357664] x26: ffff80000a7fbb80 x25: ffff80000954d0a8 x24: 0000000000000001 [ 360.364904] x23: ffff800009757000 x22: 0000000000000000 x21: ffff80000919b000 [ 360.372143] x20: ffff00000f5974e0 x19: ffff00000f5974e0 x18: ffff8000097fcf48 [ 360.379382] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000053f40 [ 360.386622] x14: ffff800009850e88 x13: 0000000000000002 x12: 000000000000a60c [ 360.393861] x11: 000000000000a610 x10: 0000000000000000 x9 : 0000000000000008 [ 360.401100] x8 : 0101010101010101 x7 : 000
0.393861] x11: 000000000000a610 x10: 0000000000000000 x9 : 0000000000000008 [ 360.401100] x8 : 0101010101010101 x7 : 00000000a473c394 x6 : 0080808080808080 [ 360.408339] x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffff80000919b458 [ 360.415578] x2 : ffff8000097577f0 x1 : 0000000000000001 x0 : 0000000000000000 [ 360.422818] Call trace: [ 360.425299] __flush_work+0x414/0x470 [ 360.429012] __cancel_work_timer+0x140/0x1b0 [ 360.433340] cancel_delayed_work_sync+0x10/0x18 [ 360.437931] gpio_keys_quiesce_key+0x28/0x58 [gpio_keys] [ 360.443327] devm_action_release+0x10/0x18 [ 360.447481] release_nodes+0x8c/0x1a0 [ 360.451194] devres_release_all+0x90/0x100 [ 360.455346] device_unbind_cleanup+0x1
360.447481] release_nodes+0x8c/0x1a0 [ 360.451194] devres_release_all+0x90/0x100 [ 360.455346] device_unbind_cleanup+0x14/0x60 [ 360.459677] device_release_driver_internal+0xe8/0x168 [ 360.464883] driver_detach+0x4c/0x90 [ 360.468509] bus_remove_driver+0x54/0xb0 [ 360.472485] driver_unregister+0x2c/0x58 [ 360.476462] platform_driver_unregister+0x10/0x18 [ 360.481230] gpio_keys_exit+0x14/0x828 [gpio_keys] [ 360.486088] __arm64_sys_delete_module+0x1e0/0x270 [ 360.490945] invoke_syscall+0x40/0xf8 [ 360.494661] el0_svc_common.constprop.3+0xf0/0x110 [ 360.499515] do_el0_svc+0x20/0x78 [ 360.502877] el0_svc+0x48/0xf8 [ 360.505977] el0t_64_sync_handler+0x88/0xb0 [ 360.510216] el0t_64_sync+0x148/0x14
/0x78 [ 360.502877] el0_svc+0x48/0xf8 [ 360.505977] el0t_64_sync_handler+0x88/0xb0 [ 360.510216] el0t_64_sync+0x148/0x14c [ 360.513930] irq event stamp: 4306 [ 360.517288] hardirqs last enabled at (4305): [<ffff8000080b0300>] __cancel_work_timer+0x130/0x1b0 [ 360.526359] hardirqs last disabled at (4306): [<ffff800008d194fc>] el1_dbg+0x24/0x88 [ 360.534204] softirqs last enabled at (4278): [<ffff8000080104a0>] _stext+0x4a0/0x5e0 [ 360.542133] softirqs last disabled at (4267): [<ffff8000080932ac>] irq_exit_rcu+0x18c/0x1b0 [ 360.550591] ---[ end trace 0000000000000000 ]--- References: - https://git.kernel.org/stable/c/96c460687813915dedca9dd7d04ae0e90607fd79 - https://git.kernel.org/stable/c/41
erences: - https://git.kernel.org/stable/c/96c460687813915dedca9dd7d04ae0e90607fd79 - https://git.kernel.org/stable/c/4160e09619086fc155b51ccdb3462a3f233a5f4b - https://git.kernel.org/stable/c/8b1ae300c2953257c146b5f0757537935c0b6027 - https://git.kernel.org/stable/c/cee409bbba0d1bd3fb73064fb480ff365f453b5d
CVE ID: CVE-2022-49431 State: PUBLISHED Published: 2025-02-26T02:12:49.592Z Last Updated: 2025-05-04T08:37:31.350Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Add missing of_node_put in iommu_init_early_dart The device_node pointer is returned by of_find_compatible_node with refcount incremented. We should use of_node_put() to avoid the refcount leak. References: - https://git.kernel.org/stable/c/cb4f2dc513e99c5d0485661f114e4dda73612d10 - https://git.kernel.org/stable/c/dfc308d6f29aa28463deb9a12278a85a382385ca - https://git.kernel.org/stable/c/df6d8b689252c0acc0448d4ae3d33f2d6db048ab - https://git.kernel.org/s
a12278a85a382385ca - https://git.kernel.org/stable/c/df6d8b689252c0acc0448d4ae3d33f2d6db048ab - https://git.kernel.org/stable/c/8657e8ea23325949091da72453ba84fb73cc2bd9 - https://git.kernel.org/stable/c/7e3f1dfb9e21733d7276bc9ccea4daada163f2ba - https://git.kernel.org/stable/c/57b742a5b8945118022973e6416b71351df512fb
CVE ID: CVE-2022-49432 State: PUBLISHED Published: 2025-02-26T02:12:50.073Z Last Updated: 2025-05-04T08:37:32.456Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/xics: fix refcount leak in icp_opal_init() The of_find_compatible_node() function returns a node pointer with refcount incremented, use of_node_put() on it when done. References: - https://git.kernel.org/stable/c/977dbc81d0f866ef63b93c127b7404f07734b3cc - https://git.kernel.org/stable/c/53f3f7f73e609b934083f896cb7ca2c2cb009b9f - https://git.kernel.org/stable/c/1d5c8cea85fb1680eae8d645b96b92146cb4633c - https://git.kernel.org/stable/c/537a317e5ff45d1f5a0ecaf6a0d
rnel.org/stable/c/1d5c8cea85fb1680eae8d645b96b92146cb4633c - https://git.kernel.org/stable/c/537a317e5ff45d1f5a0ecaf6a0d7c8043c878cb1 - https://git.kernel.org/stable/c/6a61a97106279c2aa16fbbb2a171fd5dde127d23 - https://git.kernel.org/stable/c/df802880a7f9cd96b921b00639b00871f18a9a57 - https://git.kernel.org/stable/c/2357bd7499a81c70b460e2191852bbfc7b63c354 - https://git.kernel.org/stable/c/9a42bc2494fadb453de00ce61042e588563ddc6d - https://git.kernel.org/stable/c/5dd9e27ea4a39f7edd4bf81e9e70208e7ac0b7c9
CVE ID: CVE-2022-49433 State: PUBLISHED Published: 2025-02-26T02:12:50.553Z Last Updated: 2025-05-04T08:37:33.881Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent use of lock before it is initialized If there is a failure during probe of hfi1 before the sdma_map_lock is initialized, the call to hfi1_free_devdata() will attempt to use a lock that has not been initialized. If the locking correctness validator is on then an INFO message and stack trace resembling the following may be seen: INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this o
trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validator. Call Trace: register_lock_class+0x11b/0x880 __lock_acquire+0xf3/0x7930 lock_acquire+0xff/0x2d0 _raw_spin_lock_irq+0x46/0x60 sdma_clean+0x42a/0x660 [hfi1] hfi1_free_devdata+0x3a7/0x420 [hfi1] init_one+0x867/0x11a0 [hfi1] pci_device_probe+0x40e/0x8d0 The use of sdma_map_lock in sdma_clean() is for freeing the sdma_map memory, and sdma_map is not allocated/initialized until after sdma_map_lock has been initialized. This code only needs to be run if sdma_map is not NULL, and so checking for that condition will avo
as been initialized. This code only needs to be run if sdma_map is not NULL, and so checking for that condition will avoid trying to use the lock before it is initialized. References: - https://git.kernel.org/stable/c/66090815a24ce14cf51ef5453fc0218fe8a39bc2 - https://git.kernel.org/stable/c/addb192000d8819c0b1553453994df9bb54c28db - https://git.kernel.org/stable/c/fc0750e659db7b315bf6348902cc8ca3cdd4b8d8 - https://git.kernel.org/stable/c/ca55150bff5817af4f857a746ecab9862c23e12a - https://git.kernel.org/stable/c/30eb275e7ed588270ae159cc590a96658e0cfd8f - https://git.kernel.org/stable/c/288d198f50434f29b4a26a9de4394ae2305ad8af - https://git.kernel.org/stable/c/05c03dfd09c069c4ffd783b47b2da5dc
org/stable/c/288d198f50434f29b4a26a9de4394ae2305ad8af - https://git.kernel.org/stable/c/05c03dfd09c069c4ffd783b47b2da5dcc9421f2c
CVE ID: CVE-2022-49434 State: PUBLISHED Published: 2025-02-26T02:12:51.068Z Last Updated: 2025-05-04T08:37:35.051Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() The sysfs sriov_numvfs_store() path acquires the device lock before the config space access lock: sriov_numvfs_store device_lock # A (1) acquire device lock sriov_configure vfio_pci_sriov_configure # (for example) vfio_pci_core_sriov_configure pci_disable_sriov sriov_disable pci_cfg_access_lock pci_wait_cfg # B (4) wait for dev->block_cfg_access == 0 Previously, pci_dev_lock() acquired the config space
cess_lock pci_wait_cfg # B (4) wait for dev->block_cfg_access == 0 Previously, pci_dev_lock() acquired the config space access lock before the device lock: pci_dev_lock pci_cfg_access_lock dev->block_cfg_access = 1 # B (2) set dev->block_cfg_access = 1 device_lock # A (3) wait for device lock Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may deadlock with sriov_numvfs_store() if the operations occur in the sequence (1) (2) (3) (4). Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires the device lock before the config space access lock, the same as the sriov_numvfs_store() path. [bhelgaas: combined and adapted commit log from Jay Zhou's independent subse
the same as the sriov_numvfs_store() path. [bhelgaas: combined and adapted commit log from Jay Zhou's independent subsequent posting: https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com] References: - https://git.kernel.org/stable/c/da9792920ab525b8a932aa9aeee34529ad7b83f7 - https://git.kernel.org/stable/c/c3c6dc1853b8bf3c718f96fd8480a6eb09ba4831 - https://git.kernel.org/stable/c/aed6d4d519210c28817948f34c53b6e058e0456c - https://git.kernel.org/stable/c/c9a81f9ed6ae3554621d6a50220b1bc74b67d81e - https://git.kernel.org/stable/c/eff3587b9c01439b738298475e555c028ac9f55e - https://git.kernel.org/stable/c/2cdd5284035322795b0964f899eefba254cfe483 - https://git.kernel.org/stabl
555c028ac9f55e - https://git.kernel.org/stable/c/2cdd5284035322795b0964f899eefba254cfe483 - https://git.kernel.org/stable/c/ea047f51172aa68841adef7f52d375002438b8f0 - https://git.kernel.org/stable/c/59ea6b3ae51df7cd6bfd84c9c0030609b9315622 - https://git.kernel.org/stable/c/a91ee0e9fca9d7501286cfbced9b30a33e52740a
CVE ID: CVE-2022-49435 State: PUBLISHED Published: 2025-02-26T02:12:51.554Z Last Updated: 2025-05-04T08:37:36.380Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mfd: davinci_voicecodec: Fix possible null-ptr-deref davinci_vc_probe() It will cause null-ptr-deref when using 'res', if platform_get_resource() returns NULL, so move using 'res' after devm_ioremap_resource() that will check it to avoid null-ptr-deref. And use devm_platform_get_and_ioremap_resource() to simplify code. References: - https://git.kernel.org/stable/c/49c1e32e7b3f301642a60448700ec531df981269 - https://git.kernel.org/stable/c/a1d4941d9a24999f680799f9bbde7f5
.org/stable/c/49c1e32e7b3f301642a60448700ec531df981269 - https://git.kernel.org/stable/c/a1d4941d9a24999f680799f9bbde7f57351ca637 - https://git.kernel.org/stable/c/5289795824b77489803b0802cd9edc13824a2d0b - https://git.kernel.org/stable/c/2d00158a06efe6bbcd020108634ea0f2ed8b32f7 - https://git.kernel.org/stable/c/579944b9f38727d9ff570b58f83bc424e8af8398 - https://git.kernel.org/stable/c/311242c7703df0da14c206260b7e855f69cb0264
CVE ID: CVE-2022-49436 State: PUBLISHED Published: 2025-02-26T02:12:52.044Z Last Updated: 2025-05-04T08:37:37.674Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/papr_scm: Fix leaking nvdimm_events_map elements Right now 'char *' elements allocated for individual 'stat_id' in 'papr_scm_priv.nvdimm_events_map[]' during papr_scm_pmu_check_events(), get leaked in papr_scm_remove() and papr_scm_pmu_register(), papr_scm_pmu_check_events() error paths. Also individual 'stat_id' arent NULL terminated 'char *' instead they are fixed 8-byte sized identifiers. However papr_scm_pmu_register() assumes it to be a NULL terminated 'ch
instead they are fixed 8-byte sized identifiers. However papr_scm_pmu_register() assumes it to be a NULL terminated 'char *' and at other places it assumes it to be a 'papr_scm_perf_stat.stat_id' sized string which is 8-byes in size. Fix this by allocating the memory for papr_scm_priv.nvdimm_events_map to also include space for 'stat_id' entries. This is possible since number of available events/stat_ids are known upfront. This saves some memory and one extra level of indirection from 'nvdimm_events_map' to 'stat_id'. Also rest of the code can continue to call 'kfree(papr_scm_priv.nvdimm_events_map)' without needing to iterate over the array and free up individual elements. References: - ht
scm_priv.nvdimm_events_map)' without needing to iterate over the array and free up individual elements. References: - https://git.kernel.org/stable/c/b073096df4dec70d0436321b7093bad27ae91f9e - https://git.kernel.org/stable/c/0e0946e22f3665d27325d389ff45ade6e93f3678
CVE ID: CVE-2022-49437 State: PUBLISHED Published: 2025-02-26T02:12:52.524Z Last Updated: 2025-10-01T19:46:49.892Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: Fix refcount leak in xive_spapr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/65f11ccdd746e0e7f0b469cc989ba43d4f30ecfe - https://git.kernel.org/stable/c/6e806485d851986a2445267608f27cb4ba2ed774 - https://git.kernel.org/stable/c/cc62
30ecfe - https://git.kernel.org/stable/c/6e806485d851986a2445267608f27cb4ba2ed774 - https://git.kernel.org/stable/c/cc62dde2a5f4ba14016fd9caec76f08d388f4b9c - https://git.kernel.org/stable/c/1d1fb9618bdd5a5fbf9a9eb75133da301d33721c
CVE ID: CVE-2022-49438 State: PUBLISHED Published: 2025-02-26T02:12:53.007Z Last Updated: 2025-10-01T19:46:49.766Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: Input: sparcspkr - fix refcount leak in bbc_beep_probe of_find_node_by_path() calls of_find_node_opts_by_path(), which returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/2f51db16cb740ff90086189a1ef2581eab665591 - https://git.kernel.org/stable/c/f13064b0f2c651a3fbb0749932795c6fd2155
table/c/2f51db16cb740ff90086189a1ef2581eab665591 - https://git.kernel.org/stable/c/f13064b0f2c651a3fbb0749932795c6fd21556a8 - https://git.kernel.org/stable/c/353bc58ac6c782d4dcde9136a91d1f90867938fe - https://git.kernel.org/stable/c/bbc2b0ce6042dd3117827f10ea8cb67e0ab786da - https://git.kernel.org/stable/c/6e07ccc7d56130f760d23f67a70c45366c07debc - https://git.kernel.org/stable/c/418b6a3e12f75638abc5673eb76cb32127d0ab13 - https://git.kernel.org/stable/c/73d6f42d8d86648bec2e73d34fe1648cb6d23e08 - https://git.kernel.org/stable/c/1124e39fea0e2fdb4202f95b716cb97cc7de7cc7 - https://git.kernel.org/stable/c/c8994b30d71d64d5dcc9bc0edbfdf367171aa96f
CVE ID: CVE-2022-49439 State: PUBLISHED Published: 2025-02-26T02:12:53.490Z Last Updated: 2025-10-01T19:46:49.627Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/fsl_rio: Fix refcount leak in fsl_rio_setup of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/51e25fbf20c9152d84a34b7afac15a41fe5c9116 - https://git.kernel.org/stable/c/5b8aa2ba38c010f47c965dd9bb5a8561813ed649 - https://git.kernel.org/stable/
5a41fe5c9116 - https://git.kernel.org/stable/c/5b8aa2ba38c010f47c965dd9bb5a8561813ed649 - https://git.kernel.org/stable/c/bcb6c4c5eb4836a21411dfe8247bf9951eb6e7c3 - https://git.kernel.org/stable/c/46fd994763cf6884b88a2da712af918f3ed54d7b - https://git.kernel.org/stable/c/7b668a59ddfb32727e39b06fdf52b28e58c684e0 - https://git.kernel.org/stable/c/c70dd353d37158e06bf8d450d4b31a7091609924 - https://git.kernel.org/stable/c/5607a77a365df8c0fd5ff43ac424812b95775527 - https://git.kernel.org/stable/c/fcee96924ba1596ca80a6770b2567ca546f9a482
CVE ID: CVE-2022-49440 State: PUBLISHED Published: 2025-02-26T02:12:53.988Z Last Updated: 2025-05-04T08:37:42.677Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas: Keep MSR[RI] set when calling RTAS RTAS runs in real mode (MSR[DR] and MSR[IR] unset) and in 32-bit big endian mode (MSR[SF,LE] unset). The change in MSR is done in enter_rtas() in a relatively complex way, since the MSR value could be hardcoded. Furthermore, a panic has been reported when hitting the watchdog interrupt while running in RTAS, this leads to the following stack trace: watchdog: CPU 24 Hard LOCKUP watchdog: CPU 24 TB:997512652051031, last he
RTAS, this leads to the following stack trace: watchdog: CPU 24 Hard LOCKUP watchdog: CPU 24 TB:997512652051031, last heartbeat TB:997504470175378 (15980ms ago) ... Supported: No, Unreleased kernel CPU: 24 PID: 87504 Comm: drmgr Kdump: loaded Tainted: G E X 5.14.21-150400.71.1.bz196362_2-default #1 SLE15-SP4 (unreleased) 0d821077ef4faa8dfaf370efb5fdca1fa35f4e2c NIP: 000000001fb41050 LR: 000000001fb4104c CTR: 0000000000000000 REGS: c00000000fc33d60 TRAP: 0100 Tainted: G E X (5.14.21-150400.71.1.bz196362_2-default) MSR: 8000000002981000 <SF,VEC,VSX,ME> CR: 48800002 XER: 20040020 CFAR: 000000000000011c IRQMASK: 1 GPR00: 0000000000000003 ffffffffffffffff 0000000000000001 00000000000050dc GPR04:
020 CFAR: 000000000000011c IRQMASK: 1 GPR00: 0000000000000003 ffffffffffffffff 0000000000000001 00000000000050dc GPR04: 000000001ffb6100 0000000000000020 0000000000000001 000000001fb09010 GPR08: 0000000020000000 0000000000000000 0000000000000000 0000000000000000 GPR12: 80040000072a40a8 c00000000ff8b680 0000000000000007 0000000000000034 GPR16: 000000001fbf6e94 000000001fbf6d84 000000001fbd1db0 000000001fb3f008 GPR20: 000000001fb41018 ffffffffffffffff 000000000000017f fffffffffffff68f GPR24: 000000001fb18fe8 000000001fb3e000 000000001fb1adc0 000000001fb1cf40 GPR28: 000000001fb26000 000000001fb460f0 000000001fb17f18 000000001fb17000 NIP [000000001fb41050] 0x1fb41050 LR [000000001fb4104c] 0x1fb4
b26000 000000001fb460f0 000000001fb17f18 000000001fb17000 NIP [000000001fb41050] 0x1fb41050 LR [000000001fb4104c] 0x1fb4104c Call Trace: Instruction dump: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX Oops: Unrecoverable System Reset, sig: 6 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries ... Supported: No, Unreleased kernel CPU: 24 PID: 87504 Comm: drmgr Kdump: loaded Tainted: G E X 5.14.21-150400.71.1.bz196362_2-default #1 SLE15-SP4 (unreleased) 0d821077ef4faa8dfaf370efb5fdca1fa35f4e2c NIP: 000000001fb41050 LR: 000000001fb4104c CTR: 0000000000000000 REGS: c00000000fc33d60 TRAP: 01
af370efb5fdca1fa35f4e2c NIP: 000000001fb41050 LR: 000000001fb4104c CTR: 0000000000000000 REGS: c00000000fc33d60 TRAP: 0100 Tainted: G E X (5.14.21-150400.71.1.bz196362_2-default) MSR: 8000000002981000 <SF,VEC,VSX,ME> CR: 48800002 XER: 20040020 CFAR: 000000000000011c IRQMASK: 1 GPR00: 0000000000000003 ffffffffffffffff 0000000000000001 00000000000050dc GPR04: 000000001ffb6100 0000000000000020 0000000000000001 000000001fb09010 GPR08: 0000000020000000 0000000000000000 0000000000000000 0000000000000000 GPR12: 80040000072a40a8 c00000000ff8b680 0000000000000007 0000000000000034 GPR16: 000000001fbf6e94 000000001fbf6d84 000000001fbd1db0 000000001fb3f008 GPR20: 000000001fb41018 ffffffffffffffff 000000
R16: 000000001fbf6e94 000000001fbf6d84 000000001fbd1db0 000000001fb3f008 GPR20: 000000001fb41018 ffffffffffffffff 000000000000017f fffffffffffff68f GPR24: 000000001fb18fe8 000000001fb3e000 000000001fb1adc0 000000001fb1cf40 GPR28: 000000001fb26000 000000001fb460f0 000000001fb17f18 000000001fb17000 NIP [000000001fb41050] 0x1fb41050 LR [000000001fb4104c] 0x1fb4104c Call Trace: Instruction dump: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX ---[ end trace 3ddec07f638c34a2 ]--- This happens because MSR[RI] is unset when entering RTAS but there is no valid reason to not set it here. RTAS is expected t