From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jerome Marchand <jmarchan@redhat.com>,
zhangyi <yi.zhang@huawei.com>, Stephen Boyd <swboyd@chromium.org>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Gen Zhang <blackgod016574@gmail.com>,
Milan Broz <gmazyland@gmail.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 5.2 final
Date: Thu, 27 Jun 2019 14:19:06 -0400 [thread overview]
Message-ID: <20190627181904.GA10850@redhat.com> (raw)
Hi Linus,
The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.2/dm-fixes-2
for you to fetch changes up to 2eba4e640b2c4161e31ae20090a53ee02a518657:
dm verity: use message limit for data block corruption message (2019-06-25 14:09:14 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix incorrect uses of kstrndup and DM logging macros in DM's early
init code.
- Fix DM log-writes target's handling of super block sectors so updates
are made in order through use of completion.
- Fix DM core's argument splitting code to avoid undefined behaviour
reported as a side-effect of UBSAN analysis on ppc64le.
- Fix DM verity target to limit the amount of error messages that can
result from a corrupt block being found.
----------------------------------------------------------------
Gen Zhang (1):
dm init: fix incorrect uses of kstrndup()
Jerome Marchand (1):
dm table: don't copy from a NULL pointer in realloc_argv()
Milan Broz (1):
dm verity: use message limit for data block corruption message
Stephen Boyd (1):
dm init: remove trailing newline from calls to DMERR() and DMINFO()
zhangyi (F) (1):
dm log writes: make sure super sector log updates are written in order
drivers/md/dm-init.c | 10 +++++-----
drivers/md/dm-log-writes.c | 23 +++++++++++++++++++++--
drivers/md/dm-table.c | 2 +-
drivers/md/dm-verity-target.c | 4 ++--
4 files changed, 29 insertions(+), 10 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
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>,
Gen Zhang <blackgod016574@gmail.com>,
Jerome Marchand <jmarchan@redhat.com>,
Milan Broz <gmazyland@gmail.com>,
Stephen Boyd <swboyd@chromium.org>, zhangyi <yi.zhang@huawei.com>
Subject: [git pull] device mapper fixes for 5.2 final
Date: Thu, 27 Jun 2019 14:19:06 -0400 [thread overview]
Message-ID: <20190627181904.GA10850@redhat.com> (raw)
Hi Linus,
The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.2/dm-fixes-2
for you to fetch changes up to 2eba4e640b2c4161e31ae20090a53ee02a518657:
dm verity: use message limit for data block corruption message (2019-06-25 14:09:14 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix incorrect uses of kstrndup and DM logging macros in DM's early
init code.
- Fix DM log-writes target's handling of super block sectors so updates
are made in order through use of completion.
- Fix DM core's argument splitting code to avoid undefined behaviour
reported as a side-effect of UBSAN analysis on ppc64le.
- Fix DM verity target to limit the amount of error messages that can
result from a corrupt block being found.
----------------------------------------------------------------
Gen Zhang (1):
dm init: fix incorrect uses of kstrndup()
Jerome Marchand (1):
dm table: don't copy from a NULL pointer in realloc_argv()
Milan Broz (1):
dm verity: use message limit for data block corruption message
Stephen Boyd (1):
dm init: remove trailing newline from calls to DMERR() and DMINFO()
zhangyi (F) (1):
dm log writes: make sure super sector log updates are written in order
drivers/md/dm-init.c | 10 +++++-----
drivers/md/dm-log-writes.c | 23 +++++++++++++++++++++--
drivers/md/dm-table.c | 2 +-
drivers/md/dm-verity-target.c | 4 ++--
4 files changed, 29 insertions(+), 10 deletions(-)
next reply other threads:[~2019-06-27 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 18:19 Mike Snitzer [this message]
2019-06-27 18:19 ` [git pull] device mapper fixes for 5.2 final Mike Snitzer
2019-06-28 0:55 ` pr-tracker-bot
2019-06-28 0:55 ` 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=20190627181904.GA10850@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=blackgod016574@gmail.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=jmarchan@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=swboyd@chromium.org \
--cc=torvalds@linux-foundation.org \
--cc=yi.zhang@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 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.