linux-kernel - Re: [PATCH] restart search at beggining of vmalloc address

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: <20081107110613.GA15827@poweredge.glommer>
Date:	Fri, 7 Nov 2008 09:06:13 -0200
From:	Glauber Costa <glommer@...hat.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org, avi@...hat.com
Subject: Re: [PATCH] restart search at beggining of vmalloc address

On Fri, Nov 07, 2008 at 01:27:42AM +0100, Nick Piggin wrote:
> Excellent, thank you! Good catch
> 
> If you agree my previous patch was also good in combination with this one,
> then I'll send them all to be merged.
I'll test it with conjunction with my patch to be sure it does not retrigger
the bug I had. But I'm sure it won't (famous last words)

I also had two more patches that I wrote that aided me in debugging this, that
I'd like to see included:
 * the first shows the size of the failing allocation: We can see current allocations
   with /proc/vmallocinfo, but it's hard to get a grasp at what's the size of the allocation
   that just failed, because it is not registered.
 * the second, shows the real name of the callers in vmallocinfo, instead of things like
   "vmalloc_32", which is just an intermediate.

My plan was to send them today, after getting comments from you on this one.
If you think they are all reasonable, maybe we can send them all as a series.

> 
> Thanks,
> Nick
> 
> On Thu, Nov 06, 2008 at 06:58:26PM -0200, Glauber Costa wrote:
> > Current vmalloc restart search for a free area in case we
> > can't find one. The reason is there are areas which are lazily
> > freed, and could be possibly freed now. However, current implementation
> > start searching the tree from the last failing address, which is
> > pretty much by definition at the end of address space. So, we fail.
> > 
> > The proposal of this patch is to restart the search from the beginning
> > of the requested vstart address. This fixes the regression in running
> > KVM virtual machines for me, described in
> > http://lkml.org/lkml/2008/10/28/349, caused by commit
> > db64fe02258f1507e13fe5212a989922323685ce.
> > 
> > Signed-off-by: Glauber Costa <glommer@...hat.com>
> > CC: Nick Piggin <npiggin@...e.de>
> > ---
> >  mm/vmalloc.c |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> > 
> > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > index 7db493d..6fe2003 100644
> > --- a/mm/vmalloc.c
> > +++ b/mm/vmalloc.c
> > @@ -378,6 +378,7 @@ found:
> >  		if (!purged) {
> >  			purge_vmap_area_lazy();
> >  			purged = 1;
> > +			addr = ALIGN(vstart, align);
> >  			goto retry;
> >  		}
> >  		if (printk_ratelimit())
> > -- 
> > 1.5.6.5
--
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/