linux-kernel - Re: GFS2 file locking issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090211133648.GA10273@fogou.chygwyn.com>
Date:	Wed, 11 Feb 2009 13:36:48 +0000
From:	steve@...gwyn.com
To:	Kirill Kuvaldin <kirill.kuvaldin@...il.com>
Cc:	linux-cluster@...hat.com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: GFS2 file locking issues

Hi,

On Wed, Feb 11, 2009 at 01:55:08PM +0300, Kirill Kuvaldin wrote:
> Hi,
> 
> I'm trying to understand how the FS locking mechanism should work.
> 
> I'm running a clustered GFS2 across two nodes, each node is a Xen domU.
> To check if locking works correctly I wrote the simple perl script below.
> Basically the script opens a file, locks it to prevent others from
> writing into it, writes 20 lines into it, then unlocks and closes.
>i

It should be exactly the same on GFS and GFS2, after all the code for
flock is almost identical between the two. What mount options did you
use? Which lock manager are you using - I presume lock_dlm?

Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/