lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <aNEUdggN8pkt5ylY@finisterre.sirena.org.uk>
Date: Mon, 22 Sep 2025 10:18:46 +0100
From: Mark Brown <broonie@...nel.org>
Cc: Christian Brauner <brauner@...nel.org>,
	Jeremy Linton <jeremy.linton@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Mark Brown <broonie@...nel.org>, Will Deacon <will@...nel.org>
Subject: linux-next: manual merge of the fs-next tree with the arm64 tree

Hi all,

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

  arch/arm64/include/asm/gcs.h

between commits:

  ea920b50ac9ff ("arm64: uaccess: Move existing GCS accessors definitions to gcs.h")
  9cd2a7f1180f9 ("arm64: uaccess: Add additional userspace GCS accessors")

from the arm64 tree and commit:

  053b5d3aac293 ("arm64/gcs: Return a success value from gcs_alloc_thread_stack()")

from the fs-next 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

diff --cc arch/arm64/include/asm/gcs.h
index 8fa0707069e8b,b4bbec9382a19..0000000000000
--- a/arch/arm64/include/asm/gcs.h
+++ b/arch/arm64/include/asm/gcs.h
@@@ -167,12 -91,8 +167,12 @@@ static inline bool task_gcs_el0_enabled
  static inline void gcs_set_el0_mode(struct task_struct *task) { }
  static inline void gcs_free(struct task_struct *task) { }
  static inline void gcs_preserve_current_state(void) { }
 +static inline void put_user_gcs(unsigned long val, unsigned long __user *addr,
 +				int *err) { }
 +static inline void push_user_gcs(unsigned long val, int *err) { }
 +
- static inline unsigned long gcs_alloc_thread_stack(struct task_struct *tsk,
- 						   const struct kernel_clone_args *args)
+ static inline int gcs_alloc_thread_stack(struct task_struct *tsk,
+ 					 const struct kernel_clone_args *args)
  {
  	return -ENOTSUPP;
  }
complex conflicts.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ