From: Hangyu Hua <hbh25y@gmail.com>
To: Simon Horman <simon.horman@corigine.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: sched: fix possible refcount leak in tc_chain_tmplt_add()
Date: Tue, 6 Jun 2023 10:13:44 +0800 [thread overview]
Message-ID: <1626a8b8-ae7a-a110-44a1-24c8f600822a@gmail.com> (raw)
In-Reply-To: <ZH3Vju3D3KCKAkCO@corigine.com>
On 5/6/2023 20:31, Simon Horman wrote:
> On Mon, Jun 05, 2023 at 03:01:58PM +0800, Hangyu Hua wrote:
>> try_module_get can be called in tcf_proto_lookup_ops. So if ops don't
>> implement the corresponding function we should call module_put to drop
>> the refcount.
>
> Hi Hangyu Hua,
>
> Is this correct even if try_module_get() is
> not called via tcf_proto_lookup_ops() ?
>
tcf_proto_lookup_ops will return error if try_module_get() is not called
in tcf_proto_lookup_ops(). I am not sure what you mean?
Thanks,
Hangyu
>> Fixes: 9f407f1768d3 ("net: sched: introduce chain templates")
>> Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
>> ---
>> net/sched/cls_api.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
>> index 2621550bfddc..92bfb892e638 100644
>> --- a/net/sched/cls_api.c
>> +++ b/net/sched/cls_api.c
>> @@ -2952,6 +2952,7 @@ static int tc_chain_tmplt_add(struct tcf_chain *chain, struct net *net,
>> return PTR_ERR(ops);
>> if (!ops->tmplt_create || !ops->tmplt_destroy || !ops->tmplt_dump) {
>> NL_SET_ERR_MSG(extack, "Chain templates are not supported with specified classifier");
>> + module_put(ops->owner);
>> return -EOPNOTSUPP;
>> }
>>
>> --
>> 2.34.1
>>
>>
next prev parent reply other threads:[~2023-06-06 2:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 7:01 Hangyu Hua
2023-06-05 12:31 ` Simon Horman
2023-06-06 2:13 ` Hangyu Hua [this message]
2023-06-06 9:33 ` Simon Horman
2023-06-06 8:53 ` Larysa Zaremba
2023-06-07 2:20 ` Hangyu Hua
2023-06-06 11:21 ` Jiri Pirko
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=1626a8b8-ae7a-a110-44a1-24c8f600822a@gmail.com \
--to=hbh25y@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=xiyou.wangcong@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
all inboxes | Powered by JetHome®