linux-kernel - Re: [PATCH] Prevent an oops in vmalloc

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] [day] [month] [year] [list]

Message-Id: <20061109144143.11fbca6d.akpm@osdl.org>
Date:	Thu, 9 Nov 2006 14:41:43 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Eric Dumazet <dada1@...mosbay.com>
Cc:	Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Prevent an oops in vmalloc_user()

On Thu, 09 Nov 2006 23:29:34 +0100
Eric Dumazet <dada1@...mosbay.com> wrote:

> Jonathan Corbet a __crit :
> > Prevent an oops in vmalloc_user()
> > 
> > If an attempt to allocate memory with vmalloc_user() fails, the result
> > will be an oops when it tries to tweak the flags in the (non-existent)
> > VMA.  One could argue that __find_vm_area() should not return a random
> > pointer on failure, but vmalloc_user() requires a check regardless.
> > 
> 
> Yes, I already posted a patch for that, and other problem as well.
> 
> http://lkml.org/lkml/2006/10/23/86
> 
> Maybe it was lost...
> 

It's in -mm but I'd queued it for 2.6.20 because you went and mixed a bunch
of things into the same patch.

Whatever - I'll push it for 2.6.19.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/