The 07/11/2024 10:50, Joey Gouly wrote:
> On Mon, Jul 08, 2024 at 06:53:18PM +0100, Catalin Marinas wrote:
> > On Mon, Jun 17, 2024 at 03:51:35PM +0100, Szabolcs Nagy wrote:
> > > to me it makes sense to have abstract
> > >
> > > PKEY_D
The 07/08/2024 18:53, Catalin Marinas wrote:
> Hi Szabolcs,
>
> On Mon, Jun 17, 2024 at 03:51:35PM +0100, Szabolcs Nagy wrote:
> > The 06/17/2024 15:40, Florian Weimer wrote:
> > > >> A user can still set it by interacting with the register directly, but
>
The 06/17/2024 15:40, Florian Weimer wrote:
> >> A user can still set it by interacting with the register directly, but I
> >> guess
> >> we want something for the glibc interface..
> >>
> >> Dave, any thoughts here?
> >
> > adding Florian too, since i found an old thread of his that tried
> > to
The 05/31/2024 16:21, Joey Gouly wrote:
> Hi Szabolcs,
>
> On Fri, May 31, 2024 at 03:57:07PM +0100, Szabolcs Nagy wrote:
> > The 05/03/2024 14:01, Joey Gouly wrote:
> > > Implement the PKEYS interface, using the Permission Overlay Extension.
> > ...
> > > +
The 05/03/2024 14:01, Joey Gouly wrote:
> Implement the PKEYS interface, using the Permission Overlay Extension.
...
> +#ifdef CONFIG_ARCH_HAS_PKEYS
> +int arch_set_user_pkey_access(struct task_struct *tsk, int pkey, unsigned
> long init_val)
> +{
> + u64 new_por = POE_RXW;
> + u64 old_por
The 10/17/2023 18:14, Peter Bergner wrote:
> CCing linux-kernel for more exposure.
>
> PING. I'm waiting on a reply from anyone on the kernel side of things
> to see whether they have an issue with reserving values for AT_HWCAP3
> and AT_HWCAP4.
>
> I'll note reviews from the GLIBC camp did no
* Nicholas Piggin [2020-04-20 12:08:36 +1000]:
> Excerpts from Rich Felker's message of April 20, 2020 11:29 am:
> > Also, allowing patching of executable pages is generally frowned upon
> > these days because W^X is a desirable hardening property.
>
> Right, it would want be write-protected afte
* Nicholas Piggin via Libc-alpha [2020-04-16
10:16:54 +1000]:
> Well it would have to test HWCAP and patch in or branch to two
> completely different sequences including register save/restores yes.
> You could have the same asm and matching clobbers to put the sequence
> inline and then you coul
* Christian Brauner [2019-05-23 17:47:46 +0200]:
> This adds the close_range() syscall. It allows to efficiently close a range
> of file descriptors up to all file descriptors of a calling task.
>
> The syscall came up in a recent discussion around the new mount API and
> making new file descript
