linux-kernel - Re: [PATCH v8 14/21] mm/mmap: Avoid zeroing vma tree in mmap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <374424db-4b16-4d19-b372-c51f00a62db0@lucifer.local>
Date: Tue, 1 Oct 2024 12:23:39 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Bert Karwatzki <spasswolf@....de>
Cc: "Liam R . Howlett" <Liam.Howlett@...cle.com>,
        Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 14/21] mm/mmap: Avoid zeroing vma tree in mmap_region()

On Tue, Oct 01, 2024 at 12:42:33PM GMT, Bert Karwatzki wrote:
> Am Dienstag, dem 01.10.2024 um 11:33 +0100 schrieb Lorenzo Stoakes:
> >
> >
> > OK so what is less perfect is this looks very genuine and present in rc1 so
> > yeah.
> >
> > Thanks so much for helping out here - I may ask you to try some patches if
> > that's ok at some point?
> >
> > Cheers, Lorenzo
> >
> Yes, that would be ok. As a sidenote, when I first got this bug I conducted an
> internet search and found this vaguely similar report:
> https://lkml.org/lkml/2024/8/28/1558
> The report says its from 6.10.0, that would be not related, but at least from
> the date it's possible that it could have tested the v7 patchset.
>
> Bert Karwatzki
> >

Thanks it looks similar but as I noted there, I couldn't repro it [0], the sender
sent a bunch of seemingly bogus reports in a flurry and it seemed to be on exit
whwere the issue occurred rather than anything the change did.

Of course that could be due to maple tree corruption that only got flagged on
exit, similar to your situation.

Unfortunately we got no further information or details and the report was sparse
so I don't think it hugely helps us.

Thankfully here we have a repro-able situation (albeit, painful, sorry about
that!) so we should be able to figure this out.

[0]:https://lore.kernel.org/linux-mm/e50f9da1-521d-46ae-9e12-d82c4c093223@lucifer.local/