_args we pass that into the
> shadow stack code rather than individual fields.
>
> Portions of the x86 architecture code were written by Rick Edgecombe.
>
> Acked-by: Yury Khrustalev
> Signed-off-by: Mark Brown
Tested on a fast model with a WIP Glibc patch that uses extende
now
> using more fields from the kernel_clone_args we pass that into the
> shadow stack code rather than individual fields.
>
> Portions of the x86 architecture code were written by Rick Edgecombe.
>
> Acked-by: Yury Khrustalev
LGTM. I've tested this change on the FVP model
> using more fields from the kernel_clone_args we pass that into the
> shadow stack code rather than individual fields.
>
> Portions of the x86 architecture code were written by Rick Edgecombe.
>
> Signed-off-by: Mark Brown
Acked-by: Yury Khrustalev
> @@
by: Mark Brown
> ---
> Documentation/userspace-api/index.rst| 1 +
> Documentation/userspace-api/shadow_stack.rst | 42
> ++++
> 2 files changed, 43 insertions(+)
Acked-by: Yury Khrustalev
On Wed, Oct 30, 2024 at 02:08:59PM +, Mark Brown wrote:
> On Sat, Oct 05, 2024 at 11:31:27AM +0100, Mark Brown wrote:
> > The kernel has recently added support for shadow stacks, currently
> > x86 only using their CET feature but both arm64 and RISC-V have
> > equivalent features (GCS and Zicfi
On Tue, Oct 01, 2024 at 05:12:38PM +0200, Christian Brauner wrote:
> > Thanks for the info!
> >
> > >
> > > My preference is to keep the api consistent and require a stack_size for
> > > shadow stacks as well.
> >
> > Did you catch that a token can be at a different offsets location on the
> >
6 matches
Mail list logo