linux-toradex.git/fs, branch v4.5-rc2

Merge branch 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

2016-01-31T23:49:06+00:00

Pull timer fixes from Thomas Gleixner:
 "The timer departement delivers:

   - a regression fix for the NTP code along with a proper selftest
   - prevent a spurious timer interrupt in the NOHZ lowres code
   - a fix for user space interfaces returning the remaining time on
     architectures with CONFIG_TIME_LOW_RES=y
   - a few patches to fix COMPILE_TEST fallout"

* 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  tick/nohz: Set the correct expiry when switching to nohz/lowres mode
  clocksource: Fix dependencies for archs w/o HAS_IOMEM
  clocksource: Select CLKSRC_MMIO where needed
  tick/sched: Hide unused oneshot timer code
  kselftests: timers: Add adjtimex SETOFFSET validity tests
  ntp: Fix ADJ_SETOFFSET being used w/ ADJ_NANO
  itimers: Handle relative timers with CONFIG_TIME_LOW_RES proper
  posix-timers: Handle relative timers with CONFIG_TIME_LOW_RES proper
  timerfd: Handle relative timers with CONFIG_TIME_LOW_RES proper
  hrtimer: Handle remaining time proper for TIME_LOW_RES
  clockevents/tcb_clksrc: Prevent disabling an already disabled clock

Merge branch 'for-linus-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs

2016-01-29T23:46:49+00:00

Pull btrfs fixes from Chris Mason:
 "Dave had a small collection of fixes to the new free space tree code,
  one of which was keeping our sysfs files more up to date with feature
  bits as different things get enabled (lzo, raid5/6, etc).

  I should have kept the sysfs stuff for rc3, since we always manage to
  trip over something.  This time it was GFP_KERNEL from somewhere that
  is NOFS only.  Instead of rebasing it out I've put a revert in, and
  we'll fix it properly for rc3.

  Otherwise, Filipe fixed a btrfs DIO race and Qu Wenruo fixed up a
  use-after-free in our tracepoints that Dave Jones reported"

* 'for-linus-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs:
  Revert "btrfs: synchronize incompat feature bits with sysfs files"
  btrfs: don't use GFP_HIGHMEM for free-space-tree bitmap kzalloc
  btrfs: sysfs: check initialization state before updating features
  Revert "btrfs: clear PF_NOFREEZE in cleaner_kthread()"
  btrfs: async-thread: Fix a use-after-free error for trace
  Btrfs: fix race between fsync and lockless direct IO writes
  btrfs: add free space tree to the cow-only list
  btrfs: add free space tree to lockdep classes
  btrfs: tweak free space tree bitmap allocation
  btrfs: tests: switch to GFP_KERNEL
  btrfs: synchronize incompat feature bits with sysfs files
  btrfs: sysfs: introduce helper for syncing bits with sysfs files
  btrfs: sysfs: add free-space-tree bit attribute
  btrfs: sysfs: fix typo in compat_ro attribute definition

Revert "btrfs: synchronize incompat feature bits with sysfs files"

2016-01-29T16:19:37+00:00

This reverts commit 14e46e04958df740c6c6a94849f176159a333f13.

This ends up doing sysfs operations from deep in balance (where we
should be GFP_NOFS) and under heavy balance load, we're making races
against sysfs internals.

Revert it for now while we figure things out.

Signed-off-by: Chris Mason

btrfs: don't use GFP_HIGHMEM for free-space-tree bitmap kzalloc

2016-01-27T15:05:49+00:00

This was copied incorrectly from the __vmalloc call.

Signed-off-by: Chris Mason

Merge branch 'dev/fst-followup' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.5

2016-01-27T13:48:23+00:00

btrfs: sysfs: check initialization state before updating features

2016-01-27T13:40:10+00:00

If the mount phase is not finished, we can't update the sysfs files.

Reported-by: Chris Mason 
Signed-off-by: David Sterba 
Signed-off-by: Chris Mason

Revert "btrfs: clear PF_NOFREEZE in cleaner_kthread()"

2016-01-26T00:50:27+00:00

This reverts commit 696249132158014d594896df3a81390616069c5c. The
cleaner thread can block freezing when there's a snapshot cleaning in
progress and the other threads get suspended first. From the logs
provided by Martin we're waiting for reading extent pages:

kernel: PM: Syncing filesystems ... done.
kernel: Freezing user space processes ... (elapsed 0.015 seconds) done.
kernel: Freezing remaining freezable tasks ...
kernel: Freezing of tasks failed after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
kernel: btrfs-cleaner   D ffff88033dd13bc0     0   152      2 0x00000000
kernel: ffff88032ebc2e00 ffff88032e750000 ffff88032e74fa50 7fffffffffffffff
kernel: ffffffff814a58df 0000000000000002 ffffea000934d580 ffffffff814a5451
kernel: 7fffffffffffffff ffffffff814a6e8f 0000000000000000 0000000000000020
kernel: Call Trace:
kernel: [] ? bit_wait+0x2c/0x2c
kernel: [] ? schedule+0x6f/0x7c
kernel: [] ? schedule_timeout+0x2f/0xd8
kernel: [] ? timekeeping_get_ns+0xa/0x2e
kernel: [] ? ktime_get+0x36/0x44
kernel: [] ? io_schedule_timeout+0x94/0xf2
kernel: [] ? io_schedule_timeout+0x94/0xf2
kernel: [] ? bit_wait_io+0x2c/0x30
kernel: [] ? __wait_on_bit+0x41/0x73
kernel: [] ? wait_on_page_bit+0x6d/0x72
kernel: [] ? autoremove_wake_function+0x2a/0x2a
kernel: [] ? read_extent_buffer_pages+0x1bd/0x203
kernel: [] ? free_root_pointers+0x4c/0x4c
kernel: [] ? btree_read_extent_buffer_pages.constprop.57+0x5a/0xe9
kernel: [] ? read_tree_block+0x2d/0x45
kernel: [] ? read_block_for_search.isra.34+0x22a/0x26b
kernel: [] ? btrfs_set_path_blocking+0x1e/0x4a
kernel: [] ? btrfs_search_slot+0x648/0x736
kernel: [] ? btrfs_lookup_extent_info+0xb7/0x2c7
kernel: [] ? walk_down_proc+0x9c/0x1ae
kernel: [] ? walk_down_tree+0x40/0xa4
kernel: [] ? btrfs_drop_snapshot+0x2da/0x664
kernel: [] ? finish_task_switch+0x126/0x167
kernel: [] ? btrfs_clean_one_deleted_snapshot+0xa6/0xb0
kernel: [] ? cleaner_kthread+0x13e/0x17b
kernel: [] ? btrfs_item_end+0x33/0x33
kernel: [] ? kthread+0x95/0x9d
kernel: [] ? kthread_parkme+0x16/0x16
kernel: [] ? ret_from_fork+0x3f/0x70
kernel: [] ? kthread_parkme+0x16/0x16

As this affects a released kernel (4.4) we need a minimal fix for
stable kernels.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=108361
Reported-by: Martin Ziegler 
CC: stable@vger.kernel.org # 4.4
CC: Jiri Kosina 
Signed-off-by: David Sterba 
Signed-off-by: Chris Mason

btrfs: async-thread: Fix a use-after-free error for trace

2016-01-26T00:50:26+00:00

Parameter of trace_btrfs_work_queued() can be freed in its workqueue.
So no one use use that pointer after queue_work().

Fix the user-after-free bug by move the trace line before queue_work().

Reported-by: Dave Jones 
Signed-off-by: Qu Wenruo 
Reviewed-by: David Sterba 
Signed-off-by: Chris Mason

Btrfs: fix race between fsync and lockless direct IO writes

2016-01-26T00:50:26+00:00

An fsync, using the fast path, can race with a concurrent lockless direct
IO write and end up logging a file extent item that points to an extent
that wasn't written to yet. This is because the fast fsync path collects
ordered extents into a local list and then collects all the new extent
maps to log file extent items based on them, while the direct IO write
path creates the new extent map before it creates the corresponding
ordered extent (and submitting the respective bio(s)).

So fix this by making the direct IO write path create ordered extents
before the extent maps and make the fast fsync path collect any new
ordered extents after it collects the extent maps.
Note that making the fsync handler call inode_dio_wait() (after acquiring
the inode's i_mutex) would not work and lead to a deadlock when doing
AIO, as through AIO we end up in a path where the fsync handler is called
(through dio_aio_complete_work() -> dio_complete() -> vfs_fsync_range())
before the inode's dio counter is decremented (inode_dio_wait() waits
for this counter to have a value of zero).

Signed-off-by: Filipe Manana 
Signed-off-by: Chris Mason

Merge branch 'fix/fst-sysfs' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.5

2016-01-26T00:43:13+00:00

Signed-off-by: Chris Mason