From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bart Van Assche <bart.vanassche@wdc.com>,
dm-devel@redhat.com, Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.13 final
Date: Thu, 31 Aug 2017 16:52:08 -0400 [thread overview]
Message-ID: <20170831205207.GA12284@redhat.com> (raw)
Hi Linus,
I've been away for a few weeks recovering from injury so that is why
these 4.13 fixes are so late.
The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98:
Linux 4.13-rc7 (2017-08-27 17:20:40 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-4.13/dm-fixes-2
for you to fetch changes up to 1c23484c355ec360ca2f37914f8a4802c6baeead:
dm mpath: do not lock up a CPU with requeuing activity (2017-08-28 09:58:27 -0400)
Please pull, thanks!
Mike
----------------------------------------------------------------
- A couple fixes for bugs introduced as part of the blk_status_t block
layer changes during the 4.13 merge window
- A printk throttling fix to use discrete rate limiting state for each
DM log level
- A stable@ fix for DM multipath that delays request requeueing to avoid
CPU lockup if/when the request queue is "dying"
----------------------------------------------------------------
Bart Van Assche (4):
dm: fix the second dec_pending() argument in __split_and_process_bio()
dm mpath: retry BLK_STS_RESOURCE errors
dm: fix printk() rate limiting code
dm mpath: do not lock up a CPU with requeuing activity
drivers/md/dm-mpath.c | 2 --
drivers/md/dm.c | 12 +-----------
include/linux/device-mapper.h | 41 ++++++++++++-----------------------------
3 files changed, 13 insertions(+), 42 deletions(-)
reply other threads:[~2017-08-31 20:52 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=20170831205207.GA12284@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bart.vanassche@wdc.com \
--cc=dm-devel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox