Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-30 Thread Tiwei Bie
On 5/30/24 4:54 PM, Benjamin Berg wrote: > Hi, > > On Thu, 2024-05-30 at 10:54 +0800, Tiwei Bie wrote: >> On 5/28/24 10:13 PM, Tiwei Bie wrote: >>> On 5/28/24 7:57 PM, Johannes Berg wrote: On Tue, 2024-05-28 at 18:16 +0800, Tiwei Bie wrote: > On 5/28/24 4:54 PM, benja...@sipsolutions.net 

Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-30 Thread Benjamin Berg
Hi, On Thu, 2024-05-30 at 10:54 +0800, Tiwei Bie wrote: > On 5/28/24 10:13 PM, Tiwei Bie wrote: > > On 5/28/24 7:57 PM, Johannes Berg wrote: > > > On Tue, 2024-05-28 at 18:16 +0800, Tiwei Bie wrote: > > > > On 5/28/24 4:54 PM, benja...@sipsolutions.net wrote: > > > > > From: Benjamin Berg > > > >

Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-29 Thread Tiwei Bie
On 5/28/24 10:13 PM, Tiwei Bie wrote: > On 5/28/24 7:57 PM, Johannes Berg wrote: >> On Tue, 2024-05-28 at 18:16 +0800, Tiwei Bie wrote: >>> On 5/28/24 4:54 PM, benja...@sipsolutions.net wrote: From: Benjamin Berg Newer glibc versions are enabling rseq support by default. This remain

Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-28 Thread Tiwei Bie
On 5/28/24 7:57 PM, Johannes Berg wrote: > On Tue, 2024-05-28 at 18:16 +0800, Tiwei Bie wrote: >> On 5/28/24 4:54 PM, benja...@sipsolutions.net wrote: >>> From: Benjamin Berg >>> >>> Newer glibc versions are enabling rseq support by default. This remains >>> enabled in the cloned child process, po

Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-28 Thread Johannes Berg
On Tue, 2024-05-28 at 18:16 +0800, Tiwei Bie wrote: > On 5/28/24 4:54 PM, benja...@sipsolutions.net wrote: > > From: Benjamin Berg > > > > Newer glibc versions are enabling rseq support by default. This remains > > enabled in the cloned child process, potentially causing the host kernel > > to wr

Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-28 Thread Tiwei Bie
Hi Benjamin, On 5/28/24 6:30 PM, Benjamin Berg wrote: > On Tue, 2024-05-28 at 18:16 +0800, Tiwei Bie wrote: >> On 5/28/24 4:54 PM, benja...@sipsolutions.net wrote: >>> From: Benjamin Berg >>> >>> Newer glibc versions are enabling rseq support by default. This remains >>> enabled in the cloned chi

Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-28 Thread Benjamin Berg
Hi Tiwei, On Tue, 2024-05-28 at 18:16 +0800, Tiwei Bie wrote: > On 5/28/24 4:54 PM, benja...@sipsolutions.net wrote: > > From: Benjamin Berg > > > > Newer glibc versions are enabling rseq support by default. This remains > > enabled in the cloned child process, potentially causing the host kerne

Re: [PATCH 3/5] um: Do a double clone to disable rseq

2024-05-28 Thread Tiwei Bie
On 5/28/24 4:54 PM, benja...@sipsolutions.net wrote: > From: Benjamin Berg > > Newer glibc versions are enabling rseq support by default. This remains > enabled in the cloned child process, potentially causing the host kernel > to write/read memory in the child. > > It appears that this was pure

[PATCH 3/5] um: Do a double clone to disable rseq

2024-05-28 Thread benjamin
From: Benjamin Berg Newer glibc versions are enabling rseq support by default. This remains enabled in the cloned child process, potentially causing the host kernel to write/read memory in the child. It appears that this was purely not an issue because the used memory area happened to be above T