From: Pravin Shelar <pravin.ovn@gmail.com>
To: Xidong Wang <wangxidong_97@163.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
ovs dev <dev@openvswitch.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] openvswitch: fix infoleak in conntrack
Date: Tue, 16 Jun 2020 00:17:00 -0700 [thread overview]
Message-ID: <CAOrHB_C2o31V1duzEFYAc4cqejR+P9m=7KuW=6trQa=aM8v7yg@mail.gmail.com> (raw)
In-Reply-To: <1592273581-31338-1-git-send-email-wangxidong_97@163.com>
On Mon, Jun 15, 2020 at 7:13 PM Xidong Wang <wangxidong_97@163.com> wrote:
>
> From: xidongwang <wangxidong_97@163.com>
>
> The stack object “zone_limit” has 3 members. In function
> ovs_ct_limit_get_default_limit(), the member "count" is
> not initialized and sent out via “nla_put_nohdr”.
>
> Signed-off-by: xidongwang <wangxidong_97@163.com>
Looks good.
Acked-by: Pravin B Shelar <pshelar@ovn.org>
next prev parent reply other threads:[~2020-06-16 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 2:13 [PATCH 1/1] openvswitch: fix infoleak in conntrack Xidong Wang
2020-06-16 7:17 ` Pravin Shelar [this message]
2020-06-16 7:44 ` [ovs-dev] " Tonghao Zhang
2020-06-16 8:42 ` Simon Horman
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='CAOrHB_C2o31V1duzEFYAc4cqejR+P9m=7KuW=6trQa=aM8v7yg@mail.gmail.com' \
--to=pravin.ovn@gmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wangxidong_97@163.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;
as well as URLs for NNTP newsgroup(s).