From: kernel test robot <lkp@intel.com>
To: Ziwei Xiao <ziweixiao@google.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, jeroendb@google.com,
pkaligineedi@google.com, shailend@google.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, willemb@google.com, hramamurthy@google.com,
rushilg@google.com, ziweixiao@google.com, jfraker@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 4/5] gve: Add flow steering adminq commands
Date: Wed, 8 May 2024 22:24:30 +0800 [thread overview]
Message-ID: <202405082251.rL1Lk120-lkp@intel.com> (raw)
In-Reply-To: <20240507225945.1408516-5-ziweixiao@google.com>
Hi Ziwei,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Ziwei-Xiao/gve-Add-adminq-mutex-lock/20240508-071419
base: net-next/main
patch link: https://lore.kernel.org/r/20240507225945.1408516-5-ziweixiao%40google.com
patch subject: [PATCH net-next 4/5] gve: Add flow steering adminq commands
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20240508/202405082251.rL1Lk120-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240508/202405082251.rL1Lk120-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405082251.rL1Lk120-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/ethernet/google/gve/gve_adminq.c: In function 'gve_adminq_process_flow_rules_query':
>> drivers/net/ethernet/google/gve/gve_adminq.c:1259:15: warning: variable 'descriptor_end' set but not used [-Wunused-but-set-variable]
1259 | void *descriptor_end, *rule_info;
| ^~~~~~~~~~~~~~
vim +/descriptor_end +1259 drivers/net/ethernet/google/gve/gve_adminq.c
1248
1249 /* In the dma memory that the driver allocated for the device to query the flow rules, the device
1250 * will first write it with a struct of gve_query_flow_rules_descriptor. Next to it, the device
1251 * will write an array of rules or rule ids with the count that specified in the descriptor.
1252 * For GVE_FLOW_RULE_QUERY_STATS, the device will only write the descriptor.
1253 */
1254 static int gve_adminq_process_flow_rules_query(struct gve_priv *priv, u16 query_opcode,
1255 struct gve_query_flow_rules_descriptor *descriptor)
1256 {
1257 struct gve_flow_rules_cache *flow_rules_cache = &priv->flow_rules_cache;
1258 u32 num_queried_rules, total_memory_len, rule_info_len;
> 1259 void *descriptor_end, *rule_info;
1260
1261 total_memory_len = be32_to_cpu(descriptor->total_length);
1262 if (total_memory_len > GVE_ADMINQ_BUFFER_SIZE) {
1263 dev_err(&priv->dev->dev, "flow rules query is out of memory.\n");
1264 return -ENOMEM;
1265 }
1266
1267 num_queried_rules = be32_to_cpu(descriptor->num_queried_rules);
1268 descriptor_end = (void *)descriptor + total_memory_len;
1269 rule_info = (void *)(descriptor + 1);
1270
1271 switch (query_opcode) {
1272 case GVE_FLOW_RULE_QUERY_RULES:
1273 rule_info_len = num_queried_rules * sizeof(*flow_rules_cache->rules_cache);
1274
1275 memcpy(flow_rules_cache->rules_cache, rule_info, rule_info_len);
1276 flow_rules_cache->rules_cache_num = num_queried_rules;
1277 break;
1278 case GVE_FLOW_RULE_QUERY_IDS:
1279 rule_info_len = num_queried_rules * sizeof(*flow_rules_cache->rule_ids_cache);
1280
1281 memcpy(flow_rules_cache->rule_ids_cache, rule_info, rule_info_len);
1282 flow_rules_cache->rule_ids_cache_num = num_queried_rules;
1283 break;
1284 case GVE_FLOW_RULE_QUERY_STATS:
1285 priv->num_flow_rules = be32_to_cpu(descriptor->num_flow_rules);
1286 priv->max_flow_rules = be32_to_cpu(descriptor->max_flow_rules);
1287 return 0;
1288 default:
1289 return -EINVAL;
1290 }
1291
1292 return 0;
1293 }
1294
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-08 14:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 22:59 [PATCH net-next 0/5] gve: Add flow steering support Ziwei Xiao
2024-05-07 22:59 ` [PATCH net-next 1/5] gve: Add adminq mutex lock Ziwei Xiao
2024-05-08 12:07 ` Markus Elfring
2024-05-07 22:59 ` [PATCH net-next 2/5] gve: Add adminq extended command Ziwei Xiao
2024-05-08 12:17 ` Markus Elfring
2024-05-11 14:32 ` Simon Horman
2024-05-07 22:59 ` [PATCH net-next 3/5] gve: Add flow steering device option Ziwei Xiao
2024-05-08 5:32 ` David Wei
2024-05-10 0:18 ` Ziwei Xiao
2024-05-08 5:34 ` [PATCH net-next 2/5] gve: Add adminq extended command David Wei
2024-05-10 0:17 ` Ziwei Xiao
2024-05-07 22:59 ` [PATCH net-next 4/5] gve: Add flow steering adminq commands Ziwei Xiao
2024-05-08 6:24 ` David Wei
2024-05-10 0:18 ` Ziwei Xiao
2024-05-20 17:27 ` David Wei
2024-05-08 13:23 ` Markus Elfring
2024-05-08 14:24 ` kernel test robot [this message]
2024-05-07 22:59 ` [PATCH net-next 5/5] gve: Add flow steering ethtool support Ziwei Xiao
2024-05-08 14:09 ` Markus Elfring
2024-05-10 0:19 ` Ziwei Xiao
2024-05-10 3:16 ` Jakub Kicinski
2024-05-10 6:45 ` Markus Elfring
2024-05-11 14:45 ` 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=202405082251.rL1Lk120-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=jfraker@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@google.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