On Wed, Aug 21, 2024 at 06:23:18PM +0100, Mark Brown wrote: > On Wed, Aug 21, 2024 at 03:54:49PM +0000, Edgecombe, Rick P wrote: > > On Wed, 2024-08-21 at 13:45 +0100, Mark Brown wrote: > > > > Sorry for that. I looked through all the old threads expecting to find > > > > discussion, but couldn't find an answer. Is clone3 support a dependency for > > > > arm shadow stacks? > > > > Catalin didn't want to merge the arm64 support without clone3(), and > > > there's code dependencies as a result. I could unpick it and reverse > > > the ordering so long as the arm64 maintainers are OK with that since the > > > overlap is in the implementation of copy_thread() and some of the > > > dependency patches. > > Actually in an off-list discussion today Catalin indicated that he's > fine with relaxing that a little so I'm in the process of picking the > dependency apart. Just to confirm, I'd rather get the clone3() ABI choices properly debated than rushing it. It seems that our libc support does not rely on clone3() yet, so let's continue with the arm64 series independently of this one (only clone() with default shadow stack allocation). We'll follow up with the clone3() support that covers both architectures. Thanks and sorry for the confusion. I did not realise the complications of adding clone3() support. -- Catalin
