From: Seth Arnold <sarnold@wirex.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-security-module@wirex.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] LSM file locking patch is bogus
Date: Sat, 27 Jul 2002 20:02:21 -0700 [thread overview]
Message-ID: <20020727200221.C15614@wirex.com> (raw)
In-Reply-To: <20020727233149.G1441@parcelfarce.linux.theplanet.co.uk>; from matthew@wil.cx on Sat, Jul 27, 2002 at 11:31:49PM +0100
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On Sat, Jul 27, 2002 at 11:31:49PM +0100, Matthew Wilcox wrote:
> - Remove third argument from file_lock security op. Whether the lock is
> blocking or not cannot make any difference to a security module!
Matthew, thanks for the patch. However, I'm not sure that the "blocking"
field can be removed without opening up some race conditions.
Please see the following analysis of the situation by Antony Edwards,
and make sure that removing the blocking field is still safe:
http://mail.wirex.com/pipermail/linux-security-module/2002-January/002568.html
(I'd be more than happy to forward the original email to anyone who
dislikes web browsers as much as I do. Please mail me privately if you
would like me to send you a copy.)
--
http://sardonix.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-07-28 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 22:31 [PATCH] LSM file locking patch is bogus Matthew Wilcox
2002-07-28 3:02 ` Seth Arnold [this message]
2002-07-28 3:13 ` Linus Torvalds
2002-08-09 3:59 ` H. Peter Anvin
2002-07-28 18:47 ` Greg KH
2002-07-29 23:58 ` Chris Wright
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=20020727200221.C15614@wirex.com \
--to=sarnold@wirex.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=matthew@wil.cx \
--cc=torvalds@transmeta.com \
/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