Unverified Commit 18e32b66 authored by openeuler-ci-bot's avatar openeuler-ci-bot Committed by Gitee
Browse files

!415 mainline bugfix backport

Merge Pull Request from: @LiuYongQiang0816 
 
|标题| 分析结果|
|--------| ------|
|crypto: rsa-pkcs1pad - fix buffer overread in pkcs1pad_verify_complete() |	在进行读取之前需要检查digest_info大小是否足够 |
|crypto: algif_skcipher - EBUSY on aio should be an error				 |	正确返回错误 |
|crypto: algif_skcipher - Use chunksize instead of blocksize				 |	修复CTR场景下参数错误的问题 |
|ipmi: use %*ph to print small buffer									 |	修复可能buffer溢出的问题 |
|component: do not dereference opaque pointer in debugfs					 |	match->compare[i].data不一定是struct device* 指针类型,这里使用dev_name(data)打印设备名,有可能造成空指针访问。改使用dev_name(component->dev)来打印设备名称|
|drivers/iommu: Export core IOMMU API symbols to permit modular drivers	 |	导出构建IOMMU驱动时所需要的iommu core api。此补丁能够解决iommu driver编译为模块时符号缺失的问题 |
|drivers/iommu: Allow IOMMU bus ops to be unregistered					 |	在iommu类KO卸载的情况下,ops指针非法,有可能触发访问非法地址。修复方式:让bus_set_iommu()接受一个NULL值ops参数来让给定bus类型ops重置 |
|of: unittest: Add of_node_put() before return							 |	修复driver/of/unittest.c中异常返回路径上的内存泄漏问题 |
|of: resolver: Add of_node_put() before return and break					 |	修复从for_each_child_of_node循环中break/return时没有put node而导致内存泄漏的问题 |
|iommu: Properly export iommu_group_get_for_dev()						 |	修复一个iommu core api未使用EXPORT_SYMBOL_GPL导出的问题。是drivers/iommu: Export core IOMMU API symbols to permit modular drivers的后置补丁|
|evm: Check also if *tfm is an error pointer in init_desc()				 |	修补一种在多线程场景下可能的竞争状态|
|evm: Fix a small race in init_desc()									 |	在极端条件下,即便使用了 IS_ERR_OR_NULL() 也会出现竞争状态:其内部会针对 error pointer 和 NULL 做两次判断,而竞争状态可能出现在两次判断之间|
|selinux: reorder hooks to make runtime disable less broken				 |	由于该补丁(v5.6)于 LSM Blob 机制(v5.1)之后合入,一些 hooks 在 4.19 上的实现逻辑与该补丁合入时的有变化,因此它们的位置需要进一步调整|				
 
 
Link:https://gitee.com/openeuler/kernel/pulls/415

 

Reviewed-by: default avatarZheng Zengkai <zhengzengkai@huawei.com>
Signed-off-by: default avatarZheng Zengkai <zhengzengkai@huawei.com>
parents d755712e 87d41806
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please to comment