public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Hudson <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix mmap_kmem (was: [question] What's the difference between /dev/kmem and /dev/mem)
Date: Sat, 13 Aug 2005 09:57:02 -0700	[thread overview]
Message-ID: <bda6d13a05081309575498f1bb@mail.gmail.com> (raw)
In-Reply-To: <1123951810.3187.20.camel@laptopd505.fenrus.org>

On 8/13/05, Arjan van de Ven <arjan@infradead.org> wrote:
> On Fri, 2005-08-12 at 09:35 -0700, Linus Torvalds wrote:
> >
> > On Thu, 11 Aug 2005, Steven Rostedt wrote:
> > >
> > > Found the problem.  It is a bug with mmap_kmem.  The order of checks is
> > > wrong, so here's the patch.  Attached is a little program that reads the
> > > System map looking for the variable modprobe_path.  If it finds it, then
> > > it opens /dev/kmem for read only and mmaping it to read the contents of
> > > modprobe_path.
> >
> > I'm actually more inclined to try to deprecate /dev/kmem.. I don't think
> > anybody has ever really used it except for some rootkits. It only exists
> > in the first place because it's historical.
> >
> > We do need to support /dev/mem for X, but even that might go away some
> > day.
> >
> > So I'd be perfectly happy to fix this, but I'd be even happier if we made
> > the whole kmem thing a config variable (maybe even default it to "off").
> 
I believe rootkit detectors, as well as some versions of ps (wchan
field) use kmem.

  parent reply	other threads:[~2005-08-13 16:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 21:36 [question] What's the difference between /dev/kmem and /dev/mem Steven Rostedt
2005-08-12  1:15 ` [PATCH] Fix mmap_kmem (was: [question] What's the difference between /dev/kmem and /dev/mem) Steven Rostedt
2005-08-12 14:25   ` Hugh Dickins
2005-08-12 16:35   ` Linus Torvalds
2005-08-12 16:56     ` Dave Jones
2005-08-12 17:07       ` Steven Rostedt
2005-08-12 17:16         ` Arjan van de Ven
2005-08-12 17:32           ` Steven Rostedt
2005-08-12 17:01     ` Steven Rostedt
2005-08-13 13:39     ` [PATCH] Fix mmap kmem " Nicolas George
2005-08-13 16:50     ` [PATCH] Fix mmap_kmem " Arjan van de Ven
2005-08-13 16:56       ` Linus Torvalds
2005-08-13 17:25         ` Arjan van de Ven
2005-08-13 17:37           ` Linus Torvalds
2005-08-13 18:18             ` Arjan van de Ven
2005-08-16 22:12               ` Greg Edwards
2005-08-16 23:33                 ` Alan Cox
2005-08-16 23:47                   ` Steven Rostedt
2005-08-15 19:33             ` Olaf Hering
2005-08-15 21:14               ` Jeff Dike
2005-08-15 21:50                 ` Olaf Hering
2005-08-15 22:41               ` Linus Torvalds
2005-08-16  1:16             ` Steven Rostedt
2005-08-16  1:22               ` Steven Rostedt
2005-08-16  1:36                 ` Linus Torvalds
2005-08-13 16:57       ` Joshua Hudson [this message]
2005-08-13 17:27         ` Arjan van de Ven
2005-08-14 14:50       ` Martin J. Bligh
2005-08-18 14:07         ` Arjan van de Ven
2005-08-18 14:18           ` Steven Rostedt
     [not found] <1123796188.17269.127.camel@localhost.localdomain.suse.lists.linux.kernel>
     [not found] ` <1123809302.17269.139.camel@localhost.localdomain.suse.lists.linux.kernel>
     [not found]   ` <Pine.LNX.4.58.0508120930150.3295@g5.osdl.org.suse.lists.linux.kernel>
2005-08-12 16:54     ` Andi Kleen
2005-08-12 17:56       ` Arjan van de Ven
2005-08-12 18:26         ` Andi Kleen
2005-08-13  9:56       ` Ingo Oeser
2005-08-13 12:40         ` Andi Kleen

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=bda6d13a05081309575498f1bb@mail.gmail.com \
    --to=joshudson@gmail.com \
    --cc=linux-kernel@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