- Test - mailweb.openeuler.org

openEuler-20.03 LTS版本syzkaller发现问题，请分析
by zhouang 12 May '20

12 May '20

1 0

(no subject)
by zhouang 12 May '20

12 May '20

Test

1 0

openEuler-20.03 LTS版本syzkaller发现问题，请分析
by Limiaohua (ICSL) 12 May '20

12 May '20

Openeuler：附件为openEuler-20.03 LTS内核源码采用syzkaller官方配置方法在x86-64环境跑出来的问题。 [cid:image001.png@01D6287E.53276790] Crashstat.txt是问题简要描述和ID，根据ID到相关的文件夹中可以找到详细信息。 “no output from test machine”这种无可分析信息的问题可略过。 [cid:image002.png@01D6287E.53276790] crashes20200511114318.zip(73.95M) <https://onebox.huawei.com/hwshare/5a0c0075160c7f264b90780fd81967e4?fileId=1…> ・转发、回复给外部收件人无效

1 0

openEuler-20.03 LTS版本syzkaller发现问题，请分析
by zhouang 12 May '20

12 May '20

发件人: Limiaohua (ICSL) 发送时间: 12 May 2020 16:50 收件人: zhouang <zhouang1(a)huawei.com>; Husheng (TommyLike) <hu.husheng(a)huawei.com> 主题: 转发: openEuler-20.03 LTS版本syzkaller发现问题，请分析发件人: Limiaohua (ICSL) 发送时间: 2020年5月11日 14:32 收件人: 'securities(a)openeuler.org' <securities(a)openeuler.org<mailto:securities@openeuler.org>> 抄送: 'zhujianwei7(a)huawei.com' <zhujianwei7(a)huawei.com<mailto:zhujianwei7@huawei.com>>; Luoxiaoxing (Sam, ICSL) <luoxiaoxing(a)huawei.com<mailto:luoxiaoxing@huawei.com>> 主题: openEuler-20.03 LTS版本syzkaller发现问题，请分析 Openeuler：附件为openEuler-20.03 LTS内核源码采用syzkaller官方配置方法在x86-64环境跑出来的问题。 [cid:image002.png@01D627A0.F9DE89D0] Crashstat.txt是问题简要描述和ID，根据ID到相关的文件夹中可以找到详细信息。 “no output from test machine”这种无可分析信息的问题可略过。 [cid:image001.png@01D627A0.6D5CD7A0] crashes20200511114318.zip(73.95M) <https://onebox.huawei.com/hwshare/5a0c0075160c7f264b90780fd81967e4?fileId=1…> ・转发、回复给外部收件人无效

1 0

(no subject)
by zhouang 12 May '20

12 May '20

test

1 0

openEuler-20.03 LTS版本syzkaller发现问题，请分析
by zhouang 12 May '20

12 May '20

Openeuler：附件为openEuler-20.03 LTS内核源码采用syzkaller官方配置方法在x86-64环境跑出来的问题。 [cid:image002.png@01D627A0.F9DE89D0] Crashstat.txt是问题简要描述和ID，根据ID到相关的文件夹中可以找到详细信息。 “no output from test machine”这种无可分析信息的问题可略过。 [cid:image001.png@01D627A0.6D5CD7A0] crashes20200511114318.zip(73.95M) <https://onebox.huawei.com/hwshare/5a0c0075160c7f264b90780fd81967e4?fileId...<https://onebox.huawei.com/hwshare/5a0c0075160c7f264b90780fd81967e4?fileId=1…> ・转发、回复给外部收件人无效

1 0

(no subject)
by zhouang 11 May '20

11 May '20

TEST, Hi YYL

1 0

转发: [PATCH 42/62] drm/amdkfd: kfree the wrong pointer
by zhouang 11 May '20

11 May '20

From: Jack Zhang <Jack.Zhang1(a)amd.com> [ Upstream commit 3148a6a0ef3cf93570f30a477292768f7eb5d3c3 ] Originally, it kfrees the wrong pointer for mem_obj. It would cause memory leak under stress test. Signed-off-by: Jack Zhang <Jack.Zhang1(a)amd.com> Acked-by: Nirmoy Das <nirmoy.das(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Signed-off-by: Sasha Levin <sashal(a)kernel.org> --- drivers/gpu/drm/amd/amdkfd/kfd_device.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_device.c b/drivers/gpu/drm/amd/amdkfd/kfd_device.c index 938d005..28022d1 100644 --- a/drivers/gpu/drm/amd/amdkfd/kfd_device.c +++ b/drivers/gpu/drm/amd/amdkfd/kfd_device.c @@ -921,9 +921,9 @@ int kfd_gtt_sa_allocate(struct kfd_dev *kfd, unsigned int size, return 0; kfd_gtt_no_free_chunk: - pr_debug("Allocation failed with mem_obj = %p\n", mem_obj); + pr_debug("Allocation failed with mem_obj = %p\n", *mem_obj); mutex_unlock(&kfd->gtt_sa_lock); - kfree(mem_obj); + kfree(*mem_obj); return -ENOMEM; } -- 1.8.3 _______________________________________________ Kernel mailing list -- kernel(a)openeuler.org To unsubscribe send an email to kernel-leave(a)openeuler.org

1 0

Hello Arm
by zhouang 30 Apr '20

30 Apr '20

Can you hear me? Please response. Cheers! Ang Zhou

1 0

(无主题)
by 周昂 29 Apr '20

29 Apr '20

hello arm

1 0

2024

2023

2022

2021

2020

Test