From: Solar Designer <solar@openwall.com>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-hardening@lists.openwall.com,
Randy Dunlap <rdunlap@xenotime.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
Daniel Lezcano <daniel.lezcano@free.fr>,
Oleg Nesterov <oleg@redhat.com>, Tejun Heo <tj@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [kernel-hardening] Re: [RFC] ipc: introduce shm_rmid_forced sysctl
Date: Sat, 2 Jul 2011 20:50:35 +0400 [thread overview]
Message-ID: <20110702165035.GC26232@openwall.com> (raw)
In-Reply-To: <20110701113533.GA19945@albatros>
On Fri, Jul 01, 2011 at 03:35:33PM +0400, Vasiliy Kulikov wrote:
> From -ow readme:
>
> "Of course, this breaks the way things are defined, so some applications
> might stop working. In particular, expect most commercial databases to
> break. Apache and PostgreSQL are known to work, though. :-)"
>
> http://www.openwall.com/linux/README.shtml
>
> But as it was written in days of Linux 2.4.x, the situation could have
> changed. A desktop system seems to work.
I wrote the above in 2.0.x days (circa 1998) and it was based on FUD
rather than on any real evidence of any breakage. Apache and PostgreSQL
were a couple of known users of shared memory segments, and these did
not break. I was not aware of any programs that presumably did break.
Of course, those probably do exist, but I don't recall anyone ever
reporting any to me (as maintainer of -ow patches), although the warning
quoted above might have played a role in such non-reporting.
Alexander
WARNING: multiple messages have this Message-ID (diff)
From: Solar Designer <solar@openwall.com>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-hardening@lists.openwall.com,
Randy Dunlap <rdunlap@xenotime.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
Daniel Lezcano <daniel.lezcano@free.fr>,
Oleg Nesterov <oleg@redhat.com>, Tejun Heo <tj@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [RFC] ipc: introduce shm_rmid_forced sysctl
Date: Sat, 2 Jul 2011 20:50:35 +0400 [thread overview]
Message-ID: <20110702165035.GC26232@openwall.com> (raw)
In-Reply-To: <20110701113533.GA19945@albatros>
On Fri, Jul 01, 2011 at 03:35:33PM +0400, Vasiliy Kulikov wrote:
> From -ow readme:
>
> "Of course, this breaks the way things are defined, so some applications
> might stop working. In particular, expect most commercial databases to
> break. Apache and PostgreSQL are known to work, though. :-)"
>
> http://www.openwall.com/linux/README.shtml
>
> But as it was written in days of Linux 2.4.x, the situation could have
> changed. A desktop system seems to work.
I wrote the above in 2.0.x days (circa 1998) and it was based on FUD
rather than on any real evidence of any breakage. Apache and PostgreSQL
were a couple of known users of shared memory segments, and these did
not break. I was not aware of any programs that presumably did break.
Of course, those probably do exist, but I don't recall anyone ever
reporting any to me (as maintainer of -ow patches), although the warning
quoted above might have played a role in such non-reporting.
Alexander
next prev parent reply other threads:[~2011-07-02 16:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 15:25 [kernel-hardening] [RFC] ipc: introduce shm_rmid_forced sysctl Vasiliy Kulikov
2011-06-22 15:25 ` Vasiliy Kulikov
2011-06-22 16:03 ` [kernel-hardening] " Randy Dunlap
2011-06-22 16:03 ` Randy Dunlap
2011-06-29 22:14 ` [kernel-hardening] " Andrew Morton
2011-06-29 22:14 ` Andrew Morton
2011-06-30 9:21 ` [kernel-hardening] " Vasiliy Kulikov
2011-06-30 9:21 ` Vasiliy Kulikov
2011-06-30 13:08 ` [kernel-hardening] " Vasiliy Kulikov
2011-06-30 13:08 ` Vasiliy Kulikov
2011-07-01 11:25 ` [kernel-hardening] " Ingo Molnar
2011-07-01 11:25 ` Ingo Molnar
2011-07-01 11:35 ` [kernel-hardening] " Vasiliy Kulikov
2011-07-01 11:35 ` Vasiliy Kulikov
2011-07-01 12:04 ` [kernel-hardening] " Ingo Molnar
2011-07-01 12:04 ` Ingo Molnar
2011-07-01 14:18 ` [kernel-hardening] " Alan Cox
2011-07-01 14:18 ` Alan Cox
2011-07-03 19:38 ` [kernel-hardening] " Ingo Molnar
2011-07-03 19:38 ` Ingo Molnar
2011-07-03 21:25 ` [kernel-hardening] " Alan Cox
2011-07-03 21:25 ` Alan Cox
2011-07-02 16:50 ` Solar Designer [this message]
2011-07-02 16:50 ` Solar Designer
2011-07-02 17:31 ` [kernel-hardening] " Solar Designer
2011-07-02 17:31 ` Solar Designer
2011-07-04 15:08 ` [kernel-hardening] " Oleg Nesterov
2011-07-04 15:08 ` Oleg Nesterov
2011-07-04 15:36 ` [kernel-hardening] " Vasiliy Kulikov
2011-07-04 15:36 ` Vasiliy Kulikov
2011-07-04 15:44 ` [kernel-hardening] " Oleg Nesterov
2011-07-04 15:44 ` Oleg Nesterov
2011-07-04 16:06 ` [kernel-hardening] " Vasiliy Kulikov
2011-07-04 16:06 ` Vasiliy Kulikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110702165035.GC26232@openwall.com \
--to=solar@openwall.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.lezcano@free.fr \
--cc=ebiederm@xmission.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=segoon@openwall.com \
--cc=serge.hallyn@canonical.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.