From: Mark Lord <mlord@pobox.com>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vmalloc fix buggy again?
Date: Thu, 18 Mar 2004 16:11:52 -0500 [thread overview]
Message-ID: <405A1098.8080409@pobox.com> (raw)
In-Reply-To: <20040318180744.GE16242@master.mivlgu.local>
Yup.
Thanks, Sergey. I'm suffering severe brain-impairment on this one.
Please pass this on to Marcelo.
Cheers
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
Sergey Vlasov wrote:
> Hello!
>
>
>># ChangeSet
>># 2004/03/14 13:16:58-03:00 mlord...
>># [PATCH] Yet another vmalloc() fixup
>>#
>>diff -Nru a/mm/vmalloc.c b/mm/vmalloc.c
>>--- a/mm/vmalloc.c Thu Mar 18 09:44:53 2004
>>+++ b/mm/vmalloc.c Thu Mar 18 09:44:53 2004
>>@@ -184,7 +184,7 @@
>> spin_unlock(&init_mm.page_table_lock);
>> flush_cache_all();
>> if (address > start)
>>- vmfree_area_pages((address - start), address - start);
>>+ vmfree_area_pages(address, address - start);
>> return -ENOMEM;
>> }
>>
>
>
> Looks like this should be
>
> vmfree_area_pages(start, address - start);
>
prev parent reply other threads:[~2004-03-18 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 18:07 vmalloc fix buggy again? Sergey Vlasov
2004-03-18 21:11 ` Mark Lord [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=405A1098.8080409@pobox.com \
--to=mlord@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vsu@altlinux.ru \
/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