From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Nikos Tsironis <ntsironis@arrikto.com>,
YueHaibing <yuehaibing@huawei.com>
Subject: [git pull] device mapper fixes for 5.4-rc4
Date: Fri, 18 Oct 2019 12:08:33 -0400 [thread overview]
Message-ID: <20191018160833.GA5763@redhat.com> (raw)
Hi Linus,
The following changes since commit da0c9ea146cbe92b832f1b0f694840ea8eb33cce:
Linux 5.4-rc2 (2019-10-06 14:27:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.4/dm-fixes
for you to fetch changes up to 13bd677a472d534bf100bab2713efc3f9e3f5978:
dm cache: fix bugs when a GFP_NOWAIT allocation fails (2019-10-17 11:13:50 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix DM snapshot deadlock that can occur due to COW throttling
preventing locks from being released.
- Fix DM cache's GFP_NOWAIT allocation failure error paths by switching
to GFP_NOIO.
- Make __hash_find() static in the DM clone target.
----------------------------------------------------------------
Mikulas Patocka (3):
dm snapshot: introduce account_start_copy() and account_end_copy()
dm snapshot: rework COW throttling to fix deadlock
dm cache: fix bugs when a GFP_NOWAIT allocation fails
YueHaibing (1):
dm clone: Make __hash_find static
drivers/md/dm-cache-target.c | 28 +------------
drivers/md/dm-clone-target.c | 4 +-
drivers/md/dm-snap.c | 94 ++++++++++++++++++++++++++++++++++++--------
3 files changed, 81 insertions(+), 45 deletions(-)
next reply other threads:[~2019-10-18 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 16:08 Mike Snitzer [this message]
2019-10-18 22:50 ` [git pull] device mapper fixes for 5.4-rc4 pr-tracker-bot
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=20191018160833.GA5763@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=ntsironis@arrikto.com \
--cc=torvalds@linux-foundation.org \
--cc=yuehaibing@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).