From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH][GFS2] - bz 272021: GFS2 - flocks from same process trip kernel BUG at fs/gfs2/glock.c:1118!
Date: Thu, 13 Sep 2007 23:35:27 -0500 [thread overview]
Message-ID: <46EA0F8F.8080601@redhat.com> (raw)
This patch adds a new flag to the gfs2_holder structure GL_FLOCK.
It is set on holders of glocks representing flocks. This flag is
checked in add_to_queue() and a process is permitted to queue more
than one holder onto a glock if it is set. This solves the issue
of a process not being able to do multiple flocks on the same file.
Through a single descriptor, a process can now promote and demote
flocks. Through multiple descriptors a process can now queue
multiple flocks on the same file. There's still the problem of
a process deadlocking itself (because gfs2 blocking locks are not
interruptible) by queueing incompatible deadlock.
Signed-off-by: Abhijith Das <adas@redhat.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz272021-git-new.patch
Type: text/x-patch
Size: 3496 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070913/c050e346/attachment.bin>
next reply other threads:[~2007-09-14 4:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 4:35 Abhijith Das [this message]
2007-09-14 12:26 ` [Cluster-devel] Re: [PATCH][GFS2] - bz 272021: GFS2 - flocks from same process trip kernel BUG at fs/gfs2/glock.c:1118! Steven Whitehouse
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=46EA0F8F.8080601@redhat.com \
--to=adas@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.