From: Bob Liu <lliubbo@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com,
cesarb@cesarb.net, emunson@mgebm.net, penberg@kernel.org,
namhyung@gmail.com, hannes@cmpxchg.org, mhocko@suse.cz,
lucas.demarchi@profusion.mobi, aarcange@redhat.com,
tj@kernel.org, vapier@gentoo.org, jkosina@suse.cz,
rientjes@google.com, dan.magenheimer@oracle.com,
Bob Liu <lliubbo@gmail.com>
Subject: [PATCH 2/4] frontswap: using vzalloc instead of vmalloc
Date: Thu, 4 Aug 2011 11:09:48 +0800 [thread overview]
Message-ID: <1312427390-20005-2-git-send-email-lliubbo@gmail.com> (raw)
In-Reply-To: <1312427390-20005-1-git-send-email-lliubbo@gmail.com>
This patch also add checking whether alloc frontswap_map memory
failed.
Signed-off-by: Bob Liu <lliubbo@gmail.com>
---
mm/swapfile.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/swapfile.c b/mm/swapfile.c
index ffdd06a..8fe9e88 100644
--- a/mm/swapfile.c
+++ b/mm/swapfile.c
@@ -2124,9 +2124,9 @@ SYSCALL_DEFINE2(swapon, const char __user *, specialfile, int, swap_flags)
}
/* frontswap enabled? set up bit-per-page map for frontswap */
if (frontswap_enabled) {
- frontswap_map = vmalloc(maxpages / sizeof(long));
- if (frontswap_map)
- memset(frontswap_map, 0, maxpages / sizeof(long));
+ frontswap_map = vzalloc(maxpages / sizeof(long));
+ if (!frontswap_map)
+ goto bad_swap;
}
if (p->bdev) {
--
1.6.3.3
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-04 3:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 3:09 [PATCH 1/4] page cgroup: using vzalloc instead of vmalloc Bob Liu
2011-08-04 3:09 ` Bob Liu [this message]
2011-08-04 3:09 ` [PATCH 3/4] sparse: using kzalloc to clean up code Bob Liu
2011-08-04 3:09 ` [PATCH 4/4] percpu: rename pcpu_mem_alloc to pcpu_mem_zalloc Bob Liu
2011-08-04 6:13 ` Pekka Enberg
2011-08-04 8:09 ` Michal Hocko
2011-08-04 9:04 ` Tejun Heo
2011-08-04 6:10 ` [PATCH 3/4] sparse: using kzalloc to clean up code Pekka Enberg
2011-08-04 6:55 ` Bob Liu
2011-08-04 7:22 ` Johannes Weiner
2011-08-04 7:26 ` Johannes Weiner
2011-08-04 7:37 ` Pekka Enberg
2011-08-04 8:07 ` Michal Hocko
2011-08-04 7:57 ` [PATCH 2/4] frontswap: using vzalloc instead of vmalloc Michal Hocko
2011-08-04 8:14 ` Johannes Weiner
2011-08-04 9:00 ` Michal Hocko
2011-08-04 16:47 ` Dan Magenheimer
2011-08-05 2:36 ` Bob Liu
2011-08-05 2:45 ` Dan Magenheimer
2011-08-05 2:57 ` Bob Liu
2011-08-05 18:13 ` Dan Magenheimer
2011-08-06 3:59 ` Bob Liu
2011-08-04 6:02 ` [PATCH 1/4] page cgroup: " Pekka Enberg
2011-08-04 7:23 ` Johannes Weiner
2011-08-04 7:53 ` Michal Hocko
2011-08-08 0:56 ` KAMEZAWA Hiroyuki
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=1312427390-20005-2-git-send-email-lliubbo@gmail.com \
--to=lliubbo@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=dan.magenheimer@oracle.com \
--cc=emunson@mgebm.net \
--cc=hannes@cmpxchg.org \
--cc=jkosina@suse.cz \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=mhocko@suse.cz \
--cc=namhyung@gmail.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tj@kernel.org \
--cc=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).