From: Jacob Keller <jacob.e.keller@intel.com>
To: netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
Jacob Keller <jacob.e.keller@intel.com>
Subject: [iproute2-next PATCH 1/3] update <linux/devlink.h> UAPI header
Date: Wed, 20 Jul 2022 11:34:47 -0700 [thread overview]
Message-ID: <20220720183449.2070222-2-jacob.e.keller@intel.com> (raw)
In-Reply-To: <20220720183449.2070222-1-jacob.e.keller@intel.com>
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
---
include/uapi/linux/devlink.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/include/uapi/linux/devlink.h b/include/uapi/linux/devlink.h
index da0f1ba8f7a0..90f6cf97d308 100644
--- a/include/uapi/linux/devlink.h
+++ b/include/uapi/linux/devlink.h
@@ -576,6 +576,14 @@ enum devlink_attr {
DEVLINK_ATTR_LINECARD_TYPE, /* string */
DEVLINK_ATTR_LINECARD_SUPPORTED_TYPES, /* nested */
+ /* Before adding this attribute to a command, user space should check
+ * the policy dump and verify the kernel recognizes the attribute.
+ * Otherwise older kernels which do not recognize the attribute may
+ * silently accept the unknown attribute while not actually performing
+ * a dry run.
+ */
+ DEVLINK_ATTR_DRY_RUN, /* flag */
+
/* add new attributes above here, update the policy in devlink.c */
__DEVLINK_ATTR_MAX,
--
2.36.1
next prev parent reply other threads:[~2022-07-20 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 18:34 [iproute2-next PATCH 0/3] devlink: support dry run attribute for flash update Jacob Keller
2022-07-20 18:34 ` Jacob Keller [this message]
2022-07-20 18:34 ` [iproute2-next PATCH 2/3] mnlg: add function to get CTRL_ATTR_MAXATTR value Jacob Keller
2022-07-20 18:34 ` [iproute2-next PATCH 3/3] devlink: add dry run attribute support to devlink flash Jacob Keller
2022-07-21 5:59 ` Jiri Pirko
2022-07-21 18:55 ` Keller, Jacob E
2022-07-21 5:59 ` [iproute2-next PATCH 0/3] devlink: support dry run attribute for flash update 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=20220720183449.2070222-2-jacob.e.keller@intel.com \
--to=jacob.e.keller@intel.com \
--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).