From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Yan Zhu <zhuyan34@huawei.com>, tangmeng <tangmeng@uniontech.com>
Subject: Re: linux-next: manual merge of the tip tree with the bpf-next, sysctl trees
Date: Tue, 24 May 2022 11:47:56 +1000 [thread overview]
Message-ID: <20220524114756.7cf12f51@canb.auug.org.au> (raw)
In-Reply-To: <20220414112812.652190b5@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Hi all,
On Thu, 14 Apr 2022 11:29:05 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> kernel/sysctl.c
>
> between commit:
>
> 2900005ea287 ("bpf: Move BPF sysctls from kernel/sysctl.c to BPF core")
>
> from the bpf-next, sysctl trees and commit:
>
> efaa0227f6c6 ("timers: Move timer sysctl into the timer code")
>
> from the tip 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 kernel/sysctl.c
> index 47139877f62d,5b7b1a82ae6a..000000000000
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@@ -2227,17 -2288,24 +2227,6 @@@ static struct ctl_table kern_table[] =
> .extra1 = SYSCTL_ZERO,
> .extra2 = SYSCTL_ONE,
> },
> - #if defined(CONFIG_SMP) && defined(CONFIG_NO_HZ_COMMON)
> -#ifdef CONFIG_BPF_SYSCALL
> -- {
> - .procname = "timer_migration",
> - .data = &sysctl_timer_migration,
> - .maxlen = sizeof(unsigned int),
> - .procname = "unprivileged_bpf_disabled",
> - .data = &sysctl_unprivileged_bpf_disabled,
> - .maxlen = sizeof(sysctl_unprivileged_bpf_disabled),
> -- .mode = 0644,
> - .proc_handler = timer_migration_handler,
> - .proc_handler = bpf_unpriv_handler,
> -- .extra1 = SYSCTL_ZERO,
> - .extra2 = SYSCTL_ONE,
> - .extra2 = SYSCTL_TWO,
> - },
> - {
> - .procname = "bpf_stats_enabled",
> - .data = &bpf_stats_enabled_key.key,
> - .maxlen = sizeof(bpf_stats_enabled_key),
> - .mode = 0644,
> - .proc_handler = bpf_stats_handler,
> -- },
> --#endif
> #if defined(CONFIG_TREE_RCU)
> {
> .procname = "panic_on_rcu_stall",
This is now a conflict between the tip tree and the net-next and sysctl trees.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-24 1:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 1:29 linux-next: manual merge of the tip tree with the bpf-next, sysctl trees Stephen Rothwell
2022-05-24 1:47 ` Stephen Rothwell [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=20220524114756.7cf12f51@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tangmeng@uniontech.com \
--cc=tglx@linutronix.de \
--cc=zhuyan34@huawei.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