Linux block layer
 help / color / mirror / Atom feed
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.10-rc
Date: Fri, 20 Nov 2020 11:45:35 -0700	[thread overview]
Message-ID: <5e56dcf2-0320-c637-e6ee-143de81f2c41@kernel.dk> (raw)

Hi Linus,

Block fixes that should go into 5.10-rc5:

- NVMe pull request from Christoph:
	- Doorbell Buffer freeing fix (Minwoo Im)
	- CSE log leak fix (Keith Busch)

- blk-cgroup hd_struct leak fix (Christoph)

- Flush request state fix (Ming)

- dasd NULL deref fix (Stefan)

Please pull!


The following changes since commit c01a21b77722db0474bbcc4eafc8c4e0d8fed6d8:

  loop: Fix occasional uevent drop (2020-11-12 13:59:04 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/block-5.10-2020-11-20

for you to fetch changes up to 45f703a0d4b87f940ea150367dc4f4a9c06fa868:

  Merge tag 'nvme-5.10-2020-11-19' of git://git.infradead.org/nvme into block-5.10 (2020-11-19 09:23:27 -0700)

----------------------------------------------------------------
block-5.10-2020-11-20

----------------------------------------------------------------
Christoph Hellwig (1):
      blk-cgroup: fix a hd_struct leak in blkcg_fill_root_iostats

Jens Axboe (1):
      Merge tag 'nvme-5.10-2020-11-19' of git://git.infradead.org/nvme into block-5.10

Keith Busch (2):
      nvme: directly cache command effects log
      nvme: fix memory leak freeing command effects

Ming Lei (1):
      block: mark flush request as IDLE when it is really finished

Minwoo Im (1):
      nvme: free sq/cq dbbuf pointers when dbbuf set fails

Stefan Haberland (1):
      s390/dasd: fix null pointer dereference for ERP requests

 block/blk-cgroup.c        |  1 +
 block/blk-flush.c         |  7 ++++++-
 drivers/nvme/host/core.c  | 25 ++++++++++++++++++-------
 drivers/nvme/host/nvme.h  |  6 ------
 drivers/nvme/host/pci.c   | 15 +++++++++++++++
 drivers/s390/block/dasd.c |  6 ++++++
 6 files changed, 46 insertions(+), 14 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2020-11-20 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 18:45 Jens Axboe [this message]
2020-11-21  0:29 ` [GIT PULL] Block fixes for 5.10-rc pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-11-13 21:21 [GIT PULL] block " Jens Axboe
2020-11-14  0:15 ` pr-tracker-bot
2020-11-07 20:14 [GIT PULL] Block " Jens Axboe
2020-11-07 22:08 ` pr-tracker-bot
2020-10-30 17:09 Jens Axboe
2020-10-30 22:10 ` 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=5e56dcf2-0320-c637-e6ee-143de81f2c41@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