On Tue, Jun 11, 2024 at 01:26:50PM +0530, Dev Jain wrote:
> + * A signal is said to be delivered, when the program takes action on the
> + * signal: such action may involve termination of the process, ignoring the
> + * signal, terminating with core dump, stopping the process, or continuing
> the
On Tue, Jun 11, 2024 at 03:23:17PM -0700, Andrew Morton wrote:
> On Wed, 05 Jun 2024 23:36:12 +0100 Mark Brown wrote:
> > KTAP parsers interpret the output of ksft_test_result_*() as being the
> > name of the test. The map_fixed_noreplace test uses a dynamically
> > alloc
On Wed, Jun 12, 2024 at 10:14:01AM +0530, Dev Jain wrote:
> On 6/11/24 16:55, Mark Brown wrote:
> > On Tue, Jun 11, 2024 at 01:26:50PM +0530, Dev Jain wrote:
> > > + * A signal is said to be delivered, when the program takes action on the
> > > + * signal: such action
On Thu, Jun 13, 2024 at 08:34:29AM +0100, Colin Ian King wrote:
> There are two spelling mistakes in some error messages. Fix them.
Reviewed-by: Mark Brown
signature.asc
Description: PGP signature
On Thu, Jun 13, 2024 at 10:21:39AM +0530, Dev Jain wrote:
> I guess we agree on the same thing; so, how about I rephrase the delivery
> and blocking code comments this way:
> "A process can request blocking of a signal by masking it into its set of
> blocked signals; such a signal, when sent to th
put value validation for user control
> elements no matter whether CONFIG_SND_CTL_INPUT_VALIDATION is set or
> not. The kselftest will be happier with this change, as the incorrect
> values will be bailed out now with errors.
Reviewed-by: Mark Brown
signature.asc
Description: PGP signature
On Fri, Jun 14, 2024 at 02:47:26PM +0200, Takashi Iwai wrote:
> The control elements with volatile flag don't guarantee that the
> written values are actually saved for the next reads, hence they
> aren't suitable for the standard mixer tests. Skip the write tests
> for those volatile controls fo
On Thu, Jun 13, 2024 at 07:21:15PM +0530, Naresh Kamboju wrote:
> The following selftests: arm64 tests failed on FVP-aemva test and kernel
> built with gcc-13 but pass with clang.
>
> arm64_fp-stress_KERNEL-1-0/3-0/4-0/6-0 - gcc-13 - Failed
> arm64_fp-stress_KERNEL-1-0/3-0/4-0/6-0 - clang-18 - Pas
On Fri, Jun 14, 2024 at 05:37:13PM +0200, Takashi Iwai wrote:
> @@ -616,6 +616,10 @@ static int write_and_verify(struct ctl_data *ctl,
> if (!snd_ctl_elem_info_is_readable(ctl->info))
> return err;
>
> + /* Skip the verification for volatile controls, too */
> + if (s
On Fri, Jun 14, 2024 at 06:08:12PM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> +++ b/tools/testing/selftests/alsa/mixer-test.c
> @@ -668,6 +668,10 @@ static int write_and_verify(struct ctl_data *ctl,
> ksft_print_msg("%s read and writte
controls that we currently do for events to a separate
block and just verifying that whatever value we read is valid for the
control.
Signed-off-by: Mark Brown
---
tools/testing/selftests/alsa/mixer-test.c | 45 ---
1 file changed, 29 insertions(+), 16 deletions(-)
diff
adow stacks are supported it
seemed sensible to roll it in here.
[1] https://lore.kernel.org/r/20231009-arm64-gcs-v6-0-78e55deaa...@kernel.org/
Signed-off-by: Mark Brown
---
Changes in v6:
- Rebase onto v6.10-rc3.
- Ensure we don't try to free the parent shadow stack in error paths of
x86 arch co
feature let's provide some documentation covering the common aspects.
Signed-off-by: Mark Brown
---
Documentation/userspace-api/index.rst| 1 +
Documentation/userspace-api/shadow_stack.rst | 41
2 files changed, 42 insertions(+)
diff --git a/Document
interfaces.
Reviewed-by: Rick Edgecombe
Signed-off-by: Mark Brown
---
tools/testing/selftests/ksft_shstk.h | 63
1 file changed, 63 insertions(+)
diff --git a/tools/testing/selftests/ksft_shstk.h
b/tools/testing/selftests/ksft_shstk.h
new file mode 100644
index
Gupta
Reviewed-by: Rick Edgecombe
Signed-off-by: Mark Brown
---
arch/x86/Kconfig | 1 +
fs/proc/task_mmu.c | 2 +-
include/linux/mm.h | 2 +-
mm/Kconfig | 6 ++
4 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 1d7122a1883e
-by: Mark Brown
---
arch/x86/include/asm/shstk.h | 11 +++--
arch/x86/kernel/process.c| 2 +-
arch/x86/kernel/shstk.c | 104 +--
include/linux/sched/task.h | 13 ++
include/uapi/linux/sched.h | 13 --
kernel/fork.c
Signed-off-by: Mark Brown
---
tools/testing/selftests/clone3/clone3_selftests.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/testing/selftests/clone3/clone3_selftests.h
b/tools/testing/selftests/clone3/clone3_selftests.h
index 3d2663fe50ba..39b5dcba663c 100644
--- a/tools/testing/s
change.
Signed-off-by: Mark Brown
---
tools/testing/selftests/clone3/clone3.c | 77 -
1 file changed, 37 insertions(+), 40 deletions(-)
diff --git a/tools/testing/selftests/clone3/clone3.c
b/tools/testing/selftests/clone3/clone3.c
index e61f07973ce5..e066b201fa64
In order to improve diagnostics and allow tests to explicitly look for
signals check to see if the child exited due to a signal and if it did
print the code and return it as a positive value, distinct from the
negative errnos currently returned.
Signed-off-by: Mark Brown
---
tools/testing
lone3() may return
-E2BIG due to the use of newer struct versions. Currently no tests need
this but it will become an issue for testing clone3() support for shadow
stacks, the support for shadow stacks is already present on x86.
Signed-off-by: Mark Brown
---
tools/testing/selftests/clone3/clone3.
., this should be overly cautious.
Signed-off-by: Mark Brown
---
tools/testing/selftests/clone3/clone3.c | 135 +-
tools/testing/selftests/clone3/clone3_selftests.h | 38 ++
2 files changed, 172 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests
On Tue, Jun 25, 2024 at 05:54:04PM +0530, Dev Jain wrote:
> "%s" should have been used in ksft_exit_fail_msg(). Anyways, replace that
> with the recently introduced ksft_exit_fail_perror(). Also fix no mention of
> type_name in ksft_test_result_skip().
Reviewed-by: Mark Brow
et of dependencies against Linus'
tree at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git arm64-gcs
[1] https://lore.kernel.org/lkml/20230213045351.3945824-1-de...@rivosinc.com/
Signed-off-by: Mark Brown
---
Changes in v9:
- Rebase onto v6.10-rc3.
- Restructure and clar
.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/mman.h | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/include/asm/mman.h b/arch/arm64/include/asm/mman.h
index 5966ee4a6154..c21849ffdd88 100644
--- a/arch/arm64
locking interface reworked. The set status prctl()
is also reworked to just set flags, if setting/reading the shadow stack
pointer is required this could be a separate prctl.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
include/linux/mm.h | 4
include/uapi/linux
stack marker suitable for use by unwinders should be added
above that.
For arm64 the top of stack marker is all bits 0.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/x86/include/uapi/asm/mman.h | 3 ---
include/uapi/asm-generic/mman.h | 4
2 files changed, 4 insertions
FEAT_GCS introduces a number of new system registers, we require that
access to these registers is not trapped when we identify that the feature
is detected.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
Documentation/arch/arm64/booting.rst | 22 ++
1
Add some documentation of the userspace ABI for Guarded Control Stacks.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
Documentation/arch/arm64/gcs.rst | 233 +
Documentation/arch/arm64/index.rst | 1 +
2 files changed, 234 insertions
The architecture defines a format for guarded control stack caps, used
to mark the top of an unused GCS in order to limit the potential for
exploitation via stack switching. Add definitions associated with these.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64
sufficiently fast paths for this to be a problem.
Note that GCSSTTR is used to store to EL0.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/gcs.h | 51
arch/arm64/include/asm/uaccess.h | 22 +
2 files
In order for EL1 to write to an EL0 GCS it must use the GCSSTTR instruction
rather than a normal STTR. Provide a put_user_gcs() which does this.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/uaccess.h | 18 ++
1 file changed, 18
Add a cpufeature for GCS, allowing other code to conditionally support it
at runtime.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/cpufeature.h | 6 ++
arch/arm64/kernel/cpufeature.c | 16
arch/arm64/tools/cpucaps
to copy.
Since the actual effect is defined using PIE the specific bit pattern used
does not matter to the hardware but we choose two values which differ only
in PTE_WRITE in order to help share code with non-PIE cases.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64
Use VM_HIGH_ARCH_5 for guarded control stack pages.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
Documentation/filesystems/proc.rst | 2 +-
fs/proc/task_mmu.c | 3 +++
include/linux/mm.h | 12 +++-
3 files changed, 15 insertions
Map pages flagged as being part of a GCS as such rather than using the
full set of generic VM flags.
This is done using a conditional rather than extending the size of
protection_map since that would make for a very sparse array.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
There is a control HCRX_EL2.GCSEn which must be set to allow GCS
features to take effect at lower ELs and also fine grained traps for GCS
usage at EL0 and EL1. Configure all these to allow GCS usage by EL0 and
EL1.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64
Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/kvm_host.h | 14 +
arch/arm64/include/asm/vncr_mapping.h | 2 ++
arch/arm64/kvm/hyp/include/hyp/sysreg-sr.h | 48 +++---
arch/arm64/kvm/sys_regs.c | 25 +++-
4 files
Hook up an override for GCS, allowing it to be disabled from the command
line by specifying arm64.nogcs in case there are problems.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
Documentation/admin-guide/kernel-parameters.txt | 6 ++
arch/arm64/kernel/pi/idreg-override.c
Provide a hwcap to enable userspace to detect support for GCS.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
Documentation/arch/arm64/elf_hwcaps.rst | 2 ++
arch/arm64/include/asm/hwcap.h | 1 +
arch/arm64/include/uapi/asm/hwcap.h | 1 +
arch/arm64/kernel
ating any GCS
fault as fatal.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/esr.h | 28 +++-
arch/arm64/include/asm/exception.h | 2 ++
arch/arm64/kernel/entry-common.c | 23 +++
arch/arm64/kernel/tr
it
attempts to do GCS operations outside a GCS.
Signed-off-by: Mark Brown
---
arch/arm64/mm/fault.c | 43 +++
1 file changed, 43 insertions(+)
diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
index 451ba7cbd5ad..bdc28588163d 100644
--- a/arch
been disabled.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/gcs.h | 24
arch/arm64/include/asm/processor.h | 6
arch/arm64/kernel/process.c| 56 ++
arch/arm64/mm/Makefile
,
those explicitly configured by the user will not.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/gcs.h | 9 +++
arch/arm64/kernel/process.c | 29 +
arch/arm64/mm/gcs.c | 143 +++
3 files
-off-by: Mark Brown
---
arch/arm64/include/asm/gcs.h | 22 +++
arch/arm64/include/asm/processor.h | 1 +
arch/arm64/mm/gcs.c| 81 ++
3 files changed, 104 insertions(+)
diff --git a/arch/arm64/include/asm/gcs.h b/arch/arm64/include
hiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/mm/gcs.c | 61 +
1 file changed, 61 insertions(+)
diff --git a/arch/arm64/mm/gcs.c b/arch/arm64/mm/gcs.c
index c6fae0eb9bd6..918d50ba53c6 100644
--- a/arch/arm64/mm/gcs.c
+++ b/arch/arm6
;t be interpreted as
a valid token or address.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/asm/gcs.h | 1 +
arch/arm64/kernel/signal.c | 134 +--
arch/arm64/mm/gcs.c | 1 +
3 files changed, 131 insertions(
, there is a conflict
between specifying GCSPR_EL0 and allocation of a new GCS and this is not
an ancticipated use case. We also enforce GCS configuration locking on
signal return.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/include/uapi/asm/sigcontext.h | 9
Signed-off-by: Mark Brown
---
arch/arm64/include/uapi/asm/ptrace.h | 8 +
arch/arm64/kernel/ptrace.c | 59
include/uapi/linux/elf.h | 1 +
3 files changed, 68 insertions(+)
diff --git a/arch/arm64/include/uapi/asm/ptrace.h
b/arch
Provide a Kconfig option allowing the user to select if GCS support is
built into the kernel.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
arch/arm64/Kconfig | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
Add coverage of the GCS hwcap to the hwcap selftest, using a read of
GCSPR_EL0 to generate SIGILL without having to worry about enabling GCS.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/abi/hwcap.c | 19 +++
1 file changed, 19
Allow test programs to use the shadow stack helpers on arm64.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/ksft_shstk.h | 37
1 file changed, 37 insertions(+)
diff --git a/tools/testing/selftests/ksft_shstk.h
b
In order to test shadow stack support in clone3() the clone3() selftests
need to have a fully inline clone3() call, provide one for arm64.
Signed-off-by: Mark Brown
---
tools/testing/selftests/clone3/clone3_selftests.h | 26 +++
1 file changed, 26 insertions(+)
diff --git a
In preparation for testing GCS related signal handling add it as a feature
we check for in the signal handling support code.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/signal/test_signals.h | 2 ++
tools/testing/selftests/arm64/signal
Teach the framework about the GCS signal context, avoiding warnings on
the unknown context.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/signal/testcases/testcases.c | 7 +++
tools/testing/selftests/arm64/signal/testcases/testcases.h | 1
: Mark Brown
---
.../testing/selftests/arm64/signal/test_signals.h | 4 +++
.../selftests/arm64/signal/test_signals_utils.c| 29 ++
2 files changed, 23 insertions(+), 10 deletions(-)
diff --git a/tools/testing/selftests/arm64/signal/test_signals.h
b/tools/testing
anything with stacks that would cause problems with GCS we can sidestep
this issue by unconditionally enabling GCS on startup and exiting with a
call to exit() rather than a return from main().
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
.../testing/selftests/arm64/signal
This test program just covers the basic GCS ABI, covering aspects of the
ABI as standalone features without attempting to integrate things.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/Makefile| 2 +-
tools/testing/selftests/arm64/gcs
There are things like threads which nolibc struggles with which we want
to add coverage for, and the ABI allows us to test most of these even if
libc itself does not understand GCS so add a test application built
using the system libc.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
to not do that in the build system but there are no
such toolchains yet so it is not yet an issue.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/gcs/.gitignore| 1 +
tools/testing/selftests/arm64/gcs/Makefile | 2 +-
tools/testing/selft
Do some testing of the signal handling for GCS, checking that a GCS
frame has the expected information in it and that the expected signals
are delivered with invalid operations.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/signal/.gitignore
are inserted when moving a GCS using task to another CPU. The test runs for
a configurable amount of time, defaulting to 10 seconds.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/gcs/.gitignore | 2 +
tools/testing/selftests/arm64/gcs
they continue to work as before on systems without GCS.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Mark Brown
---
tools/testing/selftests/arm64/fp/assembler.h | 15 +++
tools/testing/selftests/arm64/fp/fpsimd-test.S | 2 ++
tools/testing/selftests/arm64/fp/sve-test.S
On Tue, Jun 25, 2024 at 05:54:08PM +0530, Dev Jain wrote:
> Add arm target, individual Makefile targets, and instructions to build the
> tests, along with .gitignore files. All the Makefiles are similar to
> selftests/arm64, except abi: use TEST_CUSTOM_PROGS to override the make
> rule from lib.mk
On Tue, Jun 25, 2024 at 05:54:02PM +0530, Dev Jain wrote:
> Use ifdeffery to guard code chunks meant specifically for arm64, in
> preparation for putting signal tests in selftests/arm.
I've got to say I don't love this but I'm not sure how much better we
could do if we want to share the code. Th
t; structure to the signal handler, is mangled with. The kernel must spot this
> illegal attempt and the testcases are expected to terminate via SEGV.
Reviewed-by: Mark Brown
signature.asc
Description: PGP signature
On Tue, Jun 25, 2024 at 05:54:05PM +0530, Dev Jain wrote:
> --- /dev/null
> +++ b/tools/testing/selftests/arm64/abi/ptrace.h
> @@ -0,0 +1,135 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2024 ARM Limited.
> + */
> +#include "../../kselftest.h"
> +
> +static void run_te
On Tue, Jun 25, 2024 at 05:54:07PM +0530, Dev Jain wrote:
> +static int do_child(void)
> +{
> + if (ptrace(PTRACE_TRACEME, -1, NULL, NULL))
> + ksft_exit_fail_perror("PTRACE_TRACEME");
> +
> + /* SIGTRAP makes the child stop after exec; do_parent() resumes it */
> + execv("
On Wed, Jun 26, 2024 at 02:54:09AM -0700, Zhu Jun wrote:
> Using calloc to handling memory allocation, calloc
> can initialize the allocated memory
> SKIP(return, "Can't read patterns. Probably, module isn't
> loaded");
>
> card_name = malloc(127);
> + memset(card_name,
On Wed, Jun 26, 2024 at 02:58:17AM -0700, Zhu Jun wrote:
> Add memset to initialize the requested memory
Why?
signature.asc
Description: PGP signature
On Wed, Jun 26, 2024 at 01:48:59AM -0700, Zhu Jun wrote:
> Inside of test_pcm_time() arguments are printed via printf
> but '%d' is used to print @flags (of type unsigned int).
> Use '%u' instead, just like we do everywhere else.
>
> Signed-off-by
On Wed, Jun 26, 2024 at 11:18:47AM +0530, Dev Jain wrote:
> This test asserts the relation between blocked signal, delivered signal,
> and ucontext. The ucontext is mangled with, by adding a signal mask to
> it; on return from the handler, the thread must block the corresponding
> signal.
This loo
> signal.
Reviewed-by: Mark Brown
signature.asc
Description: PGP signature
get a chance to look at it properly.
Tested-by: Mark Brown
signature.asc
Description: PGP signature
On Thu, Jul 04, 2024 at 04:36:04PM +0200, Arnd Bergmann wrote:
> #define __ARCH_WANT_SYS_CLONE
> +#define __ARCH_WANT_NEW_STAT
>
> -#ifndef __COMPAT_SYSCALL_NR
> -#include
> -#endif
> +#include
It looks like this is causing widespread build breakage in kselftest in
-next for arm64, there are
On Wed, Jul 10, 2024 at 10:57:25AM +0200, Arnd Bergmann wrote:
> Thanks for the report! I just panicked a bit and thought I had
> done something entirely wrong here, but after having a closer
> look it turned out to be a silly typo:
> -#include
> +#include
Doh, I should've spotted that even fr
On Wed, Jul 10, 2024 at 12:31:21PM +0100, Catalin Marinas wrote:
> Sorry, these patches slipped through the cracks. We seem to be pretty
> inconsistent with using ksft_exit_fail_perror() and ksft_finished(). Is
> there some plan to update the rest or is it only this location that you
> came across
On Wed, Jul 10, 2024 at 04:17:02PM +0100, Marc Zyngier wrote:
> Mark Brown wrote:
> > + if (ctxt_has_gcs(ctxt)) {
> Since this is conditioned on S1PIE, it should be only be evaluated
> when PIE is enabled in the guest.
So make ctxt_has_gcs() embed a check of
On Wed, Jul 10, 2024 at 12:36:21PM +0200, Florian Weimer wrote:
> * Mark Brown:
> > +* When GCS is enabled for the interrupted thread a signal handling specific
> > + GCS cap token will be written to the GCS, this is an architectural GCS
> > cap
> > + token with bi
On Wed, Jul 10, 2024 at 07:28:09PM +0100, Marc Zyngier wrote:
> Mark Brown wrote:
> > On Wed, Jul 10, 2024 at 04:17:02PM +0100, Marc Zyngier wrote:
> > > > + if (ctxt_has_gcs(ctxt)) {
> > > Since this is conditioned on S1PIE, it should be only be evaluated
&g
automated systems and it wasn't
that great anyway.
Signed-off-by: Mark Brown
---
tools/testing/selftests/alsa/mixer-test.c | 76 ---
tools/testing/selftests/alsa/pcm-test.c | 35 --
2 files changed, 60 insertions(+), 51 deletions(-)
diff --git a/
On Thu, Jul 11, 2024 at 06:08:38PM +0200, Jaroslav Kysela wrote:
> On 11. 07. 24 16:33, Mark Brown wrote:
> > Address this by replacing our use of card numbers with card names which are
> > more likely to be stable across runs. We use the long name since in the
> I think tha
On Fri, Jul 12, 2024 at 11:20:05AM +0200, Jaroslav Kysela wrote:
> On 12. 07. 24 10:21, Takashi Iwai wrote:
> > OTOH, longname can be really ugly to read, and it can vary because it
> > often embeds address or irq numbers in the string.
Capturing that variation is one of the goals - it should mos
On Fri, Jul 12, 2024 at 06:25:21PM +0200, Jaroslav Kysela wrote:
> On 12. 07. 24 15:00, Mark Brown wrote:
> > The trouble with the ID field is that it's too short and seems likely to
> > create collisions, for example HDA stuff just seems to default to NVidia
> > for nVi
On Sat, Jul 13, 2024 at 09:35:36AM +0200, Jaroslav Kysela wrote:
> On 12. 07. 24 20:19, Mark Brown wrote:
> > Sure, but the genesis of this patch is that probe order isn't
> > sufficiently stable and we want to avoid names based on it... using the
> > ID will be more
On Sat, Jul 13, 2024 at 08:46:43AM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > Sure, but the genesis of this patch is that probe order isn't
> > sufficiently stable and we want to avoid names based on it... using the
> > ID will be more likely to work out stable
On Mon, Jul 15, 2024 at 03:23:24PM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > Interesting - I was mainly developing on a system with multiple HDA
> > cards and was getting fairly clearly unique names.
> An AMD system usually has two HD-audio entries, and both are &
The first patch fixes unstable naming of tests due to probe ordering not
being stable, the second just provides a bit more information.
Signed-off-by: Mark Brown
---
Changes in v2:
- Switch to using ID rather than longame.
- Log the PCM ID too.
- Link to v1:
https://lore.kernel.org/r/20240711
their long names.
Signed-off-by: Mark Brown
---
tools/testing/selftests/alsa/mixer-test.c | 98 +++
tools/testing/selftests/alsa/pcm-test.c | 64 ++--
2 files changed, 104 insertions(+), 58 deletions(-)
diff --git a/tools/testing/selftests/alsa/mixer
Drivers report a string with a name for each PCM, log it during startup of
pcm-test as a diagnostic aid.
Signed-off-by: Mark Brown
---
tools/testing/selftests/alsa/pcm-test.c | 4
1 file changed, 4 insertions(+)
diff --git a/tools/testing/selftests/alsa/pcm-test.c
b/tools/testing
On Tue, Jul 16, 2024 at 06:50:12PM +, Edgecombe, Rick P wrote:
> On Wed, 2024-07-10 at 19:27 +0100, Mark Brown wrote:
> > On Wed, Jul 10, 2024 at 12:36:21PM +0200, Florian Weimer wrote:
> > > We also have a gap on x86-64 for backtrace generation because the
> > &
On Thu, Jul 18, 2024 at 01:14:41PM -0300, Thiago Jung Bauermann wrote:
> In my FVP VM, this test gets a GCS SIGSEGV before running the first test:
Do you have THP enabled? That still doesn't work (I'm expecting it to
be fixed with -rc1).
signature.asc
Description: PGP signature
On Thu, Jul 18, 2024 at 07:28:32PM -0300, Thiago Jung Bauermann wrote:
> Mark Brown writes:
> > Do you have THP enabled? That still doesn't work (I'm expecting it to
> > be fixed with -rc1).
> I did have it enabled. After turning it off in the kernel config, the
&g
On Thu, Jul 18, 2024 at 08:47:49PM -0300, Thiago Jung Bauermann wrote:
> Thiago Jung Bauermann writes:
> > # # Totals: pass:0 fail:9 xfail:0 xpass:0 skip:0 error:0
> > ok 1 selftests: arm64: gcs-stress
> Also, Shouldn't the test report "not ok" at the end considering that
> there were fails?
It
On Thu, Jul 18, 2024 at 08:34:18PM -0300, Thiago Jung Bauermann wrote:
> Mark Brown writes:
> # # Waiting for 9 children
> # # Thread-4030: Failed to enable GCS
> # # Thread-4031: Failed to enable GCS
This is already fixed locally, just rebasing bitrot.
signature.asc
Desc
adow stacks are supported it
seemed sensible to roll it in here.
[1] https://lore.kernel.org/r/20231009-arm64-gcs-v6-0-78e55deaa...@kernel.org/
Signed-off-by: Mark Brown
---
Changes in v7:
- Rebase onto v6.11-rc1.
- Typo fixes.
- Link to v6:
https://lore.kernel.org/r/20240623-clone3-shadow-stack
feature let's provide some documentation covering the common aspects.
Signed-off-by: Mark Brown
---
Documentation/userspace-api/index.rst| 1 +
Documentation/userspace-api/shadow_stack.rst | 41
2 files changed, 42 insertions(+)
diff --git a/Document
interfaces.
Reviewed-by: Rick Edgecombe
Signed-off-by: Mark Brown
---
tools/testing/selftests/ksft_shstk.h | 63
1 file changed, 63 insertions(+)
diff --git a/tools/testing/selftests/ksft_shstk.h
b/tools/testing/selftests/ksft_shstk.h
new file mode 100644
index
Gupta
Reviewed-by: Rick Edgecombe
Signed-off-by: Mark Brown
---
arch/x86/Kconfig | 1 +
fs/proc/task_mmu.c | 2 +-
include/linux/mm.h | 2 +-
mm/Kconfig | 6 ++
4 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 007bab9f2a0e
-by: Mark Brown
---
arch/x86/include/asm/shstk.h | 11 +++--
arch/x86/kernel/process.c| 2 +-
arch/x86/kernel/shstk.c | 104 +--
include/linux/sched/task.h | 13 ++
include/uapi/linux/sched.h | 13 --
kernel/fork.c
Signed-off-by: Mark Brown
---
tools/testing/selftests/clone3/clone3_selftests.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/testing/selftests/clone3/clone3_selftests.h
b/tools/testing/selftests/clone3/clone3_selftests.h
index 3d2663fe50ba..39b5dcba663c 100644
--- a/tools/testing/s
501 - 600 of 886 matches
Mail list logo