<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [-next] nouveau corrupts kernel mm allocator" href="https://bugs.freedesktop.org/show_bug.cgi?id=58087#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [-next] nouveau corrupts kernel mm allocator" href="https://bugs.freedesktop.org/show_bug.cgi?id=58087">bug 58087</a> from <a class="email" href="mailto:peter@hurleysoftware.com" title="Peter Hurley <peter@hurleysoftware.com>"> Peter Hurley</a> <pre>(In reply to <a href="show_bug.cgi?id=58087#c3">comment #3</a>) > It's not a problem with vm allocation. The next one (vm->pgt) fails, so we > free vm, leaving *pvm pointing at freed memory. When we get to > nouveau_drm_open, we call nouveau_cli_destroy(cli), which tries to free > cli->base.vm again. Oops. Thanks for the explanation. That makes sense to me now. FYI, I did also file a bug in the kernel bugzilla for the memory allocation failure itself (kernel <a class="bz_bug_link bz_status_NEW " title="NEW --- - ignore_errors ineffective when daemon_reload performed while relevant process is running" href="show_bug.cgi?id=51301">bug 51301</a> here <a href="https://bugzilla.kernel.org/show_bug.cgi?id=51301">https://bugzilla.kernel.org/show_bug.cgi?id=51301</a>). A 32k allocation on a 10gb machine shouldn't really ever fail.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>