From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Christian Brauner <brauner@kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Cc: "Christian Göttsche" <cgzones@googlemail.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the ftrace tree with the vfs-brauner tree
Date: Wed, 17 Jul 2024 13:21:55 +1000 [thread overview]
Message-ID: <20240717132155.6ca2ce47@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]
Hi all,
Today's linux-next merge of the ftrace tree got a conflict in:
arch/x86/entry/syscalls/syscall_64.tbl
between commit:
e6873349f700 ("fs/xattr: add *at family syscalls")
from the vfs-brauner tree and commits:
190fec72df4a ("uprobe: Wire up uretprobe system call")
63ded110979b ("uprobe: Change uretprobe syscall scope and number")
from the ftrace 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.
I also added this patch due to commit (no in Linus' tree)
4fe53bf2ba0a ("syscalls: add generic scripts/syscall.tbl")
rom: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 17 Jul 2024 13:15:32 +1000
Subject: [PATCH] fixup for "uprobe: Wire up uretprobe system call"
and "uprobe: Change uretprobe syscall scope and number"
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
scripts/syscall.tbl | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/syscall.tbl b/scripts/syscall.tbl
index 86b53c7a815b..c792b08e594d 100644
--- a/scripts/syscall.tbl
+++ b/scripts/syscall.tbl
@@ -406,3 +406,4 @@
464 common getxattrat sys_getxattrat
465 common listxattrat sys_listxattrat
466 common removexattrat sys_removexattrat
+467 common uretprobe sys_uretprobe
--
2.43.0
--
Cheers,
Stephen Rothwell
diff --cc arch/x86/entry/syscalls/syscall_64.tbl
index 623d954f3afb,dabf1982de6d..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 common setxattrat sys_setxattrat
+464 common getxattrat sys_getxattrat
+465 common listxattrat sys_listxattrat
+466 common removexattrat sys_removexattrat
+ 467 common uretprobe sys_uretprobe
#
# Due to a historical design error, certain syscalls are numbered differently
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next reply other threads:[~2024-07-17 3:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 3:21 Stephen Rothwell [this message]
2024-07-19 0:34 ` linux-next: manual merge of the ftrace tree with the vfs-brauner tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 2:55 Stephen Rothwell
2024-06-13 1:42 Stephen Rothwell
2024-06-13 7:07 ` Jiri Olsa
2024-06-13 23:05 ` Stephen Rothwell
2024-06-14 1:07 ` Masami Hiramatsu
2024-07-02 17:06 ` 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=20240717132155.6ca2ce47@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=cgzones@googlemail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/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