From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Biggers <ebiggers@google.com>,
Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
Vladimir Zapolskiy <vz@mleia.com>,
dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.8-rc5
Date: Fri, 2 Sep 2016 13:57:49 -0400 [thread overview]
Message-ID: <20160902175748.GA75303@redhat.com> (raw)
Hi Linus,
The following changes since commit 3eab887a55424fc2c27553b7bfe32330df83f7b8:
Linux 4.8-rc4 (2016-08-28 15:04:33 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm tags/dm-4.8-fixes-4
for you to fetch changes up to edd1ea2a8a2549e4fe58e817d539445729491ecf:
dm bufio: remove use of deprecated create_singlethread_workqueue() (2016-08-30 19:45:20 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- a stable fix in both DM crypt and DM log-writes for too large bios (as
generated by bcache)
- 2 other stable fixes for DM log-writes
- a stable fix for a DM crypt bug that could result in freeing pointers
from uninitialized memory in the tfm allocation error path
- a DM bufio cleanup to discontinue using create_singlethread_workqueue()
----------------------------------------------------------------
Bhaktipriya Shridhar (1):
dm bufio: remove use of deprecated create_singlethread_workqueue()
Eric Biggers (1):
dm crypt: fix free of bad values after tfm allocation failure
Mikulas Patocka (3):
dm log writes: move IO accounting earlier to fix error path
dm log writes: fix bug with too large bios
dm crypt: fix error with too large bios
Vladimir Zapolskiy (1):
dm log writes: fix check of kthread_run() return value
drivers/md/dm-bufio.c | 2 +-
drivers/md/dm-crypt.c | 9 ++++++++-
drivers/md/dm-log-writes.c | 10 +++++-----
3 files changed, 14 insertions(+), 7 deletions(-)
reply other threads:[~2016-09-02 17:57 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=20160902175748.GA75303@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bhaktipriya96@gmail.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=mpatocka@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vz@mleia.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 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.