From: Parav Pandit <parav@nvidia.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <netdev@vger.kernel.org>
Cc: Parav Pandit <parav@nvidia.com>
Subject: [PATCH net-next 0/2] devlink: Use nla_policy to validate range
Date: Mon, 21 Sep 2020 19:41:28 +0300 [thread overview]
Message-ID: <20200921164130.83720-1-parav@nvidia.com> (raw)
This two small patches uses nla_policy to validate user specified
fields are in valid range or not.
Patch summary:
Patch-1 checks the range of eswitch mode field
Patch-2 checks for the port type field. It eliminates a check in
code by using nla policy infrastructure.
Parav Pandit (2):
devlink: Enhance policy to validate eswitch mode value
devlink: Enhance policy to validate port type input value
net/core/devlink.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-21 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 16:41 Parav Pandit [this message]
2020-09-21 16:41 ` [PATCH net-next 1/2] devlink: Enhance policy to validate eswitch mode value Parav Pandit
2020-09-21 16:41 ` [PATCH net-next 2/2] devlink: Enhance policy to validate port type input value Parav Pandit
2020-09-21 22:47 ` [PATCH net-next 0/2] devlink: Use nla_policy to validate range Jakub Kicinski
2020-09-23 0:39 ` David Miller
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=20200921164130.83720-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@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 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).