linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20130308120308.4f1ad93c4aed631185494201@lavabit.com>
Date:	Fri, 8 Mar 2013 12:03:08 -0800
From:	rh <richard_hubbe11@...abit.com>
To:	linux-kernel@...r.kernel.org
Subject: IPC Namespace Depends and SYSVIPC

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.

______________________
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])

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