f2fs: fix to cover sentry_lock for block allocation
authorJaegeuk Kim <jaegeuk@kernel.org>
Wed, 11 Mar 2015 17:42:48 +0000 (13:42 -0400)
committerJaegeuk Kim <jaegeuk@kernel.org>
Fri, 10 Apr 2015 22:08:43 +0000 (15:08 -0700)
commit21cb1d99bcc77252e6426010bcc6433f75b581bb
treecb96433d02fea464b2ce630fd6afd32059d0fb49
parentd6d4f1cb912d9bcf988a529d0934568d4550f7b5
f2fs: fix to cover sentry_lock for block allocation

In the following call stack, f2fs changes the bitmap for dirty segments and # of
dirty sentries without grabbing sit_i->sentry_lock.
This can result in mismatch on bitmap and # of dirty sentries, since if there
are some direct_io operations.

In allocate_data_block,
 - __allocate_new_segments
  - mutex_lock(&curseg->curseg_mutex);
  - s_ops->allocate_segment
   - new_curseg/change_curseg
    - reset_curseg
     - __set_sit_entry_type
      - __mark_sit_entry_dirty
       - set_bit(dirty_sentries_bitmap)
       - dirty_sentries++;

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/segment.c