Received-SPF: pass (google.com: domain of linux-kernel+bounces-214083-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Fri, 14 Jun 2024 09:05:23 +1000
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Masami Hiramatsu
 <mhiramat@kernel.org>, Christian Brauner <brauner@kernel.org>, Christian
 =?UTF-8?B?R8O2dHRzY2hl?= <cgzones@googlemail.com>, Linux Kernel Mailing
 List <linux-kernel@vger.kernel.org>, Linux Next Mailing List
 <linux-next@vger.kernel.org>, Michael Ellerman <mpe@ellerman.id.au>, Mark
 Brown <broonie@kernel.org>
Subject: Re: linux-next: manual merge of the ftrace tree with the
 vfs-brauner tree
Message-ID: <20240614090523.246f48e4@canb.auug.org.au>
In-Reply-To: <ZmqaytbJ0r0EXO8d@krava>
References: <20240613114243.2a50059b@canb.auug.org.au>
	<ZmqaytbJ0r0EXO8d@krava>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/pqlA1vpx455Q_K6YVmokT2X";
 protocol="application/pgp-signature"; micalg=pgp-sha256

--Sig_/pqlA1vpx455Q_K6YVmokT2X
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Jiri,

[Cc'd Mark Brown and Michael Ellerman just in case they decide to do
linux-next releases whil I am away.]

On Thu, 13 Jun 2024 09:07:54 +0200 Jiri Olsa <olsajiri@gmail.com> wrote:
>
> On Thu, Jun 13, 2024 at 11:42:43AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >=20
> > Today's linux-next merge of the ftrace tree got conflicts in:
> >=20
> >   arch/x86/entry/syscalls/syscall_64.tbl
> >   include/uapi/asm-generic/unistd.h
> >=20
> > between commit:
> >=20
> >   e6873349f700 ("fs/xattr: add *at family syscalls")
> >=20
> > from the vfs-brauner tree and commit:
> >=20
> >   190fec72df4a ("uprobe: Wire up uretprobe system call")
> >=20
> > from the ftrace tree.
> >=20
> > 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.
> >=20
> > --=20
> > Cheers,
> > Stephen Rothwell
> >=20
> > diff --cc arch/x86/entry/syscalls/syscall_64.tbl
> > index 26af003921d2,6452c2ec469a..000000000000
> > --- a/arch/x86/entry/syscalls/syscall_64.tbl
> > +++ b/arch/x86/entry/syscalls/syscall_64.tbl
> > @@@ -385,10 -384,7 +385,11 @@@
> >   460	common	lsm_set_self_attr	sys_lsm_set_self_attr
> >   461	common	lsm_list_modules	sys_lsm_list_modules
> >   462 	common  mseal			sys_mseal
> >  -463	64	uretprobe		sys_uretprobe
> >  +463	common	setxattrat		sys_setxattrat
> >  +464	common	getxattrat		sys_getxattrat
> >  +465	common	listxattrat		sys_listxattrat
> >  +466	common	removexattrat		sys_removexattrat
> > ++467	64	uretprobe		sys_uretprobe
> >  =20
> >   #
> >   # Due to a historical design error, certain syscalls are numbered dif=
ferently
> > diff --cc include/uapi/asm-generic/unistd.h
> > index 5b8dab0b934e,2378f88d5ad4..000000000000
> > --- a/include/uapi/asm-generic/unistd.h
> > +++ b/include/uapi/asm-generic/unistd.h
> > @@@ -845,17 -845,11 +845,20 @@@ __SYSCALL(__NR_lsm_list_modules, sys_ls
> >   #define __NR_mseal 462
> >   __SYSCALL(__NR_mseal, sys_mseal)
> >  =20
> >  -#define __NR_uretprobe 463
> >  +#define __NR_setxattrat 463
> >  +__SYSCALL(__NR_setxattrat, sys_setxattrat)
> >  +#define __NR_getxattrat 464
> >  +__SYSCALL(__NR_getxattrat, sys_getxattrat)
> >  +#define __NR_listxattrat 465
> >  +__SYSCALL(__NR_listxattrat, sys_listxattrat)
> >  +#define __NR_removexattrat 466
> >  +__SYSCALL(__NR_removexattrat, sys_removexattrat)
> >  +
> > ++#define __NR_uretprobe 467
> > + __SYSCALL(__NR_uretprobe, sys_uretprobe) =20
>=20
> hi,
> we need one more change in tests (below), otherwise lgtm
> I can send formal patch for you if needed, plz let me know
>=20
> thanks,
> jirka
>=20
>=20
> ---
> diff --git a/tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c b/to=
ols/testing/selftests/bpf/prog_tests/uprobe_syscall.c
> index c8517c8f5313..bd8c75b620c2 100644
> --- a/tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c
> +++ b/tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c
> @@ -216,7 +216,7 @@ static void test_uretprobe_regs_change(void)
>  }
> =20
>  #ifndef __NR_uretprobe
> -#define __NR_uretprobe 463
> +#define __NR_uretprobe 467
>  #endif
> =20
>  __naked unsigned long uretprobe_syscall_call_1(void)

Or you could change __NR_uretprobe in the patch set to 467, then this
will become just a conflict and not a renumbering.

--=20
Cheers,
Stephen Rothwell

--Sig_/pqlA1vpx455Q_K6YVmokT2X
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmZrezMACgkQAVBC80lX
0GzrUQgAi6RKxet5+upQje0Zmi+rxYK24YRJoiBJYS4FOhJjmVrfV30PhS4A0iRY
6rJLbmNQDJch+fanjTk9vgBnwWQyF7UM6u0llgJNJG1CIj9B+hzrly8vwlDQVrMb
V9omSFNzdEPuACyBQxesJbT0WSSh7FhADWdgAs0fJbJ4bV+JJrUJjMUUk/gCH9yL
jhT1Edundp6wSc8MMBTDDSh/qEJ7TZ+QaE3qy33hS5xtZ6IbbffTE0jIWmfqXpMM
fy8XmSBqEb7aiODMsOGQQ40bkt445ZD/ov+YkdFmOQ+l17pd4nF8TGgY6homlbzc
02zfq8b8CoN+4Otx2GEyoQwX19fwVw==
=dszQ
-----END PGP SIGNATURE-----

--Sig_/pqlA1vpx455Q_K6YVmokT2X--