From: Boqun Feng <boqun.feng@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vlastimil Babka <vbabka@suse.cz>,
"Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the slab tree with the rcu tree
Date: Tue, 11 Feb 2025 21:34:23 -0800 [thread overview]
Message-ID: <Z6wy388KxXI2xpfA@Mac.home> (raw)
In-Reply-To: <20250212150941.5e4fa1c9@canb.auug.org.au>
Hi Stephen,
On Wed, Feb 12, 2025 at 03:09:41PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the slab tree got a conflict in:
>
> kernel/rcu/tiny.c
>
> between commits:
>
> 84ae91018af5 ("rcutorture: Include grace-period sequence numbers in failure/close-call")
> 2db7ab8c1086 ("rcutorture: Expand failure/close-call grace-period output")
> 7acc2d90151f ("rcutorture: Make cur_ops->format_gp_seqs take buffer length")
>
> from the rcu tree and commit:
>
> b14ff274e8aa ("slab, rcu: move TINY_RCU variant of kvfree_rcu() to SLAB")
>
> 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.
>
Thanks for reporting this, the below resolution looks good to me, I also
created a branch recording this:
git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git merge/rcu-vs-slab.2025.02.11a
Regards,
Boqun
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc kernel/rcu/tiny.c
> index 8a52aca686a5,7a34a99d4664..000000000000
> --- a/kernel/rcu/tiny.c
> +++ b/kernel/rcu/tiny.c
> @@@ -246,31 -232,6 +232,20 @@@ bool poll_state_synchronize_rcu(unsigne
> }
> EXPORT_SYMBOL_GPL(poll_state_synchronize_rcu);
>
> - #ifdef CONFIG_KASAN_GENERIC
> - void kvfree_call_rcu(struct rcu_head *head, void *ptr)
> - {
> - if (head)
> - kasan_record_aux_stack(ptr);
> -
> - __kvfree_call_rcu(head, ptr);
> - }
> - EXPORT_SYMBOL_GPL(kvfree_call_rcu);
> - #endif
> -
> +#if IS_ENABLED(CONFIG_RCU_TORTURE_TEST)
> +unsigned long long rcutorture_gather_gp_seqs(void)
> +{
> + return READ_ONCE(rcu_ctrlblk.gp_seq) & 0xffffULL;
> +}
> +EXPORT_SYMBOL_GPL(rcutorture_gather_gp_seqs);
> +
> +void rcutorture_format_gp_seqs(unsigned long long seqs, char *cp, size_t len)
> +{
> + snprintf(cp, len, "g%04llx", seqs & 0xffffULL);
> +}
> +EXPORT_SYMBOL_GPL(rcutorture_format_gp_seqs);
> +#endif
> +
> void __init rcu_init(void)
> {
> open_softirq(RCU_SOFTIRQ, rcu_process_callbacks);
next prev parent reply other threads:[~2025-02-12 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 4:09 linux-next: manual merge of the slab tree with the rcu tree Stephen Rothwell
2025-02-12 5:34 ` Boqun Feng [this message]
-- strict thread matches above, loose matches on Subject: below --
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=Z6wy388KxXI2xpfA@Mac.home \
--to=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=urezki@gmail.com \
--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