DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=Y+5yjcFGffxufJF+2E6vonizsS69QUO5DwqkD5JKqyx6LnIHVIfKlMyl/NXOeFlZ9o
         FwcILoDuPrLgHKo0aC3666KwVZXNe1CJVz0ZjNUVDgDtaD5hFP99weVMCUZc86q7g0Gy
         A3FjQn3oI2jZelXSQDhtdwNa07ABHxsqnZtAk=
MIME-Version: 1.0
Date: Sun, 17 Jan 2010 18:47:10 +0200
Message-ID: <af0693f01001170847r49083075hc538a42b6bcd65ab@mail.gmail.com>
Subject: /dev/mem implementation
From: Felix Rubinstein <felixru@gmail.com>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1191
Lines: 29

The recent kernels use CONFIG_STRICT_DEVMEM and CONFIG_X86_PAT
concerning the /dev/mem (/dev/kmem) so interchangeably one cannot
figure out what exactly does it mean to access the /dev/mem if both
CONFIG_STRICT_DEVMEM and CONFIG_X86_PAT are disabled.

It would be more logically to remove pat_enabled variable in
arch/x86/mm/pat.c and to make everything under CONFIG_X86_PAT define.
The same goes for phys_mem_access_prot_allowed function (from
arch/x86/mm/pat.c) even though CONFIG_X86_PAT is disabled.
To make the story worse there are four implementations of
range_is_allowed depending on how CONFIG_STRICT_DEVMEM and
CONFIG_X86_PAT are defined.


I see the motivation to limit the access to DRAM from root account
CONFIG_STRICT_DEVMEM by mmap'ing /dev/[k]mem but it's easily overruled
by simple char driver and implementing mmap of it's own totally
bypassing all limitations.

What do you think about it guy?
Appreciate it.

Thanks,
Felix R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/