From: Jakub Kicinski <kuba@kernel.org>
To: Hawkins Jiawei <yin31149@gmail.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
syzbot+232ebdbd36706c965ebf@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, 18801353760@163.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: sched: fix memory leak in tcindex_set_parms
Date: Wed, 2 Nov 2022 20:26:04 -0700 [thread overview]
Message-ID: <20221102202604.0d316982@kernel.org> (raw)
In-Reply-To: <20221031060835.11722-1-yin31149@gmail.com>
On Mon, 31 Oct 2022 14:08:35 +0800 Hawkins Jiawei wrote:
> Kernel will uses tcindex_change() to change an existing
s/will//
> traffic-control-indices filter properties. During the
> process of changing, kernel will clears the old
s/will//
> traffic-control-indices filter result, and updates it
> by RCU assigning new traffic-control-indices data.
>
> Yet the problem is that, kernel will clears the old
s/will//
> traffic-control-indices filter result, without destroying
> its tcf_exts structure, which triggers the above
> memory leak.
>
> This patch solves it by using tcf_exts_destroy() to
> destroy the tcf_exts structure in old
> traffic-control-indices filter result.
>
Please provide a Fixes tag to where the problem was introduced
(or the initial git commit).
> Link: https://lore.kernel.org/all/0000000000001de5c505ebc9ec59@google.com/
> Reported-by: syzbot+232ebdbd36706c965ebf@syzkaller.appspotmail.com
> Tested-by: syzbot+232ebdbd36706c965ebf@syzkaller.appspotmail.com
> Signed-off-by: Hawkins Jiawei <yin31149@gmail.com>
> ---
> net/sched/cls_tcindex.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/net/sched/cls_tcindex.c b/net/sched/cls_tcindex.c
> index 1c9eeb98d826..dc872a794337 100644
> --- a/net/sched/cls_tcindex.c
> +++ b/net/sched/cls_tcindex.c
> @@ -338,6 +338,9 @@ tcindex_set_parms(struct net *net, struct tcf_proto *tp, unsigned long base,
> struct tcf_result cr = {};
> int err, balloc = 0;
> struct tcf_exts e;
> +#ifdef CONFIG_NET_CLS_ACT
> + struct tcf_exts old_e = {};
> +#endif
Why all the ifdefs?
> err = tcf_exts_init(&e, net, TCA_TCINDEX_ACT, TCA_TCINDEX_POLICE);
> if (err < 0)
> @@ -479,6 +482,14 @@ tcindex_set_parms(struct net *net, struct tcf_proto *tp, unsigned long base,
> }
>
> if (old_r && old_r != r) {
> +#ifdef CONFIG_NET_CLS_ACT
> + /* r->exts is not copied from old_r->exts, and
> + * the following code will clears the old_r, so
> + * we need to destroy it after updating the tp->root,
> + * to avoid memory leak bug.
> + */
> + old_e = old_r->exts;
> +#endif
Can't you localize all the changes to this if block?
Maybe add a function called tcindex_filter_result_reinit()
which will act more appropriately?
> err = tcindex_filter_result_init(old_r, cp, net);
> if (err < 0) {
> kfree(f);
> @@ -510,6 +521,9 @@ tcindex_set_parms(struct net *net, struct tcf_proto *tp, unsigned long base,
> tcf_exts_destroy(&new_filter_result.exts);
> }
>
> +#ifdef CONFIG_NET_CLS_ACT
> + tcf_exts_destroy(&old_e);
> +#endif
> if (oldp)
> tcf_queue_work(&oldp->rwork, tcindex_partial_destroy_work);
> return 0;
next prev parent reply other threads:[~2022-11-03 3:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 6:08 [PATCH] net: sched: fix memory leak in tcindex_set_parms Hawkins Jiawei
2022-11-03 3:26 ` Jakub Kicinski [this message]
2022-11-03 16:07 ` Hawkins Jiawei
2022-11-04 2:23 ` Jakub Kicinski
2022-11-05 14:11 ` Hawkins Jiawei
2022-11-05 19:50 ` Cong Wang
2022-11-06 14:55 ` Hawkins Jiawei
2022-11-06 17:49 ` Cong Wang
2022-11-07 16:00 ` Hawkins Jiawei
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=20221102202604.0d316982@kernel.org \
--to=kuba@kernel.org \
--cc=18801353760@163.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+232ebdbd36706c965ebf@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yin31149@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox