Hi, On Wed, Jan 07, 2026 at 12:49:31AM -0600, Andy Chiu wrote: > On Sun, Dec 14, 2025 at 10:35 AM Sergey Matyukevich <[email protected]> > wrote: > > > > The vstate in thread_struct is zeroed when the vector context is > > initialized. That includes read-only register vlenb, which holds > > the vector register length in bytes. Zeroed state persists until > > mstatus.VS becomes 'dirty' and a context switch saves the actual > > hardware values. > > > > This can expose the zero vlenb value to the user-space in early > > debug scenarios, e.g. when ptrace attaches to a traced process > > early, before any vector instruction except the first one was > > executed. > > > > Fix this by specifying proper vlenb on vector context init. > > > > Signed-off-by: Sergey Matyukevich <[email protected]> > > Reviewed-by: Andy Chiu <[email protected]> >
Thanks for reviews ! What would be the recommended way to proceed with these patches ? I have reviews from Andy for the patches 1,2 and 5 (selftest for 2). They can be used independently of the remainig ptrace v-state validation changes and their tests. Would it make sense to split the series into two parts, so that the v-state validation can continue evolve independently ? Regards, Sergey
