From: Andrew Morton <akpm@digeo.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: vandrove@vc.cvut.cz, helgehaf@aitel.hist.no,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vm_area_struct slab corruption
Date: Thu, 6 Mar 2003 14:52:23 -0800 [thread overview]
Message-ID: <20030306145223.67d571b1.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303061208470.2196-100000@localhost.localdomain>
Hugh Dickins <hugh@veritas.com> wrote:
>
> + * Note: mremap's move_vma VM_ACCOUNT handling assumes a partially
> + * unmapped vm_area_struct will remain in use: so lower split_vma
> + * places tmp vma above, and higher split_vma places tmp vma below.
Cough. Would it be clearer to just return the address of the surviving vma
from do_munmap()? Via an extra arg, or a PTR_ERR thingy?
next prev parent reply other threads:[~2003-03-06 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 12:29 [PATCH] vm_area_struct slab corruption Hugh Dickins
2003-03-06 22:52 ` Andrew Morton [this message]
2003-03-07 5:27 ` Hugh Dickins
2003-03-07 6:00 ` Andrew Morton
2003-03-07 12:59 ` Alan Cox
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=20030306145223.67d571b1.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=helgehaf@aitel.hist.no \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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).