* re: sfc: process RX event inner checksum flags
@ 2017-02-10 16:14 Colin Ian King
2017-02-10 16:52 ` Edward Cree
0 siblings, 1 reply; 2+ messages in thread
From: Colin Ian King @ 2017-02-10 16:14 UTC (permalink / raw)
To: Solarflare linux maintainers, Edward Cree, netdev
Cc: linux-kernel@vger.kernel.org
Hi there,
not sure if this is a bug, or intentional, but CoverityScan picked up a
mismatch in arguments when calling efx_ef10_handle_rx_event_error() with
commit "sfc: process RX event inner checksum flags" that landed in
linux-next:
CID 1402067 (#1 of 1): Arguments in wrong order
(SWAPPED_ARGUMENTS)swapped_arguments: The positions of arguments in the
call to efx_ef10_handle_rx_event_errors do not match the ordering of the
parameters:
rx_l3_class is passed to rx_encap_hdr
rx_l4_class is passed to rx_l3_class
rx_encap_hdr is passed to rx_l4_class
The function in question has the prototype:
static u16 efx_ef10_handle_rx_event_errors(struct efx_channel *channel,
unsigned int n_packets,
unsigned int rx_encap_hdr,
unsigned int rx_l3_class,
unsigned int rx_l4_class,
const efx_qword_t *event)
...where as it it being called using:
flags |= efx_ef10_handle_rx_event_errors(channel, n_packets,
rx_l3_class, rx_l4_class, rx_encap_hdr, event);
Is this a bug or intentional?
Colin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-02-10 16:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-10 16:14 sfc: process RX event inner checksum flags Colin Ian King
2017-02-10 16:52 ` Edward Cree
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox