From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, NeilBrown <neilb@suse.com>,
Milan Broz <gmazyland@gmail.com>
Subject: [git pull] device mapper fix for 4.16-rc2
Date: Fri, 16 Feb 2018 11:03:32 -0500 [thread overview]
Message-ID: <20180216160331.GA8182@redhat.com> (raw)
Hi Linus,
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-4.16/dm-chained-bios-fix
for you to fetch changes up to 8dd601fa8317243be887458c49f6c29c2f3d719f:
dm: correctly handle chained bios in dec_pending() (2018-02-16 10:46:35 -0500)
Please pull, thanks!
Mike
----------------------------------------------------------------
- Fix for DM core to properly propagate errors (avoids overriding
non-zero error with 0). This is particularly important given DM
core's increased use of chained bios.
----------------------------------------------------------------
NeilBrown (1):
dm: correctly handle chained bios in dec_pending()
drivers/md/dm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
reply other threads:[~2018-02-16 16:03 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=20180216160331.GA8182@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=neilb@suse.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