netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christian Hopps <chopps@chopps.org>, devel@linux-ipsec.org
Cc: oe-kbuild-all@lists.linux.dev,
	Steffen Klassert <steffen.klassert@secunet.com>,
	netdev@vger.kernel.org, Florian Westphal <fw@strlen.de>,
	Sabrina Dubroca <sd@queasysnail.net>,
	Simon Horman <horms@kernel.org>,
	Antony Antony <antony@phenome.org>,
	Christian Hopps <chopps@chopps.org>
Subject: Re: [PATCH ipsec-next v13 15/15] xfrm: iptfs: add tracepoint functionality
Date: Tue, 5 Nov 2024 23:06:00 +0800	[thread overview]
Message-ID: <202411052231.OM2TTHhn-lkp@intel.com> (raw)
In-Reply-To: <20241105083759.2172771-16-chopps@chopps.org>

Hi Christian,

kernel test robot noticed the following build warnings:

[auto build test WARNING on klassert-ipsec-next/master]
[also build test WARNING on next-20241105]
[cannot apply to klassert-ipsec/master netfilter-nf/main linus/master nf-next/master v6.12-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Christian-Hopps/xfrm-config-add-CONFIG_XFRM_IPTFS/20241105-164740
base:   https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
patch link:    https://lore.kernel.org/r/20241105083759.2172771-16-chopps%40chopps.org
patch subject: [PATCH ipsec-next v13 15/15] xfrm: iptfs: add tracepoint functionality
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20241105/202411052231.OM2TTHhn-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241105/202411052231.OM2TTHhn-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/202411052231.OM2TTHhn-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> net/xfrm/xfrm_iptfs.c:194:12: warning: '__trace_ip_proto_seq' defined but not used [-Wunused-function]
     194 | static u32 __trace_ip_proto_seq(struct iphdr *iph)
         |            ^~~~~~~~~~~~~~~~~~~~
>> net/xfrm/xfrm_iptfs.c:187:12: warning: '__trace_ip_proto' defined but not used [-Wunused-function]
     187 | static u32 __trace_ip_proto(struct iphdr *iph)
         |            ^~~~~~~~~~~~~~~~

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for GET_FREE_REGION
   Depends on [n]: SPARSEMEM [=n]
   Selected by [y]:
   - RESOURCE_KUNIT_TEST [=y] && RUNTIME_TESTING_MENU [=y] && KUNIT [=y]


vim +/__trace_ip_proto_seq +194 net/xfrm/xfrm_iptfs.c

   186	
 > 187	static u32 __trace_ip_proto(struct iphdr *iph)
   188	{
   189		if (iph->version == 4)
   190			return iph->protocol;
   191		return ((struct ipv6hdr *)iph)->nexthdr;
   192	}
   193	
 > 194	static u32 __trace_ip_proto_seq(struct iphdr *iph)
   195	{
   196		void *nexthdr;
   197		u32 protocol = 0;
   198	
   199		if (iph->version == 4) {
   200			nexthdr = (void *)(iph + 1);
   201			protocol = iph->protocol;
   202		} else if (iph->version == 6) {
   203			nexthdr = (void *)(((struct ipv6hdr *)(iph)) + 1);
   204			protocol = ((struct ipv6hdr *)(iph))->nexthdr;
   205		}
   206		switch (protocol) {
   207		case IPPROTO_ICMP:
   208			return ntohs(((struct icmphdr *)nexthdr)->un.echo.sequence);
   209		case IPPROTO_ICMPV6:
   210			return ntohs(((struct icmp6hdr *)nexthdr)->icmp6_sequence);
   211		case IPPROTO_TCP:
   212			return ntohl(((struct tcphdr *)nexthdr)->seq);
   213		case IPPROTO_UDP:
   214			return ntohs(((struct udphdr *)nexthdr)->source);
   215		default:
   216			return 0;
   217		}
   218	}
   219	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2024-11-05 15:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  8:37 [PATCH ipsec-next v13 00/15] Add IP-TFS mode to xfrm Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 01/15] xfrm: config: add CONFIG_XFRM_IPTFS Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 02/15] include: uapi: protocol number and packet structs for AGGFRAG in ESP Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 03/15] xfrm: netlink: add config (netlink) options Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 04/15] xfrm: add mode_cbs module functionality Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 05/15] xfrm: add generic iptfs defines and functionality Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 06/15] xfrm: iptfs: add new iptfs xfrm mode impl Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 07/15] xfrm: iptfs: add user packet (tunnel ingress) handling Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 08/15] xfrm: iptfs: share page fragments of inner packets Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 09/15] xfrm: iptfs: add fragmenting of larger than MTU user packets Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 10/15] xfrm: iptfs: add basic receive packet (tunnel egress) handling Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 11/15] xfrm: iptfs: handle received fragmented inner packets Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 12/15] xfrm: iptfs: add reusing received skb for the tunnel egress packet Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 13/15] xfrm: iptfs: add skb-fragment sharing code Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 14/15] xfrm: iptfs: handle reordering of received packets Christian Hopps
2024-11-05  8:37 ` [PATCH ipsec-next v13 15/15] xfrm: iptfs: add tracepoint functionality Christian Hopps
2024-11-05 15:06   ` kernel test robot [this message]

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=202411052231.OM2TTHhn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=antony@phenome.org \
    --cc=chopps@chopps.org \
    --cc=devel@linux-ipsec.org \
    --cc=fw@strlen.de \
    --cc=horms@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sd@queasysnail.net \
    --cc=steffen.klassert@secunet.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).