diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2014-09-24 19:53:33 +0400 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-09-24 19:53:33 +0400 |
| commit | a90e41e228b50f3975c5f1b9359f927fc0173a19 (patch) | |
| tree | de74f3e5930ea1e4d03f2b13f3613f1a9cf4c49e /drivers/md/persistent-data/dm-bitset.h | |
| parent | 452b6361c4d9baf6940adb7b1316e0f386c39799 (diff) | |
| parent | b8cb6b4c121e1bf1963c16ed69e7adcb1bc301cd (diff) | |
| download | linux-a90e41e228b50f3975c5f1b9359f927fc0173a19.tar.xz | |
Merge tag 'md/3.17-more-fixes' of git://git.neil.brown.name/md
Pull bugfixes for md/raid1 from Neil Brown:
"It is amazing how much easier it is to find bugs when you know one is
there. Two bug reports resulted in finding 7 bugs!
All are tagged for -stable. Those that can't cause (rare) data
corruption, cause lockups.
Particularly, but not only, fixing new "resync" code"
* tag 'md/3.17-more-fixes' of git://git.neil.brown.name/md:
md/raid1: fix_read_error should act on all non-faulty devices.
md/raid1: count resync requests in nr_pending.
md/raid1: update next_resync under resync_lock.
md/raid1: Don't use next_resync to determine how far resync has progressed
md/raid1: make sure resync waits for conflicting writes to complete.
md/raid1: clean up request counts properly in close_sync()
md/raid1: be more cautious where we read-balance during resync.
md/raid1: intialise start_next_window for READ case to avoid hang
Diffstat (limited to 'drivers/md/persistent-data/dm-bitset.h')
0 files changed, 0 insertions, 0 deletions