From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: Hugh Dickins <hugh@veritas.com>,
vandrove@vc.cvut.cz, helgehaf@aitel.hist.no,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vm_area_struct slab corruption
Date: 07 Mar 2003 12:59:57 +0000 [thread overview]
Message-ID: <1047041996.20794.21.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030306220053.1d757ed6.akpm@digeo.com>
On Fri, 2003-03-07 at 06:00, Andrew Morton wrote:
> This looks pretty simple? Is it not just a matter of propagating that flag
> down to unmap_region()? I don't see where drivers and such are involved?
Only two or three. i8xx DRM uses do_munmap as does ipc/shm.c. I think the
shmem fs may also do so but I'd have to check.
prev parent reply other threads:[~2003-03-07 11:43 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
2003-03-07 5:27 ` Hugh Dickins
2003-03-07 6:00 ` Andrew Morton
2003-03-07 12:59 ` Alan Cox [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=1047041996.20794.21.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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).