1. 05 7月, 2017 1 次提交
    • A
      gfs2: Get rid of flush_delayed_work in gfs2_evict_inode · 4fd1a579
      Andreas Gruenbacher 提交于
      So far, gfs2_evict_inode clears gl->gl_object and then flushes the glock
      work queue to make sure that inode glops which dereference gl->gl_object
      have finished running before the inode is destroyed.  However, flushing
      the work queue may do more work than needed, and in particular, it may
      call into DLM, which we want to avoid here.  Use a bit lock
      (GIF_GLOP_PENDING) to synchronize between the inode glops and
      gfs2_evict_inode instead to get rid of the flushing.
      
      In addition, flush the work queues of existing glocks before reusing
      them for new inodes to get those glocks into a known state: the glock
      state engine currently doesn't handle glock re-appropriation correctly.
      (We may be able to fix the glock state engine instead later.)
      
      Based on a patch by Steven Whitehouse <swhiteho@redhat.com>.
      Signed-off-by: NAndreas Gruenbacher <agruenba@redhat.com>
      Signed-off-by: NBob Peterson <rpeterso@redhat.com>
      4fd1a579
  2. 20 6月, 2017 1 次提交
  3. 13 6月, 2017 2 次提交
  4. 06 5月, 2017 1 次提交
    • B
      GFS2: Allow glocks to be unlocked after withdraw · ed17545d
      Bob Peterson 提交于
      This bug fixes a regression introduced by patch 0d1c7ae9.
      
      The intent of the patch was to stop promoting glocks after a
      file system is withdrawn due to a variety of errors, because doing
      so results in a BUG(). (You should be able to unmount after a
      withdraw rather than having the kernel panic.)
      
      Unfortunately, it also stopped demotions, so glocks could not be
      unlocked after withdraw, which means the unmount would hang.
      
      This patch allows function do_xmote to demote locks to an
      unlocked state after a withdraw, but not promote them.
      Signed-off-by: NBob Peterson <rpeterso@redhat.com>
      ed17545d
  5. 05 5月, 2017 4 次提交
  6. 04 5月, 2017 11 次提交
  7. 02 5月, 2017 1 次提交
  8. 29 4月, 2017 1 次提交
  9. 28 4月, 2017 6 次提交
  10. 27 4月, 2017 12 次提交