From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] XArray for 5.5
Date: Wed, 22 Jan 2020 22:41:40 -0800 [thread overview]
Message-ID: <20200123064140.GG4675@bombadil.infradead.org> (raw)
I had an oops live on stage at linux.conf.au this year, and it turned out
to be a bug in xas_find() which I can't prove isn't triggerable in the
current codebase. Then in looking for the bug, I spotted two more bugs.
The bots have had a few days to chew on this with no problems reported,
and it passes the test-suite (which now has more tests to make sure
these problems don't come back).
So I feel pretty comfortable asking you to pull this, even though it's
so late in the development cycle.
The following changes since commit 0058b0a506e40d9a2c62015fe92eb64a44d78cd9:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2019-11-08 18:21:05 -0800)
are available in the Git repository at:
git://git.infradead.org/users/willy/linux-dax.git tags/xarray-5.5
for you to fetch changes up to 00ed452c210a0bc1ff3ee79e1ce6b199f00a0638:
XArray: Add xa_for_each_range (2020-01-17 22:33:37 -0500)
----------------------------------------------------------------
XArray updates for 5.5
Primarily bugfixes, mostly around handling index wrap-around correctly.
A couple of doc fixes and adding missing APIs.
----------------------------------------------------------------
Matthew Wilcox (Oracle) (7):
XArray: Fix xas_pause at ULONG_MAX
XArray: Improve documentation of search marks
XArray: Add wrappers for nested spinlocks
XArray: Fix infinite loop with entry at ULONG_MAX
XArray: Fix xa_find_after with multi-index entries
XArray: Fix xas_find returning too many entries
XArray: Add xa_for_each_range
Documentation/core-api/xarray.rst | 70 +++++++++++++++++++++--------------
include/linux/xarray.h | 45 +++++++++++++++++++---
lib/test_xarray.c | 78 ++++++++++++++++++++++++++++++++-------
lib/xarray.c | 41 ++++++++++++++------
4 files changed, 175 insertions(+), 59 deletions(-)
next reply other threads:[~2020-01-23 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 6:41 Matthew Wilcox [this message]
2020-01-23 19:40 ` [GIT PULL] XArray for 5.5 Linus Torvalds
2020-01-23 20:05 ` 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=20200123064140.GG4675@bombadil.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).