From: syzbot <syzbot+006987d1be3586e13555@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [arm-msm?] [net?] memory leak in radix_tree_insert
Date: Fri, 08 Dec 2023 22:53:06 -0800 [thread overview]
Message-ID: <0000000000002bb22d060c0e278e@google.com> (raw)
In-Reply-To: <000000000000bfba3a060bf4ffcf@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [arm-msm?] [net?] memory leak in radix_tree_insert
Author: eadavis@qq.com
please test memory leak in radix_tree_insert
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 33cc938e65a9
diff --git a/net/qrtr/af_qrtr.c b/net/qrtr/af_qrtr.c
index 41ece61eb57a..3d06156fe913 100644
--- a/net/qrtr/af_qrtr.c
+++ b/net/qrtr/af_qrtr.c
@@ -275,6 +275,8 @@ static int qrtr_tx_wait(struct qrtr_node *node, int dest_node, int dest_port,
if (flow) {
init_waitqueue_head(&flow->resume_tx);
if (radix_tree_insert(&node->qrtr_tx_flow, key, flow)) {
+ printk("f: %p\n", flow);
+ radix_tree_delete(&node->qrtr_tx_flow, key);
kfree(flow);
flow = NULL;
}
@@ -287,10 +289,14 @@ static int qrtr_tx_wait(struct qrtr_node *node, int dest_node, int dest_port,
return 1;
spin_lock_irq(&flow->resume_tx.lock);
+ printk("to wait, f: %p, pd: %d, ff: %d, ep: %p\n",
+ flow, flow->pending, flow->failed, node->ep);
ret = wait_event_interruptible_locked_irq(flow->resume_tx,
flow->pending < QRTR_TX_FLOW_HIGH ||
flow->tx_failed ||
!node->ep);
+ printk("r: %d, f: %p, pd: %d, ff: %d, ep: %p\n",
+ ret, flow, flow->pending, flow->failed, node->ep);
if (ret < 0) {
confirm_rx = ret;
} else if (!node->ep) {
next prev parent reply other threads:[~2023-12-09 6:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 0:52 [syzbot] [arm-msm?] [net?] memory leak in radix_tree_insert (2) syzbot
2023-12-08 4:13 ` [syzbot] [arm-msm?] [net?] memory leak in radix_tree_insert syzbot
2023-12-08 5:56 ` syzbot
2023-12-08 6:59 ` syzbot
2023-12-08 7:44 ` syzbot
2023-12-08 9:45 ` syzbot
2023-12-09 4:40 ` syzbot
2023-12-09 6:52 ` syzbot
2023-12-09 6:53 ` syzbot [this message]
2023-12-10 1:04 ` syzbot
2023-12-10 3:52 ` syzbot
2023-12-10 4:30 ` syzbot
2023-12-10 5:14 ` syzbot
2023-12-10 6:06 ` syzbot
2023-12-10 6:58 ` syzbot
2023-12-11 4:24 ` syzbot
2023-12-11 5:15 ` syzbot
2023-12-11 9:48 ` [PATCH] radix-tree: fix " Lizhi Xu
2023-12-11 23:16 ` kernel test robot
2023-12-13 3:25 ` Lizhi Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000002bb22d060c0e278e@google.com \
--to=syzbot+006987d1be3586e13555@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.