linux-toradex.git/drivers/md/md-cluster.c, branch v5.3.2

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 45

2019-05-24T15:27:12+00:00

Based on 1 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license as published by
  the free software foundation either version 2 or at your option any
  later version

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-or-later

has been chosen to replace the boilerplate/reference in 11 file(s).

Signed-off-by: Thomas Gleixner 
Reviewed-by: Kate Stewart 
Reviewed-by: Allison Randal 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190520170858.370933192@linutronix.de
Signed-off-by: Greg Kroah-Hartman

md-cluster: remove suspend_info

2018-10-18T16:41:25+00:00

Previously, we allow multiple nodes can resync device, but we
had changed it to only support one node can do resync at one
time, but suspend_info is still used.

Now, let's remove the structure and use suspend_lo/hi to record
the range.

Reviewed-by: NeilBrown 
Signed-off-by: Guoqing Jiang 
Signed-off-by: Shaohua Li

md-cluster: send BITMAP_NEEDS_SYNC message if reshaping is interrupted

2018-10-18T16:40:48+00:00

We need to continue the reshaping if it was interrupted in
original node. So original node should call resync_bitmap
in case reshaping is aborted.

Then BITMAP_NEEDS_SYNC message is broadcasted to other nodes,
node which continues the reshaping should restart reshape from
mddev->reshape_position instead of from the first beginning.

Reviewed-by: NeilBrown 
Signed-off-by: Guoqing Jiang 
Signed-off-by: Shaohua Li

md-cluster/bitmap: don't call md_bitmap_sync_with_cluster during reshaping stage

2018-10-18T16:40:01+00:00

When reshape is happening in one node, other nodes could receive
lots of RESYNCING messages, so md_bitmap_sync_with_cluster is called.

Since the resyncing window is typically small in these RESYNCING
messages, so WARN is always triggered, so we should not call the
func when reshape is happening.

Reviewed-by: NeilBrown 
Signed-off-by: Guoqing Jiang 
Signed-off-by: Shaohua Li

md-cluster: introduce resync_info_get interface for sanity check

2018-10-18T16:36:35+00:00

Since the resync region from suspend_info means one node
is reshaping this area, so the position of reshape_progress
should be included in the area.

Reviewed-by: NeilBrown 
Signed-off-by: Guoqing Jiang 
Signed-off-by: Shaohua Li

md-cluster/raid10: resize all the bitmaps before start reshape

2018-10-18T16:30:58+00:00

To support add disk under grow mode, we need to resize
all the bitmaps of each node before reshape, so that we
can ensure all nodes have the same view of the bitmap of
the clustered raid.

So after the master node resized the bitmap, it broadcast
a message to other slave nodes, and it checks the size of
each bitmap are same or not by compare pages. We can only
continue the reshaping after all nodes update the bitmap
to the same size (by checking the pages), otherwise revert
bitmap size to previous value.

The resize_bitmaps interface and BITMAP_RESIZE message are
introduced in md-cluster.c for the purpose.

Reviewed-by: NeilBrown 
Signed-off-by: Guoqing Jiang 
Signed-off-by: Shaohua Li

md-cluster: release RESYNC lock after the last resync message

2018-09-01T00:38:10+00:00

All the RESYNC messages are sent with resync lock held, the only
exception is resync_finish which releases resync_lockres before
send the last resync message, this should be changed as well.
Otherwise, we can see deadlock issue as follows:

clustermd2-gqjiang2:~ # cat /proc/mdstat
Personalities : [raid10] [raid1]
md0 : active raid1 sdg[0] sdf[1]
      134144 blocks super 1.2 [2/2] [UU]
      [===================>.]  resync = 99.6% (134144/134144) finish=0.0min speed=26K/sec
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: 
clustermd2-gqjiang2:~ # ps aux|grep md|grep D
root     20497  0.0  0.0      0     0 ?        D    16:00   0:00 [md0_raid1]
clustermd2-gqjiang2:~ # cat /proc/20497/stack
[] dlm_lock_sync+0x8e/0xc0 [md_cluster]
[] __sendmsg+0x98/0x130 [md_cluster]
[] sendmsg+0x20/0x30 [md_cluster]
[] resync_info_update+0xb5/0xc0 [md_cluster]
[] md_reap_sync_thread+0x134/0x170 [md_mod]
[] md_check_recovery+0x28c/0x510 [md_mod]
[] raid1d+0x42/0x800 [raid1]
[] md_thread+0x121/0x150 [md_mod]
[] kthread+0xff/0x140
[] ret_from_fork+0x35/0x40
[] 0xffffffffffffffff

clustermd-gqjiang1:~ # ps aux|grep md|grep D
root     20531  0.0  0.0      0     0 ?        D    16:00   0:00 [md0_raid1]
root     20537  0.0  0.0      0     0 ?        D    16:00   0:00 [md0_cluster_rec]
root     20676  0.0  0.0      0     0 ?        D    16:01   0:00 [md0_resync]
clustermd-gqjiang1:~ # cat /proc/mdstat
Personalities : [raid10] [raid1]
md0 : active raid1 sdf[1] sdg[0]
      134144 blocks super 1.2 [2/2] [UU]
      [===================>.]  resync = 97.3% (131072/134144) finish=8076.8min speed=0K/sec
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: 
clustermd-gqjiang1:~ # cat /proc/20531/stack
[] metadata_update_start+0xcd/0xd0 [md_cluster]
[] md_update_sb.part.61+0x97/0x820 [md_mod]
[] md_check_recovery+0x29b/0x510 [md_mod]
[] raid1d+0x42/0x800 [raid1]
[] md_thread+0x121/0x150 [md_mod]
[] kthread+0xff/0x140
[] ret_from_fork+0x35/0x40
[] 0xffffffffffffffff
clustermd-gqjiang1:~ # cat /proc/20537/stack
[] freeze_array+0xf2/0x140 [raid1]
[] recv_daemon+0x41e/0x580 [md_cluster]
[] md_thread+0x121/0x150 [md_mod]
[] kthread+0xff/0x140
[] ret_from_fork+0x35/0x40
[] 0xffffffffffffffff
clustermd-gqjiang1:~ # cat /proc/20676/stack
[] dlm_lock_sync+0x8e/0xc0 [md_cluster]
[] lock_token+0x2f/0xa0 [md_cluster]
[] lock_comm+0x32/0x90 [md_cluster]
[] sendmsg+0x15/0x30 [md_cluster]
[] resync_info_update+0x8a/0xc0 [md_cluster]
[] raid1_sync_request+0xa9a/0xb10 [raid1]
[] md_do_sync+0xbaa/0xf90 [md_mod]
[] md_thread+0x121/0x150 [md_mod]
[] kthread+0xff/0x140
[] ret_from_fork+0x35/0x40
[] 0xffffffffffffffff

Reviewed-by: NeilBrown 
Signed-off-by: Guoqing Jiang 
Signed-off-by: Shaohua Li

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

2018-08-18T23:48:07+00:00

Pull input updates from Dmitry Torokhov:

 - a new driver for Rohm BU21029 touch controller

 - new bitmap APIs: bitmap_alloc, bitmap_zalloc and bitmap_free

 - updates to Atmel, eeti. pxrc and iforce drivers

 - assorted driver cleanups and fixes.

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input: (57 commits)
  MAINTAINERS: Add PhoenixRC Flight Controller Adapter
  Input: do not use WARN() in input_alloc_absinfo()
  Input: mark expected switch fall-throughs
  Input: raydium_i2c_ts - use true and false for boolean values
  Input: evdev - switch to bitmap API
  Input: gpio-keys - switch to bitmap_zalloc()
  Input: elan_i2c_smbus - cast sizeof to int for comparison
  bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  md: Avoid namespace collision with bitmap API
  dm: Avoid namespace collision with bitmap API
  Input: pm8941-pwrkey - add resin entry
  Input: pm8941-pwrkey - abstract register offsets and event code
  Input: iforce - reorganize joystick configuration lists
  Input: atmel_mxt_ts - move completion to after config crc is updated
  Input: atmel_mxt_ts - don't report zero pressure from T9
  Input: atmel_mxt_ts - zero terminate config firmware file
  Input: atmel_mxt_ts - refactor config update code to add context struct
  Input: atmel_mxt_ts - config CRC may start at T71
  Input: atmel_mxt_ts - remove unnecessary debug on ENOMEM
  Input: atmel_mxt_ts - remove duplicate setup of ABS_MT_PRESSURE
  ...

md: Avoid namespace collision with bitmap API

2018-08-01T22:49:39+00:00

bitmap API (include/linux/bitmap.h) has 'bitmap' prefix for its methods.

On the other hand MD bitmap API is special case.
Adding 'md' prefix to it to avoid name space collision.

No functional changes intended.

Signed-off-by: Andy Shevchenko 
Acked-by: Shaohua Li 
Signed-off-by: Dmitry Torokhov

md-cluster: don't send msg if array is closing

2018-07-05T18:17:02+00:00

If we close an array which resync thread is running,
then we don't need the node to send msg since another
node would launch the resync thread to continue the
rest works. Also send a message is time consuming,
we should avoid it.

Signed-off-by: Guoqing Jiang 
Reviewed-by: NeilBrown 
Signed-off-by: Shaohua Li