From: Benny Halevy <bhalevy@panasas.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrea Arcangeli <andrea@qumranet.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix uninitialized variables for find_vma_prepare callers
Date: Tue, 01 Jul 2008 14:53:07 +0300 [thread overview]
Message-ID: <486A1AA3.203@panasas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806301942220.22984@blonde.site>
On Jun. 30, 2008, 22:00 +0300, Hugh Dickins <hugh@veritas.com> wrote:
> On Mon, 30 Jun 2008, Benny Halevy wrote:
>> gcc 4.3.0 correctly emits the following warnings.
>> When a vma covering addr is found, find_vma_prepare indeed returns without
>> setting pprev, rb_link, and rb_parent.
>
> That's amusing, thank you.
>
> You may wonder how the vma rb_tree has been working all these years
> despite that. The answer is that we only use find_vma_prepare when
> about to insert a new vma: if there's anything already there, it's
> either an error condition, or we go off and unmap the overlap without
> taking any interest in those uninitialized values for linking.
>
> It would be nicer to initialize them, and your patch is certainly
> nice and simple. Would it have the effect, that it returns with
> vma == *pprev when addr falls within an existing vma?
> That would be a sensible outcome, I think.
No, *pprev will be set to the last parent encountered with this
patch, but doing what you suggested is possible, though I doubt
it matters since apparently nobody is using pprev in this path
otherwise stuff would've just broken.
Benny
>
> Hugh
>
>> [warnings snipped]
>>
>> Signed-off-by: Benny Halevy <bhalevy@panasas.com>
>> ---
>> mm/mmap.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/mm/mmap.c b/mm/mmap.c
>> index 3354fdd..81b9873 100644
>> --- a/mm/mmap.c
>> +++ b/mm/mmap.c
>> @@ -366,7 +366,7 @@ find_vma_prepare(struct mm_struct *mm, unsigned long addr,
>> if (vma_tmp->vm_end > addr) {
>> vma = vma_tmp;
>> if (vma_tmp->vm_start <= addr)
>> - return vma;
>> + break;
>> __rb_link = &__rb_parent->rb_left;
>> } else {
>> rb_prev = __rb_parent;
WARNING: multiple messages have this Message-ID (diff)
From: Benny Halevy <bhalevy@panasas.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrea Arcangeli <andrea@qumranet.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix uninitialized variables for find_vma_prepare callers
Date: Tue, 01 Jul 2008 14:53:07 +0300 [thread overview]
Message-ID: <486A1AA3.203@panasas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806301942220.22984@blonde.site>
On Jun. 30, 2008, 22:00 +0300, Hugh Dickins <hugh@veritas.com> wrote:
> On Mon, 30 Jun 2008, Benny Halevy wrote:
>> gcc 4.3.0 correctly emits the following warnings.
>> When a vma covering addr is found, find_vma_prepare indeed returns without
>> setting pprev, rb_link, and rb_parent.
>
> That's amusing, thank you.
>
> You may wonder how the vma rb_tree has been working all these years
> despite that. The answer is that we only use find_vma_prepare when
> about to insert a new vma: if there's anything already there, it's
> either an error condition, or we go off and unmap the overlap without
> taking any interest in those uninitialized values for linking.
>
> It would be nicer to initialize them, and your patch is certainly
> nice and simple. Would it have the effect, that it returns with
> vma == *pprev when addr falls within an existing vma?
> That would be a sensible outcome, I think.
No, *pprev will be set to the last parent encountered with this
patch, but doing what you suggested is possible, though I doubt
it matters since apparently nobody is using pprev in this path
otherwise stuff would've just broken.
Benny
>
> Hugh
>
>> [warnings snipped]
>>
>> Signed-off-by: Benny Halevy <bhalevy@panasas.com>
>> ---
>> mm/mmap.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/mm/mmap.c b/mm/mmap.c
>> index 3354fdd..81b9873 100644
>> --- a/mm/mmap.c
>> +++ b/mm/mmap.c
>> @@ -366,7 +366,7 @@ find_vma_prepare(struct mm_struct *mm, unsigned long addr,
>> if (vma_tmp->vm_end > addr) {
>> vma = vma_tmp;
>> if (vma_tmp->vm_start <= addr)
>> - return vma;
>> + break;
>> __rb_link = &__rb_parent->rb_left;
>> } else {
>> rb_prev = __rb_parent;
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-01 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 16:54 [PATCH] mm: fix uninitialized variables for find_vma_prepare callers Benny Halevy
2008-06-30 16:54 ` Benny Halevy
2008-06-30 19:00 ` Hugh Dickins
2008-06-30 19:00 ` Hugh Dickins
2008-07-01 11:53 ` Benny Halevy [this message]
2008-07-01 11:53 ` Benny Halevy
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=486A1AA3.203@panasas.com \
--to=bhalevy@panasas.com \
--cc=andrea@qumranet.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.