All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
	Joe Thornber <ejt@redhat.com>, Alasdair G Kergon <agk@redhat.com>,
	Dennis Yang <shinrairis@gmail.com>
Subject: [git pull] device mapper fixes for 4.2-rc3
Date: Fri, 17 Jul 2015 14:27:33 -0400	[thread overview]
Message-ID: <20150717182733.GA830@redhat.com> (raw)

Hi Linus,

The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:

  Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm tags/dm-4.2-fixes-2

for you to fetch changes up to 665022d72f9b5762f21b5ea02fa0503d04802849:

  dm cache: avoid calls to prealloc_free_structs() if possible (2015-07-16 22:32:08 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Revert a request-based DM core change that caused IO latency to
  increase and adversely impact both throughput and system load

- Fix for a use after free bug in DM core's device cleanup

- A couple DM btree removal fixes (used by dm-thinp)

- A DM thinp fix for order-5 allocation failure

- A DM thinp fix to not degrade to read-only metadata mode when in
  out-of-data-space mode for longer than the 'no_space_timeout'

- Fix a long-standing oversight in both dm-thinp and dm-cache by
  now exporting 'needs_check' in status if it was set in metadata

- Fix an embarrassing dm-cache busy-loop that caused worker threads to
  eat cpu even if no IO was actively being issued to the cache device

----------------------------------------------------------------
Dennis Yang (1):
      dm btree remove: fix bug in redistribute3

Joe Thornber (2):
      dm thin: allocate the cell_sort_array dynamically
      dm btree: silence lockdep lock inversion in dm_btree_del()

Mike Snitzer (7):
      Revert "dm: only run the queue on completion if congested or no requests pending"
      dm thin: stay in out-of-data-space mode once no_space_timeout expires
      dm thin: display 'needs_check' in status if it is set
      dm cache: display 'needs_check' in status if it is set
      dm cache: do not wake_worker() in free_migration()
      dm cache: avoid preallocation if no work in writeback_some_dirty_blocks()
      dm cache: avoid calls to prealloc_free_structs() if possible

Mikulas Patocka (1):
      dm: fix use after free crash due to incorrect cleanup sequence

 Documentation/device-mapper/cache.txt             |  6 ++++
 Documentation/device-mapper/thin-provisioning.txt |  9 ++++-
 drivers/md/dm-cache-target.c                      | 38 ++++++++++++--------
 drivers/md/dm-thin.c                              | 44 +++++++++++++++++++----
 drivers/md/dm.c                                   | 12 +++----
 drivers/md/persistent-data/dm-btree-remove.c      |  6 ++--
 drivers/md/persistent-data/dm-btree.c             |  2 +-
 7 files changed, 82 insertions(+), 35 deletions(-)

                 reply	other threads:[~2015-07-17 18:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150717182733.GA830@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=shinrairis@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.