From: ASANO Masahiro <masano@tnes.nec.co.jp>
To: trond.myklebust@fys.uio.no
Cc: matthew@wil.cx, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fix posix lock on NFS, #2
Date: Sat, 24 Dec 2005 11:56:07 +0900 (JST) [thread overview]
Message-ID: <20051224.115607.730554607.masano@tnes.nec.co.jp> (raw)
In-Reply-To: <1135350151.8167.160.camel@lade.trondhjem.org>
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [PATCH] fix posix lock on NFS, #2
Date: Fri, 23 Dec 2005 16:02:31 +0100
> On Fri, 2005-12-23 at 23:38 +0900, ASANO Masahiro wrote:
> > Here is a patch. It changes nfsd to keep the range of file_lock for
> > later use. Any comments and feedback are welcome.
> NACK. You cannot copy locks like this. See locks_copy_lock().
Thank you for pointing it out. I forgot all that point. I'm trying
to update my patch, but things are complicated.
Do you think it is safe to copy the file_lock table simply with
locks_copy_lock() at that point, or it may break nlm_blocked list in
nfsd?
--
masano
prev parent reply other threads:[~2005-12-24 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 14:38 ASANO Masahiro
2005-12-23 15:02 ` Trond Myklebust
2005-12-24 2:56 ` ASANO Masahiro [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=20051224.115607.730554607.masano@tnes.nec.co.jp \
--to=masano@tnes.nec.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=trond.myklebust@fys.uio.no \
/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®