On Tue, May 19, 2026 at 9:11 PM Afi0 <[email protected]> wrote:
>
> Hi,
>
> You are right, the commit message overstates the impact. The actual result is 
> an immediate kernel oops, not an OOB write into adjacent slab objects. The 
> fix is still correct - checking the return value avoids the oops. Shall I 
> send a v3 with a corrected commit message?

Yes, please send v3.

Sami

Reply via email to