Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Harry Yoo <harry@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Puranjay Mohan <puranjay@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>
Subject: linux-next: manual merge of the slab tree with the rcu tree
Date: Thu, 30 Jul 2026 15:38:48 +0100	[thread overview]
Message-ID: <amth-CMf3Xz5hR32@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

Hi all,

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

  mm/slab_common.c

between commit:

  736084507faa3 ("rcu: Rename struct rcu_gp_oldstate to rcu_gp_seq")

from the rcu tree and commit:

  bdd0cc9f0ffc3 ("mm/slab: introduce struct kvfree_rcu_head for kvfree_rcu batching")

from the slab 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.

diff --cc mm/slab_common.c
index 657fd75776ea7,b8f21eabcccc2..0000000000000
--- a/mm/slab_common.c
+++ b/mm/slab_common.c
@@@ -1363,8 -1420,8 +1420,8 @@@ struct kvfree_rcu_bulk_data 
  
  struct kfree_rcu_cpu_work {
  	struct rcu_work rcu_work;
- 	struct rcu_head *head_free;
+ 	struct kvfree_rcu_head *head_free;
 -	struct rcu_gp_oldstate head_free_gp_snap;
 +	struct rcu_gp_seq head_free_gp_snap;
  	struct list_head bulk_head_free[FREE_N_CHANNELS];
  	struct kfree_rcu_cpu *krcp;
  };
@@@ -1569,10 -1626,10 +1626,10 @@@ static void kfree_rcu_work(struct work_
  	unsigned long flags;
  	struct kvfree_rcu_bulk_data *bnode, *n;
  	struct list_head bulk_head[FREE_N_CHANNELS];
- 	struct rcu_head *head;
+ 	struct kvfree_rcu_head *head;
  	struct kfree_rcu_cpu *krcp;
  	struct kfree_rcu_cpu_work *krwp;
 -	struct rcu_gp_oldstate head_gp_snap;
 +	struct rcu_gp_seq head_gp_snap;
  	int i;
  
  	krwp = container_of(to_rcu_work(work),

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-07-30 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 14:38 Mark Brown [this message]
2026-07-30 17:31 ` linux-next: manual merge of the slab tree with the rcu tree Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2025-02-12  4:09 Stephen Rothwell
2025-02-12  5:34 ` Boqun Feng
2024-08-12  2:47 Stephen Rothwell

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=amth-CMf3Xz5hR32@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=harry@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=puranjay@kernel.org \
    --cc=vbabka@kernel.org \
    --cc=vbabka@suse.cz \
    /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