netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Yi-Hung Wei <yihung.wei@gmail.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
	Yi-Hung Wei <yihung.wei@gmail.com>,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH net-next 1/2] netfilter: Export nf_ct_destroy_timeout()
Date: Sat, 23 Mar 2019 14:41:50 +0800	[thread overview]
Message-ID: <201903231402.KFLVGATu%lkp@intel.com> (raw)
In-Reply-To: <1553116295-16359-1-git-send-email-yihung.wei@gmail.com>

Hi Yi-Hung,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Yi-Hung-Wei/netfilter-Export-nf_ct_destroy_timeout/20190323-094843
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'


sparse warnings: (new ones prefixed by >>)

   net//netfilter/nf_conntrack_timeout.c:38:62: sparse: incompatible types in comparison expression (different base types)
>> net//netfilter/nf_conntrack_timeout.c:58:23: sparse: incompatible types in comparison expression (different address spaces)

vim +58 net//netfilter/nf_conntrack_timeout.c

    33	
    34	static int untimeout(struct nf_conn *ct, void *timeout)
    35	{
    36		struct nf_conn_timeout *timeout_ext = nf_ct_timeout_find(ct);
    37	
  > 38		if (timeout_ext && (!timeout || timeout_ext->timeout == timeout))
    39			RCU_INIT_POINTER(timeout_ext->timeout, NULL);
    40	
    41		/* We are not intended to delete this conntrack. */
    42		return 0;
    43	}
    44	
    45	void nf_ct_untimeout(struct net *net, struct nf_ct_timeout *timeout)
    46	{
    47		nf_ct_iterate_cleanup_net(net, untimeout, timeout, 0, 0);
    48	}
    49	EXPORT_SYMBOL_GPL(nf_ct_untimeout);
    50	
    51	void nf_ct_destroy_timeout(struct nf_conn *ct)
    52	{
    53	#ifdef CONFIG_NF_CONNTRACK_TIMEOUT
    54		struct nf_conn_timeout *timeout_ext;
    55		typeof(nf_ct_timeout_put_hook) timeout_put;
    56	
    57		rcu_read_lock();
  > 58		timeout_put = rcu_dereference(nf_ct_timeout_put_hook);
    59	
    60		if (timeout_put) {
    61			timeout_ext = nf_ct_timeout_find(ct);
    62			if (timeout_ext) {
    63				timeout_put(timeout_ext->timeout);
    64				RCU_INIT_POINTER(timeout_ext->timeout, NULL);
    65			}
    66		}
    67		rcu_read_unlock();
    68	#endif
    69	}
    70	EXPORT_SYMBOL_GPL(nf_ct_destroy_timeout);
    71	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

      parent reply	other threads:[~2019-03-23  6:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 21:11 [PATCH net-next 1/2] netfilter: Export nf_ct_destroy_timeout() Yi-Hung Wei
2019-03-20 21:11 ` [PATCH net-next 2/2] openvswitch: Add timeout support to ct action Yi-Hung Wei
2019-03-21  4:39   ` Pravin Shelar
2019-03-21 23:05     ` Yi-Hung Wei
2019-03-23  2:49   ` kbuild test robot
2019-03-23  8:35   ` kbuild test robot
2019-03-23  6:41 ` kbuild 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=201903231402.KFLVGATu%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=yihung.wei@gmail.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).