From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: mst@redhat.com, roopa@cumulusnetworks.com, davem@davemloft.net,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Subject: [PATCH net-next 0/2] virtio_net: better ethtool setting validation
Date: Sun, 7 Feb 2016 21:52:22 +0100 [thread overview]
Message-ID: <1454878344-21730-1-git-send-email-razor@blackwall.org> (raw)
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Hi,
This small set is a follow-up for the recent patches that added ethtool
get/set settings. Patch 1 changes the speed validation routine to check
if the speed is between 0 and INT_MAX (or SPEED_UNKNOWN) and patch 2 adds
port validation to virtio_net and better validation comment.
This set is on top of Michael's patch which explains that speeds from 0
to INT_MAX are valid:
http://patchwork.ozlabs.org/patch/578911/
Cheers,
Nik
Nikolay Aleksandrov (2):
ethtool: make validate_speed accept all speeds between 0 and INT_MAX
virtio_net: validate ethtool port setting and explain the user
validation
drivers/net/virtio_net.c | 6 ++++--
include/uapi/linux/ethtool.h | 19 +------------------
2 files changed, 5 insertions(+), 20 deletions(-)
--
2.4.3
next reply other threads:[~2016-02-07 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 20:52 Nikolay Aleksandrov [this message]
2016-02-07 20:52 ` [PATCH net-next 1/2] ethtool: make validate_speed accept all speeds between 0 and INT_MAX Nikolay Aleksandrov
2016-02-07 21:26 ` Michael S. Tsirkin
2016-02-07 20:52 ` [PATCH net-next 2/2] virtio_net: validate ethtool port setting and explain the user validation Nikolay Aleksandrov
2016-02-07 21:26 ` Michael S. Tsirkin
2016-02-11 16:56 ` [PATCH net-next 0/2] virtio_net: better ethtool setting validation 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=1454878344-21730-1-git-send-email-razor@blackwall.org \
--to=razor@blackwall.org \
--cc=davem@davemloft.net \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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).