From: Chris Wright <chrisw@osdl.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Chris Wright <chrisw@osdl.org>, Andrew Morton <akpm@osdl.org>,
Michael Kerrisk <michael.kerrisk@gmx.net>,
Linus Torvalds <torvalds@osdl.org>,
Manfred Spraul <manfred@colorfullife.com>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] shmtcl SHM_LOCK perms
Date: Tue, 30 Nov 2004 20:55:33 -0800 [thread overview]
Message-ID: <20041130205533.O2357@build.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0412010049520.3344-100000@localhost.localdomain>; from hugh@veritas.com on Wed, Dec 01, 2004 at 01:00:13AM +0000
* Hugh Dickins (hugh@veritas.com) wrote:
> But that's not the only reason for SHM_LOCK, and all you're telling us
> there is that the owner of sensitive data should be careful who they
> give read permission to - indeed! So I still tend to agree with
> Michael, that the most natural restriction is to owner or creator -
> relax that if some app actually has a good case for relaxing it.
Yup, I agree.
thanks,
-chris
prev parent reply other threads:[~2004-12-01 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 19:09 Hugh Dickins
2004-11-30 20:50 ` Chris Wright
2004-12-01 1:00 ` Hugh Dickins
2004-12-01 4:55 ` Chris Wright [this message]
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=20041130205533.O2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=michael.kerrisk@gmx.net \
--cc=riel@redhat.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®