linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: XArray pull for 5.9
Date: Tue, 20 Oct 2020 21:32:18 +0100	[thread overview]
Message-ID: <20201020203218.GD20115@casper.infradead.org> (raw)

The following changes since commit 856deb866d16e29bd65952e0289066f6078af773:

  Linux 5.9-rc5 (2020-09-13 16:06:00 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/willy/xarray.git tags/xarray-5.9

for you to fetch changes up to 84c34df158cf215b0cd1475ab3b8e6f212f81f23:

  XArray: Fix xas_create_range for ranges above 4 billion (2020-10-13 08:53:29 -0400)

----------------------------------------------------------------
XArray updates for 5.9

 - Fix the test suite after introduction of the local_lock
 - Fix a bug in the IDA spotted by Coverity
 - Change the API that allows the workingset code to delete a node
 - Fix xas_reload() when dealing with entries that occupy multiple indices
 - Add a few more tests to the test suite
 - Fix an unsigned int being shifted into an unsigned long

----------------------------------------------------------------
Hui Su (1):
      radix-tree: fix the comment of radix_tree_next_slot()

Matthew Wilcox (Oracle) (8):
      radix tree test suite: Fix compilation
      ida: Free allocated bitmap in error path
      XArray: Test two more things about xa_cmpxchg
      XArray: Test marked multiorder iterations
      XArray: Fix xas_for_each_conflict documentation
      XArray: Add private interface for workingset node deletion
      XArray: Fix xas_reload for multi-index entries
      XArray: Fix xas_create_range for ranges above 4 billion

 include/linux/radix-tree.h                  |  3 ++-
 include/linux/xarray.h                      | 34 ++++++++++++++++++++----------
 lib/idr.c                                   |  1 +
 lib/radix-tree.c                            |  1 -
 lib/test_xarray.c                           | 32 ++++++++++++++++++++++------
 lib/xarray.c                                | 25 +++++++++++++++++++++-
 mm/workingset.c                             | 13 ++----------
 tools/testing/radix-tree/idr-test.c         | 29 +++++++++++++++++++++++++
 tools/testing/radix-tree/linux/kernel.h     |  1 +
 tools/testing/radix-tree/linux/local_lock.h |  8 +++++++
 tools/testing/radix-tree/test.h             |  4 ----
 11 files changed, 116 insertions(+), 35 deletions(-)
 create mode 100644 tools/testing/radix-tree/linux/local_lock.h


                 reply	other threads:[~2020-10-20 20:32 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=20201020203218.GD20115@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).