On 1/19/26 08:44, Kees Cook wrote: >> Like you noted, this is surprising. This would be a good thing to >> make sure it goes in very early after -rc1 and gets plenty of wide >> testing. > Right, we are pretty late in the dev cycle (rc6). It would be > prudent to get this into -next after the coming rc1 (1 month from > now). > > On the other hand, the changes are pretty "binary" in the sense that > mistakes should be VERY visible right away. Would it be better to > take this into -next immediately instead? I think it can go into -next ASAP. It's just a matter of when it goes to Linus.
- Re: [PATCH v4 1/3] randomize_kstack: ... Ryan Roberts
- Re: [PATCH v4 1/3] randomize_ksta... Dave Hansen
- [PATCH v4 2/3] prandom: Add __always_inline ve... Ryan Roberts
- Re: [PATCH v4 2/3] prandom: Add __always_... Jason A. Donenfeld
- Re: [PATCH v4 2/3] prandom: Add __alw... Ryan Roberts
- Re: [PATCH v4 2/3] prandom: Add _... David Laight
- Re: [PATCH v4 2/3] prandom: Add __alw... Christophe Leroy (CS GROUP)
- [PATCH v4 3/3] randomize_kstack: Unify random ... Ryan Roberts
- Re: [PATCH v4 0/3] Fix bugs and performance of... Dave Hansen
- Re: [PATCH v4 0/3] Fix bugs and performan... Kees Cook
- Re: [PATCH v4 0/3] Fix bugs and perfo... Dave Hansen
- Re: [PATCH v4 0/3] Fix bugs and perfo... Ryan Roberts
- Re: [PATCH v4 0/3] Fix bugs and p... Dave Hansen
- Re: [PATCH v4 0/3] Fix bugs a... Ryan Roberts
- Re: [PATCH v4 0/3] Fix bugs a... David Laight
- Re: [PATCH v4 0/3] Fix bugs and performance of... Heiko Carstens
