From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: chrisw@sous-sol.org, matthew@wil.cx,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: DoS with POSIX file locks?
Date: Wed, 22 Mar 2006 10:56:16 -0500 [thread overview]
Message-ID: <1143042976.12871.34.camel@lade.trondhjem.org> (raw)
In-Reply-To: <E1FM2Gi-0001LF-00@dorka.pomaz.szeredi.hu>
On Wed, 2006-03-22 at 13:16 +0100, Miklos Szeredi wrote:
> > > > i concur with Trond, there's no sane way to get rid of it w/out
> > > > formalizing CLONE_FILES and locks on exec
> > >
> > > Probably there is. It would involve allocating a separate
> > > lock-owner-ID stored in files_struct but separate from it. But it's
> > > more complicated than simply not propagating locks on exec in the
> > > CLONE_FILES case.
> >
> > That doesn't solve the fundamental problem.
> >
> > You would still have to be able to tell a remote server that some locks
> > which previously belonged to one owner are being reallocated to several
> > owners.
>
> No changing of lock owner is involved, that's the whole point.
You still don't get it. For NFS/CIFS/... the locks on the server _also_
have a lock owner. The local lockowner is completely and utterly
irrelevant.
Cheers,
Trond
next prev parent reply other threads:[~2006-03-22 15:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 11:41 Miklos Szeredi
2006-03-20 12:11 ` Matthew Wilcox
2006-03-20 12:19 ` Miklos Szeredi
2006-03-20 12:39 ` Matthew Wilcox
2006-03-20 12:52 ` Miklos Szeredi
2006-03-20 13:13 ` Arjan van de Ven
2006-03-20 13:24 ` Miklos Szeredi
2006-03-20 13:30 ` Arjan van de Ven
2006-03-20 13:39 ` Miklos Szeredi
2006-03-20 15:32 ` Matthew Wilcox
2006-03-20 16:41 ` Miklos Szeredi
2006-03-20 20:35 ` J. Bruce Fields
2006-03-21 6:38 ` Miklos Szeredi
2006-03-20 18:22 ` Trond Myklebust
2006-03-21 9:44 ` Miklos Szeredi
2006-03-21 17:28 ` Trond Myklebust
2006-03-21 17:58 ` Miklos Szeredi
2006-03-21 18:16 ` Trond Myklebust
2006-03-21 19:16 ` Chris Wright
2006-03-22 6:21 ` Miklos Szeredi
2006-03-22 11:12 ` Trond Myklebust
2006-03-22 12:16 ` Miklos Szeredi
2006-03-22 15:56 ` Trond Myklebust [this message]
2006-03-22 16:34 ` Miklos Szeredi
2006-03-22 20:07 ` Trond Myklebust
2006-03-22 20:19 ` Miklos Szeredi
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=1143042976.12871.34.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=chrisw@sous-sol.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=miklos@szeredi.hu \
/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®