linux-toradex.git/fs/f2fs/super.c, branch v4.10

block: Rename blk_queue_zone_size and bdev_zone_size

2017-01-12T14:58:32+00:00

All block device data fields and functions returning a number of 512B
sectors are by convention named xxx_sectors while names in the form
xxx_size are generally used for a number of bytes. The blk_queue_zone_size
and bdev_zone_size functions were not following this convention so rename
them.

No functional change is introduced by this patch.

Signed-off-by: Damien Le Moal 

Collapsed the two patches, they were nonsensically split and broke
bisection.

Signed-off-by: Jens Axboe

Merge tag 'for-f2fs-4.10' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs

2016-12-14T17:07:36+00:00

Pull f2fs updates from Jaegeuk Kim:
 "This patch series contains several performance tuning patches
  regarding to the IO submission flow, in addition to supporting new
  features such as a ZBC-base drive and multiple devices.

  It also includes some major bug fixes such as:
   - checkpoint version control
   - fdatasync-related roll-forward recovery routine
   - memory boundary or null-pointer access in corner cases
   - missing error cases

  It has various minor clean-up patches as well"

* tag 'for-f2fs-4.10' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs: (66 commits)
  f2fs: fix a missing size change in f2fs_setattr
  f2fs: fix to access nullified flush_cmd_control pointer
  f2fs: free meta pages if sanity check for ckpt is failed
  f2fs: detect wrong layout
  f2fs: call sync_fs when f2fs is idle
  Revert "f2fs: use percpu_counter for # of dirty pages in inode"
  f2fs: return AOP_WRITEPAGE_ACTIVATE for writepage
  f2fs: do not activate auto_recovery for fallocated i_size
  f2fs: fix to determine start_cp_addr by sbi->cur_cp_pack
  f2fs: fix 32-bit build
  f2fs: set ->owner for debugfs status file's file_operations
  f2fs: fix incorrect free inode count in ->statfs
  f2fs: drop duplicate header timer.h
  f2fs: fix wrong AUTO_RECOVER condition
  f2fs: do not recover i_size if it's valid
  f2fs: fix fdatasync
  f2fs: fix to account total free nid correctly
  f2fs: fix an infinite loop when flush nodes in cp
  f2fs: don't wait writeback for datas during checkpoint
  f2fs: fix wrong written_valid_blocks counting
  ...

f2fs: fix to access nullified flush_cmd_control pointer

2016-12-08T02:56:50+00:00

f2fs_sync_file()             remount_ro
 - f2fs_readonly
                               - destroy_flush_cmd_control
 - f2fs_issue_flush
   - no fcc pointer!

So, this patch doesn't free fcc in this case, but just stop its kernel thread
which sends flush commands.

Signed-off-by: Jaegeuk Kim

f2fs: detect wrong layout

2016-12-07T22:37:33+00:00

Previous mkfs.f2fs allows small partition inappropriately, so f2fs should detect
that as well.

Refer this in f2fs-tools.

mkfs.f2fs: detect small partition by overprovision ratio and # of segments

Reported-and-Tested-by: Eric Biggers 
Signed-off-by: Jaegeuk Kim

Revert "f2fs: use percpu_counter for # of dirty pages in inode"

2016-12-05T19:43:59+00:00

This reverts commit 1beba1b3a953107c3ff5448ab4e4297db4619c76.

The perpcu_counter doesn't provide atomicity in single core and consume more
DRAM. That incurs fs_mark test failure due to ENOMEM.

Cc: stable@vger.kernel.org # 4.7+
Signed-off-by: Jaegeuk Kim

f2fs: fix incorrect free inode count in ->statfs

2016-11-25T18:16:07+00:00

While calculating inode count that we can create at most in the left space,
we should consider space which data/node blocks occupied, since we create
data/node mixly in main area. So fix the wrong calculation in ->statfs.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: support multiple devices

2016-11-25T18:15:13+00:00

This patch implements multiple devices support for f2fs.
Given multiple devices by mkfs.f2fs, f2fs shows them entirely as one big
volume under one f2fs instance.

Internal block management is very simple, but we will modify block allocation
and background GC policy to boost IO speed by exploiting them accoording to
each device speed.

Signed-off-by: Jaegeuk Kim

f2fs: remove checkpoint in f2fs_freeze

2016-11-23T20:11:29+00:00

The generic freeze_super() calls sync_filesystems() before f2fs_freeze().
So, basically we don't need to do checkpoint in f2fs_freeze(). But, in xfs/068,
it triggers circular locking problem below due to gc_mutex for checkpoint.

======================================================
[ INFO: possible circular locking dependency detected ]
4.9.0-rc1+ #132 Tainted: G           OE
-------------------------------------------------------

1. wait for __sb_start_write() by

 [] dump_stack+0x85/0xc2
 [] print_circular_bug+0x1cf/0x230
 [] __lock_acquire+0x19e0/0x1bc0
 [] lock_acquire+0x11b/0x220
 [] ? f2fs_drop_inode+0x9b/0x160 [f2fs]
 [] __sb_start_write+0x130/0x200
 [] ? f2fs_drop_inode+0x9b/0x160 [f2fs]
 [] f2fs_drop_inode+0x9b/0x160 [f2fs]
 [] iput+0x171/0x2c0
 [] f2fs_sync_inode_meta+0x3f/0xf0 [f2fs]
 [] block_operations+0x84/0x110 [f2fs]
 [] write_checkpoint+0xe8/0xf20 [f2fs]
 [] ? trace_hardirqs_on+0xd/0x10
 [] ? f2fs_sync_fs+0x79/0x190 [f2fs]
 [] ? sched_clock+0x9/0x10
 [] ? f2fs_sync_fs+0x79/0x190 [f2fs]
 [] f2fs_sync_fs+0x85/0x190 [f2fs]
 [] ? do_fsync+0x70/0x70
 [] ? do_fsync+0x70/0x70
 [] sync_fs_one_sb+0x20/0x30
 [] iterate_supers+0xae/0x100
 [] sys_sync+0x55/0x90
 [] entry_SYSCALL_64_fastpath+0x23/0xc6

2. wait for sbi->gc_mutex by

 [] lock_acquire+0x11b/0x220
 [] mutex_lock_nested+0x76/0x3f0
 [] f2fs_sync_fs+0x79/0x190 [f2fs]
 [] f2fs_freeze+0x1c/0x20 [f2fs]
 [] freeze_super+0xcf/0x190
 [] do_vfs_ioctl+0x53c/0x6a0
 [] SyS_ioctl+0x79/0x90
 [] entry_SYSCALL_64_fastpath+0x23/0xc6

Signed-off-by: Jaegeuk Kim

f2fs: Cache zoned block devices zone type

2016-11-23T20:11:22+00:00

With the zoned block device feature enabled, section discard
need to do a zone reset for sections contained in sequential
zones, and a regular discard (if supported) for sections
stored in conventional zones. Avoid the need for a costly
report zones to obtain a section zone type when discarding it
by caching the types of the device zones in the super block
information. This cache is initialized at mount time for mounts
with the zoned block device feature enabled.

Signed-off-by: Damien Le Moal 
Signed-off-by: Jaegeuk Kim

f2fs: Do not allow adaptive mode for host-managed zoned block devices

2016-11-23T20:11:20+00:00

The LFS mode is mandatory for host-managed zoned block devices as
update in place optimizations are not possible for segments in
sequential zones.

Signed-off-by: Damien Le Moal 
Signed-off-by: Jaegeuk Kim