From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
torvalds@linuxfoundation.org, akpm@linuxfoundation.org,
mpm@selenic.com, linux-kernel@vger.kernel.org
Subject: Re: *sigh* /proc/*/pagemap
Date: Sat, 5 Jul 2008 10:40:26 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807051036000.2815@woody.linux-foundation.org> (raw)
In-Reply-To: <20080704185312.052e7145.akpm@linux-foundation.org>
On Fri, 4 Jul 2008, Andrew Morton wrote:
> int pagecount;
> int ret = -ESRCH;
> + static struct mm_walk pagemap_walk;
>
...
>
> + pagemap_walk.pmd_entry = pagemap_pte_range;
> + pagemap_walk.pte_hole = pagemap_pte_hole;
> + pagemap_walk.mm = mm;
> + pagemap_walk.private = ±
> +
No can do. You have one single pagemap_walk, but perhaps multiple users,
who all disagree about what it should contain.
Quite frankly, I think we should just remove the whole f*cking crap. I
think it's also potentially a security hole to give physical page
information and swap info - even if it's just your own pages.
Matt, can you explain what the point was of this whole thing? I'm really
_this_ close to just removing the POS right now. It's been a big source of
bugs, and it looks entirely pointless.
Linus
next prev parent reply other threads:[~2008-07-05 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 1:07 *sigh* /proc/*/pagemap Alexey Dobriyan
2008-07-05 1:53 ` Andrew Morton
2008-07-05 7:44 ` Alexey Dobriyan
2008-07-05 8:02 ` Andrew Morton
[not found] ` <28fa9c5e0807161906q68411e9bn5975dc277f67b086@mail.gmail.com>
2008-07-17 20:17 ` Alexey Dobriyan
2008-07-05 17:40 ` Linus Torvalds [this message]
2008-07-07 18:23 ` Matt Mackall
2008-07-07 18:34 ` Linus Torvalds
2008-07-07 18:51 ` Matt Mackall
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=alpine.LFD.1.10.0807051036000.2815@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=akpm@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=torvalds@linuxfoundation.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.