From: Abhijith Das <adas@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] bz502531 - GFS2: smbd proccess hangs with flock() call.
Date: Mon, 01 Jun 2009 12:30:03 -0500 [thread overview]
Message-ID: <4A24101B.5020301@redhat.com> (raw)
In-Reply-To: <1243624260.3431.6.camel@localhost.localdomain>
GFS2 currently does not support mandatory flocks. An flock() call with
LOCK_MAND triggers unexpected behavior because gfs2 is not checking for
this lock type. This patch corrects that.
Signed-off-by: Abhi Das <adas@redhat.com>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bz502531-git.patch
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20090601/bbb46e11/attachment.ksh>
next prev parent reply other threads:[~2009-06-01 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 19:11 [Cluster-devel] GFS2: Add tracepoints Steven Whitehouse
2009-05-29 19:23 ` [Cluster-devel] " Christoph Hellwig
2009-05-29 19:50 ` Steven Whitehouse
2009-05-30 10:25 ` Christoph Hellwig
2009-06-01 14:19 ` Steven Whitehouse
2009-06-01 17:30 ` Abhijith Das [this message]
2009-06-02 8:08 ` [Cluster-devel] [GFS2 PATCH] bz502531 - GFS2: smbd proccess hangs with flock() call 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=4A24101B.5020301@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox