public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: "[email protected]" <[email protected]>,
	[email protected]
Subject: [GIT PULL] Fixes for 5.4-rc8/final
Date: Fri, 15 Nov 2019 12:40:46 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

We have a few fixes that should make it into this release. This pull
request contains:

- io_uring:
	- The timeout command assumes sequence == 0 means that we want
	  one completion, but this kind of overloading is unfortunate as
	  it prevents users from doing a pure time based wait. Since
	  this operation was introduced in this cycle, let's correct it
	  now, while we can. (me)
	- One-liner to fix an issue with dependent links and fixed
	  buffer reads. The actual IO completed fine, but the link got
	  severed since we stored the wrong expected value. (me)
	- Add TIMEOUT to list of opcodes that don't need a file. (Pavel)

- rsxx missing workqueue destry calls. Old bug. (Chuhong)

- Fix blk-iocost active list check (Jiufei)

- Fix impossible-to-hit overflow merge condition, that still hit some
  folks very rarely (Junichi)

- Fix bfq hang issue from 5.3. This didn't get marked for stable, but
  will go into stable post this merge (Paolo)

Please pull!


  git://git.kernel.dk/linux-block.git tags/for-linus-20191115


----------------------------------------------------------------
Chuhong Yuan (1):
      rsxx: add missed destroy_workqueue calls in remove

Jens Axboe (2):
      io_uring: make timeout sequence == 0 mean no sequence
      io_uring: ensure registered buffer import returns the IO length

Jiufei Xue (1):
      iocost: check active_list of all the ancestors in iocg_activate()

Junichi Nomura (1):
      block: check bi_size overflow before merge

Paolo Valente (1):
      block, bfq: deschedule empty bfq_queues not referred by any process

Pavel Begunkov (1):
      io_uring: Fix getting file for timeout

 block/bfq-iosched.c       | 32 ++++++++++++++++++++++++++------
 block/bio.c               |  2 +-
 block/blk-iocost.c        |  8 ++++++--
 drivers/block/rsxx/core.c |  2 ++
 fs/io_uring.c             | 32 ++++++++++++++++++++++++--------
 5 files changed, 59 insertions(+), 17 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2019-11-15 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 19:40 Jens Axboe [this message]
2019-11-15 21:17 ` [GIT PULL] Fixes for 5.4-rc8/final Linus Torvalds
2019-11-15 21:21   ` Jens Axboe
2019-11-15 22:20 ` 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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