From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junichi Nomura <j-nomura@ce.jp.nec.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
dm-devel@redhat.com, Joe Thornber <ejt@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.1-rc6
Date: Fri, 29 May 2015 15:06:46 -0400 [thread overview]
Message-ID: <20150529190645.GA29347@redhat.com> (raw)
Hi Linus,
The following changes since commit ba155e2d21f6bf05de86a78dbe5bfd8757604a65:
Linux 4.1-rc5 (2015-05-24 18:22:35 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm tags/dm-4.1-fixes-3
for you to fetch changes up to 1c220c69ce0dcc0f234a9f263ad9c0864f971852:
dm: fix casting bug in dm_merge_bvec() (2015-05-29 13:41:16 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
Quite a few fixes for DM's blk-mq support thanks to extra DM multipath
testing from Junichi Nomura and Bart Van Assche.
Also fix a casting bug in dm_merge_bvec() that could cause only a single
page to be added to a bio (Joe identified this while testing dm-cache
writeback).
----------------------------------------------------------------
Joe Thornber (1):
dm: fix casting bug in dm_merge_bvec()
Junichi Nomura (3):
dm: run queue on re-queue
dm: fix NULL pointer when clone_and_map_rq returns !DM_MAPIO_REMAPPED
dm: fix reload failure of 0 path multipath mapping on blk-mq devices
Mike Snitzer (3):
dm mpath: fix leak of dm_mpath_io structure in blk-mq .queue_rq error path
dm: requeue from blk-mq dm_mq_queue_rq() using BLK_MQ_RQ_QUEUE_BUSY
dm: fix false warning in free_rq_clone() for unmapped requests
drivers/md/dm-mpath.c | 4 +++-
drivers/md/dm-table.c | 16 +++++++++-------
drivers/md/dm.c | 40 ++++++++++++++++++++++++----------------
3 files changed, 36 insertions(+), 24 deletions(-)
reply other threads:[~2015-05-29 19:06 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=20150529190645.GA29347@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=j-nomura@ce.jp.nec.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.