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

Message-ID: <CAG27Bk32JN+9ECaH1CEsSBMqLR3KBUMQ-kZdJQ7SJLO8UxzeoA@mail.gmail.com>
Date:	Sun, 25 Nov 2012 11:11:45 +0000
From:	Sami Kerola <kerolasa@....fi>
To:	Karel Zak <kzak@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	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 Tue, Nov 20, 2012 at 12:21 PM, Karel Zak <kzak@...hat.com> wrote:
> 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.

It seems there is not much interest to have more IPC information
available in user space. Fair enough, and since nothign is exactly
broken so we can live with this.
--
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/