From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs inode.c ops_file.c ...
Date: Sat, 01 Dec 2007 21:51:41 -0500 [thread overview]
Message-ID: <47521DBD.30201@redhat.com> (raw)
In-Reply-To: <4750DE3C.5090004@ubuntu.com>
Fabio Massimo Di Nitto wrote:
>wcheng at sourceware.org wrote:
>
>
>>CVSROOT: /cvs/cluster
>>Module name: cluster
>>Branch: RHEL5
>>Changes by: wcheng at sourceware.org 2007-11-30 21:48:54
>>
>>Modified files:
>> gfs-kernel/src/gfs: inode.c ops_file.c ops_file.h
>>
>>Log message:
>> Red Hat bugzilla 244343:
>>
>> GFS supports two modes of locking - lock_nolock for single node filesystem
>> and lock_dlm for cluster mode locking. The gfs lock methods are removed from
>> file operation table for lock_nolock protocol. This would allow VFS to handle
>> posix lock and flock logics just like other in-tree filesystems without
>> duplication.
>>
>>Patches:
>>http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/inode.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.26&r2=1.26.2.1
>>http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_file.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.28.2.2&r2=1.28.2.3
>>http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_file.h.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.2&r2=1.2.2.1
>>
>>
>>
>
>
>Should this patch land in HEAD as well?
>
>
>
>
Yes .. but gfs(1)-kernel HEAD is currently broken .. Will review few
proposed patches (including your NFS patches) and do a clean-up first
thing next week.
-- Wendy
next prev parent reply other threads:[~2007-12-02 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 21:48 [Cluster-devel] cluster/gfs-kernel/src/gfs inode.c ops_file.c wcheng
2007-12-01 4:08 ` Fabio Massimo Di Nitto
2007-12-02 2:51 ` Wendy Cheng [this message]
2007-12-02 7:18 ` Fabio M. Di Nitto
2007-12-02 14:33 ` Wendy Cheng
2007-12-03 13:54 ` Fabio M. Di Nitto
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=47521DBD.30201@redhat.com \
--to=wcheng@redhat.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 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.