public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Fixes for 4.3 final
Date: Fri, 23 Oct 2015 08:24:12 -0600	[thread overview]
Message-ID: <20151023142412.GA22140@kernel.dk> (raw)

Hi Linus,

A final set of fixes for 4.3. It's (again) bigger than I would have
liked, but it's all been through the testing mill and has been carefully
reviewed by multiple parties. Each fix is either a regression fix for
this cycle, or is marked stable. You can scold me at KS.
The pull request contains:

- Three simple fixes for NVMe, fixing regressions since 4.3. From Arnd,
  Christoph, and Keith.

- A single xen-blkfront fix from Cathy, fixing a NULL dereference if an
  error is returned through the staste change callback.

- Fixup for some bad/sloppy code in nbd that got introduced earlier in
  this cycle. From Markus Pargmann.

- A blk-mq tagset use-after-free fix from Junichi.

- A backing device lifetime fix from Tejun, fixing a crash.

- And finally, a set of regression/stable fixes for cgroup writeback
  from Tejun.

Please pull!


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


----------------------------------------------------------------
Arnd Bergmann (1):
      nvme: fix 32-bit build warning

Cathy Avery (1):
      xen-blkfront: check for null drvdata in blkback_changed (XenbusStateClosing)

Christoph Hellwig (1):
      nvme: use an integer value to Linux errno values

Jens Axboe (1):
      Merge branch 'stable/for-jens-4.3' of git://git.kernel.org/.../konrad/xen into for-linus

Junichi Nomura (1):
      blk-mq: fix use-after-free in blk_mq_free_tag_set()

Keith Busch (1):
      NVMe: Fix memory leak on retried commands

Markus Pargmann (1):
      nbd: Add locking for tasks

Tejun Heo (7):
      writeback: laptop_mode_timer_fn() needs rcu_read_lock() around bdi_writeback iteration
      writeback: fix bdi_writeback iteration in wakeup_dirtytime_writeback()
      writeback: bdi_writeback iteration must not skip dying ones
      writeback: memcg dirty_throttle_control should be initialized with wb->memcg_completions
      writeback: fix incorrect calculation of available memory for memcg domains
      block: don't release bdi while request_queue has live references
      writeback: remove broken rbtree_postorder_for_each_entry_safe() usage in cgwb_bdi_destroy()

 block/blk-core.c                 |  2 +-
 block/blk-mq-tag.c               |  1 +
 block/blk-mq.c                   |  4 +--
 block/blk-sysfs.c                |  1 +
 drivers/block/nbd.c              | 36 +++++++++++++++++----
 drivers/block/nvme-core.c        | 24 ++++++++------
 drivers/block/xen-blkfront.c     |  3 +-
 fs/fs-writeback.c                | 35 +++++++++++++-------
 include/linux/backing-dev-defs.h |  3 ++
 include/linux/backing-dev.h      | 69 +++-------------------------------------
 include/linux/memcontrol.h       |  8 +++--
 mm/backing-dev.c                 | 36 +++++++++++++++++----
 mm/memcontrol.c                  | 35 ++++++++++----------
 mm/page-writeback.c              | 54 ++++++++++++++++++-------------
 14 files changed, 167 insertions(+), 144 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2015-10-23 14:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151023142412.GA22140@kernel.dk \
    --to=axboe@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linuxfoundation.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