linux-kernel - Re: IPC Namespace Depends and SYSVIPC

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: <513F7364.50408@infradead.org>
Date:	Tue, 12 Mar 2013 11:26:44 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	linux-kernel@...r.kernel.org
Subject: Re: IPC Namespace Depends and SYSVIPC

On 03/08/13 12:03, rh wrote:
> Not sure what I'm looking at but here's what I see when I do a sym
> search in nconfig.  Note: Namespace seems to depend in SYSVIPC or
> not.

from init/Kconfig:

config IPC_NS
	bool "IPC namespace"
	depends on (SYSVIPC || POSIX_MQUEUE)
	default y

so as long as POSIX_MQUEUE is enabled, the value of SYSVIPC does not matter.

or did I misunderstand your statement/confusion/question?


> ______________________
> With SYSVIPC enabled:
> 
> Symbol: IPC_NS [=y]
> Type  : boolean
> Prompt: IPC namespace
> Defined at init/Kconfig:794
> Depends on: NAMESPACES [=y] && (SYSVIPC [=y] || POSIX_MQUEUE [=y])
> Location:
> -> General setup
> -> Namespaces support (NAMESPACES [=y])
> 
> _______________________
> With SYSVIPC disabled:
> 
> 
> Symbol: IPC_NS [=y]
> Type  : boolean
> Prompt: IPC namespace
> Defined at init/Kconfig:794
> Depends on: NAMESPACES [=y] && (SYSVIPC [=n] || POSIX_MQUEUE [=y])
> Location:
> -> General setup
> -> Namespaces support (NAMESPACES [=y])


-- 
~Randy
--
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/