Message ID | 20221117012346.22647-3-shangxiaojing@huawei.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp158729wrr; Wed, 16 Nov 2022 17:33:08 -0800 (PST) X-Google-Smtp-Source: AA0mqf4Ai50nZVo3d8eZPXLWhqxDb/E+LCtMRPcFAMbL7iQjPFRCgwn+0KXnAh0SMjLlLkxOaUMk X-Received: by 2002:a17:906:36cb:b0:7ad:c9b4:8faf with SMTP id b11-20020a17090636cb00b007adc9b48fafmr354861ejc.507.1668648788337; Wed, 16 Nov 2022 17:33:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668648788; cv=none; d=google.com; s=arc-20160816; b=1JePIs4r/drsEXVsdlsC3vqR3QEuumHXeOO010nT7L0HFIchedo/UEV6hHcmWn0S/H 5ncmLbqK2ZUcJ8wRhkn2wGma5Yv+NN1gxMfllQiJ0LlKv8lOhoDM874dtHCBmbBdtWor z+C5sFYLyChXn5BlUT8DRkYMcXwQx9lBwMcyCtWmO8grg3WgX4bVUGzHCsgY2vBeixar wr/ewcRx5dwpx5vPr+5FhINzxXzSN3Keq3PCVRH0ZN3k8YFeQ0/wl+w1FA7qHU3R+HVu VoZJeoh6vwiKBbg3Y+noZbYmiHanQyo/pW+oag7E9XUp3Q6kofs6XFxpSV4NMqs9HWiP PeIw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=0JLlm1pWNL1YmFdXkLdwxvlw7jWaF2WtU3iA/rSEwt4=; b=saprrRsCLD4X84ZdVqx/bTtZofG02Yeo3v22QYQA638t+J8Sm4r9GNCHoCg9CY3ucc WbAyHHoQtRJeeo8bLo1H0tpkucmMonsU8owBXzpJ3vAVQNAsfIaroKqyLI9/4D0dvTbY rGFmR+JF6YKA7CR7CEPCYSBL4JSXAKwbQsXEEtgf4iUUJMl5/0jUfqaAUXxUoLJ/yfAJ 9vJVzaDCCDyXbn6tmTQbgKkCe8UxFoLpiFEKcBgYhhp5BBcVtUe/RwsRZduUBHx7bMu2 Vdu0d1Os8+C3c0RdcdsVikxtZgsXiUAXAH0Ah9uvDOUfCYM5PQ0PDOiBgZDDl0ujrzRw TFjA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hc18-20020a170907169200b00782ff2649a7si16355941ejc.346.2022.11.16.17.32.45; Wed, 16 Nov 2022 17:33:08 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234544AbiKQBZd (ORCPT <rfc822;just.gull.subs@gmail.com> + 99 others); Wed, 16 Nov 2022 20:25:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33614 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233772AbiKQBZ0 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 16 Nov 2022 20:25:26 -0500 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 772D73134D for <linux-kernel@vger.kernel.org>; Wed, 16 Nov 2022 17:25:23 -0800 (PST) Received: from kwepemi500016.china.huawei.com (unknown [172.30.72.55]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4NCMfN6GS2zRpNW; Thu, 17 Nov 2022 09:25:00 +0800 (CST) Received: from huawei.com (10.175.100.227) by kwepemi500016.china.huawei.com (7.221.188.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 17 Nov 2022 09:25:20 +0800 From: Shang XiaoJing <shangxiaojing@huawei.com> To: <rostedt@goodmis.org>, <mhiramat@kernel.org>, <zanussi@kernel.org>, <fengguang.wu@intel.com>, <linux-kernel@vger.kernel.org> CC: <shangxiaojing@huawei.com> Subject: [PATCH v3 2/2] tracing: Fix wild-memory-access in register_synth_event() Date: Thu, 17 Nov 2022 09:23:46 +0800 Message-ID: <20221117012346.22647-3-shangxiaojing@huawei.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20221117012346.22647-1-shangxiaojing@huawei.com> References: <20221117012346.22647-1-shangxiaojing@huawei.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.175.100.227] X-ClientProxiedBy: dggems701-chm.china.huawei.com (10.3.19.178) To kwepemi500016.china.huawei.com (7.221.188.220) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1749705071961255840?= X-GMAIL-MSGID: =?utf-8?q?1749705071961255840?= |
Series |
tracing: Fix some bug about synth
|
|
Commit Message
Shang XiaoJing
Nov. 17, 2022, 1:23 a.m. UTC
In register_synth_event(), if set_synth_event_print_fmt() failed, then
both trace_remove_event_call() and unregister_trace_event() will be
called, which means the trace_event_call will call
__unregister_trace_event() twice. As the result, the second unregister
will causes the wild-memory-access.
register_synth_event
set_synth_event_print_fmt failed
trace_remove_event_call
event_remove
if call->event.funcs then
__unregister_trace_event (first call)
unregister_trace_event
__unregister_trace_event (second call)
Fix the bug by avoiding to call the second __unregister_trace_event() by
checking if the first one is called.
general protection fault, probably for non-canonical address
0xfbd59c0000000024: 0000 [#1] SMP KASAN PTI
KASAN: maybe wild-memory-access in range
[0xdead000000000120-0xdead000000000127]
CPU: 0 PID: 3807 Comm: modprobe Not tainted
6.1.0-rc1-00186-g76f33a7eedb4 #299
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
RIP: 0010:unregister_trace_event+0x6e/0x280
Code: 00 fc ff df 4c 89 ea 48 c1 ea 03 80 3c 02 00 0f 85 0e 02 00 00 48
b8 00 00 00 00 00 fc ff df 4c 8b 63 08 4c 89 e2 48 c1 ea 03 <80> 3c 02
00 0f 85 e2 01 00 00 49 89 2c 24 48 85 ed 74 28 e8 7a 9b
RSP: 0018:ffff88810413f370 EFLAGS: 00010a06
RAX: dffffc0000000000 RBX: ffff888105d050b0 RCX: 0000000000000000
RDX: 1bd5a00000000024 RSI: ffff888119e276e0 RDI: ffffffff835a8b20
RBP: dead000000000100 R08: 0000000000000000 R09: fffffbfff0913481
R10: ffffffff8489a407 R11: fffffbfff0913480 R12: dead000000000122
R13: ffff888105d050b8 R14: 0000000000000000 R15: ffff888105d05028
FS: 00007f7823e8d540(0000) GS:ffff888119e00000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7823e7ebec CR3: 000000010a058002 CR4: 0000000000330ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__create_synth_event+0x1e37/0x1eb0
create_or_delete_synth_event+0x110/0x250
synth_event_run_command+0x2f/0x110
test_gen_synth_cmd+0x170/0x2eb [synth_event_gen_test]
synth_event_gen_test_init+0x76/0x9bc [synth_event_gen_test]
do_one_initcall+0xdb/0x480
do_init_module+0x1cf/0x680
load_module+0x6a50/0x70a0
__do_sys_finit_module+0x12f/0x1c0
do_syscall_64+0x3f/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Fixes: 4b147936fa50 ("tracing: Add support for 'synthetic' events")
Signed-off-by: Shang XiaoJing <shangxiaojing@huawei.com>
Cc: stable@vger.kernel.org
---
changes in v2:
- remove the redundant if statement.
changes in v3:
- remove the redundant return statment.
---
kernel/trace/trace_events_synth.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/trace/trace_events_synth.c b/kernel/trace/trace_events_synth.c index e310052dc83c..29fbfb27c2b2 100644 --- a/kernel/trace/trace_events_synth.c +++ b/kernel/trace/trace_events_synth.c @@ -828,10 +828,9 @@ static int register_synth_event(struct synth_event *event) } ret = set_synth_event_print_fmt(call); - if (ret < 0) { + /* unregister_trace_event() will be called inside */ + if (ret < 0) trace_remove_event_call(call); - goto err; - } out: return ret; err: