netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	NetFilter <netfilter-devel@vger.kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Florian Westphal <fw@strlen.de>
Subject: linux-next: manual merge of the rcu tree with the netfilter-next tree
Date: Fri, 3 Feb 2017 13:08:02 +1100	[thread overview]
Message-ID: <20170203130802.55dbd6e6@canb.auug.org.au> (raw)

Hi all,

Today's linux-next merge of the rcu tree got a conflict in:

  net/netfilter/nf_conntrack_core.c

between commit:

  a9e419dc7be6 ("netfilter: merge ctinfo into nfct pointer storage area")

from the netfilter-next tree and commit:

  55f619e5c322 ("mm: Rename SLAB_DESTROY_BY_RCU to SLAB_TYPESAFE_BY_RCU")

from the rcu tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc net/netfilter/nf_conntrack_core.c
index 071b97fcbefb,13b7e5159660..000000000000
--- a/net/netfilter/nf_conntrack_core.c
+++ b/net/netfilter/nf_conntrack_core.c
@@@ -1876,9 -1862,8 +1876,9 @@@ int nf_conntrack_init_start(void
  	nf_conntrack_max = max_factor * nf_conntrack_htable_size;
  
  	nf_conntrack_cachep = kmem_cache_create("nf_conntrack",
 -						sizeof(struct nf_conn), 0,
 +						sizeof(struct nf_conn),
 +						NFCT_INFOMASK + 1,
- 						SLAB_DESTROY_BY_RCU | SLAB_HWCACHE_ALIGN, NULL);
+ 						SLAB_TYPESAFE_BY_RCU | SLAB_HWCACHE_ALIGN, NULL);
  	if (!nf_conntrack_cachep)
  		goto err_cachep;
  

                 reply	other threads:[~2017-02-03  2:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170203130802.55dbd6e6@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=paulmck@linux.vnet.ibm.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).