From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, linux-mm@kvack.org
Subject: Re: [PATCH] mm: Make vb_alloc() more foolproof
Date: Wed, 6 Jun 2012 01:02:03 +0200 [thread overview]
Message-ID: <20120605230203.GA4402@quack.suse.cz> (raw)
In-Reply-To: <20120605155601.738bde7c.akpm@linux-foundation.org>
On Tue 05-06-12 15:56:01, Andrew Morton wrote:
> On Wed, 6 Jun 2012 00:40:56 +0200
> Jan Kara <jack@suse.cz> wrote:
>
> > If someone calls vb_alloc() (or vm_map_ram() for that matter) to allocate
> > 0 bytes (0 pages), get_order() returns BITS_PER_LONG - PAGE_CACHE_SHIFT
> > and interesting stuff happens. So make debugging such problems easier and
> > warn about 0-size allocation.
> >
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> > mm/vmalloc.c | 9 +++++++++
> > 1 files changed, 9 insertions(+), 0 deletions(-)
> >
> > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > index 2aad499..bebee70 100644
> > --- a/mm/vmalloc.c
> > +++ b/mm/vmalloc.c
> > @@ -904,6 +904,15 @@ static void *vb_alloc(unsigned long size, gfp_t gfp_mask)
> >
> > BUG_ON(size & ~PAGE_MASK);
> > BUG_ON(size > PAGE_SIZE*VMAP_MAX_ALLOC);
> > + if (size == 0) {
> > + /*
> > + * Allocating 0 bytes isn't what caller wants since
> > + * get_order(0) returns funny result. Just warn and terminate
> > + * early.
> > + */
> > + WARN_ON(1);
> > + return NULL;
> > + }
> > order = get_order(size);
>
> Spose so. You got bitten, I assume ;)
Yup ;)
> We can neaten the implementation:
>
> --- a/mm/vmalloc.c~mm-make-vb_alloc-more-foolproof-fix
> +++ a/mm/vmalloc.c
> @@ -904,13 +904,12 @@ static void *vb_alloc(unsigned long size
>
> BUG_ON(size & ~PAGE_MASK);
> BUG_ON(size > PAGE_SIZE*VMAP_MAX_ALLOC);
> - if (size == 0) {
> + if (WARN_ON(size == 0)) {
Ah, nice trick :) Thanks.
> /*
> * Allocating 0 bytes isn't what caller wants since
> * get_order(0) returns funny result. Just warn and terminate
> * early.
> */
> - WARN_ON(1);
> return NULL;
> }
> order = get_order(size);
>
> and that gives us the unlikely() hit too.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
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>
prev parent reply other threads:[~2012-06-05 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 22:40 [PATCH] mm: Make vb_alloc() more foolproof Jan Kara
2012-06-05 22:56 ` Andrew Morton
2012-06-05 23:02 ` Jan Kara [this message]
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=20120605230203.GA4402@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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).