|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH for-4.13 1/2] xen/nospec: Introduce CONFIG_SPECULATIVE_ARRAY_HARDEN
On 30.09.2019 20:24, Andrew Cooper wrote:
> --- a/xen/common/Kconfig
> +++ b/xen/common/Kconfig
> @@ -77,6 +77,27 @@ config HAS_CHECKPOLICY
> string
> option env="XEN_HAS_CHECKPOLICY"
>
> +menu "Speculative hardening"
> +
> +config SPECULATIVE_ARRAY_HARDEN
Seeing also the new item in patch 2 - wouldn't it be better for them all
to have (just) a common prefix, rather than common prefix and a common
suffix. E.g. SPECULATIVE_HARDEN_ARRAYS here and SPECULATIVE_HARDEN_BRANCHES
there?
> --- a/xen/include/xen/nospec.h
> +++ b/xen/include/xen/nospec.h
> @@ -33,6 +33,7 @@ static inline unsigned long
> array_index_mask_nospec(unsigned long index,
> }
> #endif
>
> +#ifdef CONFIG_SPECULATIVE_ARRAY_HARDEN
> /*
> * array_index_nospec - sanitize an array index after a bounds check
> *
> @@ -58,6 +59,17 @@ static inline unsigned long
> array_index_mask_nospec(unsigned long index,
> \
> (typeof(_i)) (_i & _mask); \
> })
> +#else
> +/* No index hardening. */
> +#define array_index_nospec(index, size) \
> +({ \
> + typeof(index) _i = (index); \
> + typeof(size) _s = (size); \
> + \
> + (void)_s; \
> + _i; \
> +})
Why not the simpler
#define array_index_nospec(index, size) \
({ \
(void)(size); \
(index); \
})
at which point it would seem feasible to avoid the use of compiler
extensions altogether by making it
#define array_index_nospec(index, size) ((void)(size), (index))
?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |