public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Smarduch <cms063@email.mot.com>
To: linux-ia64@vger.kernel.org
Subject: Re: mmap() of /dev/kmem issue
Date: Wed, 05 May 2004 14:57:41 +0000	[thread overview]
Message-ID: <409900E5.B7A8AEC7@email.mot.com> (raw)
In-Reply-To: <4097C51D.71EA0BEA@email.mot.com>

Grant Grundler wrote:

> On Tue, May 04, 2004 at 05:27:41PM -0500, Mario Smarduch wrote:
> > I would think allot of people would like to mmap() /dev/kmem
> > to take a quick look at kernel values, atleast that's what I've
> > seen on other Unix variants.
>
> yes - and that's a religious issue. I know people would
> like like to see /dev/kmem completely removed.
>
> Many wise kernel engineers have advised me to add /proc
> or similar "architected" interfaces. That way a program
> will merely get an error instead of crashing the box
> when the kernel changes it's data structures or how said
> structures get used.
>
> grant

That's understandable. But there are cases where
kernel values just need to be read timely. As things
are right now you can still corrupt the kernel but
are unable to do anything useful because of attribute
aliasing to that range. Perhaps a rejection of mapping
such regions for writes should be imposed, but I'm
not sure how mapping it as uncachable helps? To
me this behaviour seems buggy.

- Mario.


  parent reply	other threads:[~2004-05-05 14:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 16:30 mmap() of /dev/kmem issue Mario Smarduch
2004-05-04 17:05 ` Bjorn Helgaas
2004-05-04 17:19 ` Grant Grundler
2004-05-04 18:12 ` Mario Smarduch
2004-05-04 20:29 ` Grant Grundler
2004-05-04 22:15 ` Mario Smarduch
2004-05-04 22:27 ` Mario Smarduch
2004-05-04 23:59 ` Grant Grundler
2004-05-05 14:57 ` Mario Smarduch [this message]
2004-05-05 15:08 ` Luck, Tony
2004-05-05 15:36 ` Grant Grundler
2004-05-05 15:44 ` Matthew Wilcox
2004-05-05 15:49 ` Mario Smarduch
2004-05-05 15:53 ` Mario Smarduch
2004-05-05 16:07 ` Matthew Wilcox
2004-05-05 16:18 ` Chris Wedgwood
2004-05-05 16:32 ` Mario Smarduch
2004-05-05 16:42 ` Mario Smarduch
2004-05-05 16:44 ` Luck, Tony
2004-05-05 16:57 ` Mario Smarduch

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=409900E5.B7A8AEC7@email.mot.com \
    --to=cms063@email.mot.com \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox