linux-kernel - Re: [S390] mm: add devmem_is_allowed() for STRICT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101118095837.4ef7c563@mschwide.boeblingen.de.ibm.com>
Date:	Thu, 18 Nov 2010 09:58:37 +0100
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Dave Jones <davej@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	brueckner@...ux.vnet.ibm.com
Subject: Re: [S390] mm: add devmem_is_allowed() for STRICT_DEVMEM checking

On Wed, 17 Nov 2010 13:03:21 -0500
Dave Jones <davej@...hat.com> wrote:

> On Tue, Nov 16, 2010 at 11:59:03PM +0000, Linux Kernel wrote:
>  > Gitweb:     http://git.kernel.org/linus/ec6743bb06510c7b629603ce35713d6ae9273579
>  > Commit:     ec6743bb06510c7b629603ce35713d6ae9273579
>  > Parent:     ca768b663131ca644689fcadc9ca092dcc96a758
>  > Author:     Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>
>  > AuthorDate: Wed Nov 10 10:05:55 2010 +0100
>  > Committer:  Martin Schwidefsky <sky@...hwide.boeblingen.de.ibm.com>
>  > CommitDate: Wed Nov 10 10:05:54 2010 +0100
>  > 
>  >     [S390] mm: add devmem_is_allowed() for STRICT_DEVMEM checking
>  >     
>  >     Provide the devmem_is_allowed() routine to restrict access to
>  >     kernel memory from userspace.
>  >     Set the CONFIG_STRICT_DEVMEM config option to switch on checking.
>  >     
>  >     Signed-off-by: Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>
>  >     Signed-off-by: Martin Schwidefsky <schwidefsky@...ibm.com>
> 
> [snip add kconfig]
> 
> ...
> 
>  > +static inline int devmem_is_allowed(unsigned long pfn)
>  > +{
>  > +	return 0;
>  > +}
> 
> So you add the config option that promises security, but then you always
> allow the access.  This seems pointless ?  Why bother having the option at all?

It is the other way around, access is always disallowed. So it is very secure,
access via /dev/mem is disabled if STRICT_DEVMEM=y.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

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