From: walt <w41ter@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] Fix vmalloc regression
Date: Fri, 07 Nov 2008 13:56:10 -0800 [thread overview]
Message-ID: <gf2dhq$l1d$1@ger.gmane.org> (raw)
In-Reply-To: <1226097354-7523-1-git-send-email-glommer@redhat.com>
Glauber Costa wrote:
> Nick,
>
> This is the whole set of patches I was talking about.
> Patch 3 is the one that in fact fixes the problem...
Yep, patch 3 works for me, thanks. Only the 32-bit kernel
seems to need the patch, FWIW.
next prev parent reply other threads:[~2008-11-07 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 22:35 [PATCH 0/4] Fix vmalloc regression Glauber Costa
2008-11-07 21:56 ` walt [this message]
2008-11-07 22:35 ` [PATCH 1/4] don't call __vmalloc from other vmap internal functions Glauber Costa
2008-11-07 22:35 ` [PATCH 2/4] show size of failing allocation Glauber Costa
2008-11-07 22:35 ` [PATCH 3/4] restart search at beggining of vmalloc address Glauber Costa
2008-11-07 22:35 ` [PATCH 4/4] Do not use guard pages in non-debug kernels Glauber Costa
2008-11-14 17:53 ` [PATCH 3/4] restart search at beggining of vmalloc address walt
2008-11-08 0:58 ` [PATCH 0/4] Fix vmalloc regression Nick Piggin
2008-11-08 2:13 ` Glauber Costa
2008-11-08 2:54 ` Nick Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gf2dhq$l1d$1@ger.gmane.org' \
--to=w41ter@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox