From: Song Liu <songliubraving@fb.com>
To: Jens Axboe <axboe@kernel.dk>, linux-raid <linux-raid@vger.kernel.org>
Cc: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>,
Zhao Heming <heming.zhao@suse.com>,
Jason Yan <yanaijie@huawei.com>
Subject: [GIT PULL] md-next 20201008
Date: Fri, 9 Oct 2020 05:49:49 +0000 [thread overview]
Message-ID: <0AE63FFF-6DBF-4AD1-B93E-F5466E1AF5D9@fb.com> (raw)
Hi Jens,
Please consider pulling the following changes on top of your for-5.10/drivers
branch.
The main changes are:
1. Bug fixes in bitmap code, from Zhao Heming.
2. Fix a work queue check, from Guoqing Jiang.
3. Fix raid5 oops with reshape, from Song Liu.
4. Clean up unused code, from Jason Yan.
Thanks,
Song
The following changes since commit b6bf0830a808498146903e0e1f407a1eba95019a:
Merge tag 'nvme-5.10-2020-10-08' of git://git.infradead.org/nvme into for-5.10/drivers (2020-10-08 09:07:09 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-next
for you to fetch changes up to b44c018cdf748b96b676ba09fdbc5b34fc443ada:
md/raid5: fix oops during stripe resizing (2020-10-08 22:38:10 -0700)
----------------------------------------------------------------
Guoqing Jiang (1):
md: fix the checking of wrong work queue
Jason Yan (1):
md/raid0: remove unused function is_io_in_chunk_boundary()
Song Liu (1):
md/raid5: fix oops during stripe resizing
Zhao Heming (3):
md/bitmap: md_bitmap_read_sb uses wrong bitmap blocks
md/bitmap: md_bitmap_get_counter returns wrong blocks
md/bitmap: fix memory leak of temporary bitmap
drivers/md/md-bitmap.c | 9 +++++----
drivers/md/md-cluster.c | 1 +
drivers/md/md.c | 2 +-
drivers/md/raid0.c | 17 -----------------
drivers/md/raid5.c | 4 ++--
5 files changed, 9 insertions(+), 24 deletions(-)
next reply other threads:[~2020-10-09 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 5:49 Song Liu [this message]
2020-10-09 15:04 ` [GIT PULL] md-next 20201008 Jens Axboe
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=0AE63FFF-6DBF-4AD1-B93E-F5466E1AF5D9@fb.com \
--to=songliubraving@fb.com \
--cc=axboe@kernel.dk \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=heming.zhao@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=yanaijie@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).