linux-kernel - Re: ipc: object information data in proc and sysfs

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

Date:	Tue, 20 Nov 2012 13:21:15 +0100
From:	Karel Zak <kzak@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	kerolasa@...il.com, Sami Kerola <kerolasa@....fi>,
	Al Viro <viro@...iv.linux.org.uk>,
	Doug Ledford <dledford@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	linux-kernel@...r.kernel.org
Subject: Re: ipc: object information data in proc and sysfs

On Mon, Nov 19, 2012 at 04:12:50PM -0800, Andrew Morton wrote:
> Where's the benefit in switching ipcs over to using /proc?
> 
> procfs reads are probably slower than the syscalls?

 32bit userspace and 64bit kernel (RHEL ppc64), it seems more reliable
 read from /proc than use the syscalls.

 I guess that IPC_64 flag for shmctl() commands is used by libc in 64bit
 userspace only.

    Karel

-- 
 Karel Zak  <kzak@...hat.com>
 http://karelzak.blogspot.com
--
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/