From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [RFC net-next] net/flow_offload: allow user to offload tc action to net device
Date: Thu, 29 Apr 2021 22:42:44 +0800 [thread overview]
Message-ID: <202104292231.T8MBtTk3-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3372 bytes --]
CC: kbuild-all(a)lists.01.org
In-Reply-To: <20210429081014.28498-1-simon.horman@netronome.com>
References: <20210429081014.28498-1-simon.horman@netronome.com>
TO: Simon Horman <simon.horman@netronome.com>
Hi Simon,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Simon-Horman/net-flow_offload-allow-user-to-offload-tc-action-to-net-device/20210429-161217
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 4a52dd8fefb45626dace70a63c0738dbd83b7edb
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
config: arm64-randconfig-c004-20210429 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
cocci warnings: (new ones prefixed by >>)
>> net/sched/act_api.c:1075:29-71: WARNING avoid newline at end of message in NL_SET_ERR_MSG_MOD
vim +1075 net/sched/act_api.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 1061
d691d7b74a9b53 Baowen Zheng 2021-04-29 1062 /* offload the tc command after inserted */
d691d7b74a9b53 Baowen Zheng 2021-04-29 1063 int tcf_action_offload_cmd(struct tc_action *actions[], bool add, struct netlink_ext_ack *extack)
d691d7b74a9b53 Baowen Zheng 2021-04-29 1064 {
d691d7b74a9b53 Baowen Zheng 2021-04-29 1065 int err = 0;
d691d7b74a9b53 Baowen Zheng 2021-04-29 1066 struct flow_offload_action *fl_act;
d691d7b74a9b53 Baowen Zheng 2021-04-29 1067
d691d7b74a9b53 Baowen Zheng 2021-04-29 1068 fl_act = flow_action_alloc(tcf_act_num_actions(actions));
d691d7b74a9b53 Baowen Zheng 2021-04-29 1069 if (!fl_act)
d691d7b74a9b53 Baowen Zheng 2021-04-29 1070 return -ENOMEM;
d691d7b74a9b53 Baowen Zheng 2021-04-29 1071
d691d7b74a9b53 Baowen Zheng 2021-04-29 1072 fl_act->extack = extack;
d691d7b74a9b53 Baowen Zheng 2021-04-29 1073 err = tc_setup_action(&fl_act->action, actions);
d691d7b74a9b53 Baowen Zheng 2021-04-29 1074 if (err) {
d691d7b74a9b53 Baowen Zheng 2021-04-29 @1075 NL_SET_ERR_MSG_MOD(extack, "Failed to setup tc actions for offload\n");
d691d7b74a9b53 Baowen Zheng 2021-04-29 1076 goto err_out;
d691d7b74a9b53 Baowen Zheng 2021-04-29 1077 }
d691d7b74a9b53 Baowen Zheng 2021-04-29 1078 fl_act->command = add ? FLOW_ACT_REPLACE : FLOW_ACT_DESTROY;
d691d7b74a9b53 Baowen Zheng 2021-04-29 1079
d691d7b74a9b53 Baowen Zheng 2021-04-29 1080 flow_indr_dev_setup_offload(NULL, NULL, TC_SETUP_ACT, fl_act, NULL, NULL);
d691d7b74a9b53 Baowen Zheng 2021-04-29 1081
d691d7b74a9b53 Baowen Zheng 2021-04-29 1082 tc_cleanup_flow_action(&fl_act->action);
d691d7b74a9b53 Baowen Zheng 2021-04-29 1083
d691d7b74a9b53 Baowen Zheng 2021-04-29 1084 err_out:
d691d7b74a9b53 Baowen Zheng 2021-04-29 1085 kfree(fl_act);
d691d7b74a9b53 Baowen Zheng 2021-04-29 1086 return err;
d691d7b74a9b53 Baowen Zheng 2021-04-29 1087 }
d691d7b74a9b53 Baowen Zheng 2021-04-29 1088 EXPORT_SYMBOL(tcf_action_offload_cmd);
d691d7b74a9b53 Baowen Zheng 2021-04-29 1089
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31687 bytes --]
next reply other threads:[~2021-04-29 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 14:42 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-29 8:10 [RFC net-next] net/flow_offload: allow user to offload tc action to net device Simon Horman
2021-04-29 16:49 ` Ido Schimmel
2021-04-29 18:20 ` kernel test robot
2021-04-30 2:47 ` Marcelo Ricardo Leitner
2021-04-30 11:11 ` Vlad Buslov
2021-05-10 22:37 ` Jamal Hadi Salim
2021-05-10 22:47 ` Jamal Hadi Salim
2021-05-21 7:33 ` Jianbo Liu
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=202104292231.T8MBtTk3-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.