From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 5.8-rc1
Date: Thu, 11 Jun 2020 15:31:26 -0600 [thread overview]
Message-ID: <fc27bd22-3954-5733-c503-bd45d51754e0@kernel.dk> (raw)
Hi Linus,
Some followup fixes for this merge window. In particular:
- Seqcount write missing preemption disable for stats (Ahmed)
- blktrace fixes (Chaitanya)
- Redundant initializations (Colin)
- Various small NVMe fixes (Chaitanya, Christoph, Daniel, Max, Niklas,
Rikard)
- loop flag bug regression fix (Martijn)
- blk-mq tagging fixes (Christoph, Ming)
Please pull!
The following changes since commit 1ee08de1e234d95b5b4f866878b72fceb5372904:
Merge tag 'for-5.8/io_uring-2020-06-01' of git://git.kernel.dk/linux-block (2020-06-02 15:42:50 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/block-5.8-2020-06-11
for you to fetch changes up to 9a6a5738abf82d6f467a31f1f6779e495462f7af:
umem: remove redundant initialization of variable ret (2020-06-11 09:16:17 -0600)
----------------------------------------------------------------
block-5.8-2020-06-11
----------------------------------------------------------------
Ahmed S. Darwish (1):
block: nr_sects_write(): Disable preemption on seqcount write
Chaitanya Kulkarni (4):
blktrace: use errno instead of bi_status
blktrace: fix endianness in get_pdu_int()
blktrace: fix endianness for blk_log_remap()
nvmet: fail outstanding host posted AEN req
Christoph Hellwig (3):
block: remove the error argument to the block_bio_complete tracepoint
blk-mq: split out a __blk_mq_get_driver_tag helper
nvme-pci: use simple suspend when a HMB is enabled
Colin Ian King (2):
pktcdvd: remove redundant initialization of variable ret
umem: remove redundant initialization of variable ret
Daniel Wagner (1):
nvme-fc: don't call nvme_cleanup_cmd() for AENs
Martijn Coenen (1):
loop: Fix wrong masking of status flags
Max Gurtovoy (1):
nvmet-tcp: constify nvmet_tcp_ops
Ming Lei (1):
blk-mq: fix blk_mq_all_tag_iter
Niklas Cassel (1):
nvme: do not call del_gendisk() on a disk that was never added
Rikard Falkeborn (1):
nvme-tcp: constify nvme_tcp_mq_ops and nvme_tcp_admin_mq_ops
yu kuai (1):
block/bio-integrity: don't free 'buf' if bio_integrity_add_page() failed
block/bio-integrity.c | 1 -
block/bio.c | 3 +--
block/blk-mq-tag.c | 39 ++++++++++++++++++++++++++++++++++++---
block/blk-mq-tag.h | 8 ++++++++
block/blk-mq.c | 29 -----------------------------
block/blk-mq.h | 1 -
block/blk.h | 2 ++
drivers/block/loop.c | 2 +-
drivers/block/pktcdvd.c | 2 +-
drivers/block/umem.c | 2 +-
drivers/nvme/host/core.c | 4 +---
drivers/nvme/host/fc.c | 5 +++--
drivers/nvme/host/nvme.h | 3 +--
drivers/nvme/host/pci.c | 6 ++++++
drivers/nvme/host/tcp.c | 8 ++++----
drivers/nvme/target/core.c | 27 ++++++++++++++++++++-------
drivers/nvme/target/tcp.c | 4 ++--
include/trace/events/block.h | 6 +++---
kernel/trace/blktrace.c | 36 ++++++++++++++----------------------
19 files changed, 104 insertions(+), 84 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-06-11 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 21:31 Jens Axboe [this message]
2020-06-11 23:45 ` [GIT PULL] Block fixes for 5.8-rc1 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=fc27bd22-3954-5733-c503-bd45d51754e0@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--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