[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gfs-bugs
Subject:    [gfs-bugs] [Bug 221] Changed - flocks broken again
From:       bugzilla-daemon () sistina ! com
Date:       2001-03-08 18:51:33
[Download RAW message or body]

http://bugzilla.sistina.com/show_bug.cgi?id=221

*** shadow/221	Thu Mar  8 11:14:09 2001
--- shadow/221.tmp.4330	Thu Mar  8 12:51:33 2001
***************
*** 3,10 ****
  Version: Public CVS
  Platform: 
  OS/Version: All
! Status: ASSIGNED   
! Resolution: 
  Severity: normal
  Priority: P4
  Component: gfs
--- 3,10 ----
  Version: Public CVS
  Platform: 
  OS/Version: All
! Status: RESOLVED   
! Resolution: FIXED
  Severity: normal
  Priority: P4
  Component: gfs
***************
*** 52,54 ****
--- 52,58 ----
  time depenant bug.  If you fire off the flock commands too fast, they lose
  ordering.  I'll probably have to add a mutex ro spinlock or something to force
  ordering of flock actions.
+ 
+ ------- Additional Comments From conrad@sistina.com  2001-03-08 12:51 -------
+ Added another mutex at the inode level, This forces order on the flock commands.
+ Now they don't walkover eachother.
Read the GFS HOWTO http://www.sistina.com/gfs/Pages/howto.html
gfs-bugs mailing list
gfs-bugs@sistina.com
http://lists.sistina.com/mailman/listinfo/gfs-bugs
Read the GFS Howto:  http://www.sistina.com/gfs/Pages/howto.html

[prev in list] [next in list] [prev in thread] [next in thread]