linux/lib/test_xarray.c, branch v4.20

XArray: Fix xa_alloc when id exceeds max

2018-12-13T19:07:33Z

Specifying a starting ID greater than the maximum ID isn't something attempted very often, but it should fail. It was succeeding due to xas_find_marked() returning the wrong error state, so add tests for both xa_alloc() and xas_find_marked(). Fixes: b803b42823d0 ("xarray: Add XArray iterators") Signed-off-by: Matthew Wilcox

XArray tests: Check iterating over multiorder entries

2018-12-06T14:25:33Z

There was no bug here, but there was no test coverage for this scenario. Signed-off-by: Matthew Wilcox

XArray tests: Handle larger indices more elegantly

2018-12-06T14:25:15Z

xa_mk_value() only handles values up to LONG_MAX. I successfully hid that inside xa_store_index() and xa_erase_index(), but it turned out I also needed it for testing xa_alloc() on 32-bit machines. So extract xa_mk_index() from the above two functions, and convert the non-constant users of xa_mk_value() to xa_mk_index(). Signed-off-by: Matthew Wilcox

XArray tests: Add missing locking

2018-11-19T14:41:11Z

Lockdep caught me being sloppy in the test suite and failing to lock the XArray appropriately. Reported-by: kernel test robot Signed-off-by: Matthew Wilcox

XArray tests: Correct some 64-bit assumptions

2018-11-16T21:38:45Z

The test-suite caught these two mistakes when compiled for 32-bit. I had only been running the test-suite in 64-bit mode. Signed-off-by: Matthew Wilcox

XArray: Regularise xa_reserve

2018-11-05T21:38:08Z

The xa_reserve() function was a little unusual in that it attempted to be callable for all kinds of locking scenarios. Make it look like the other APIs with __xa_reserve, xa_reserve_bh and xa_reserve_irq variants. Signed-off-by: Matthew Wilcox

XArray: Fix xa_for_each with a single element at 0

2018-11-05T19:56:46Z

The following sequence of calls would result in an infinite loop in xa_find_after(): xa_store(xa, 0, x, GFP_KERNEL); index = 0; xa_for_each(xa, entry, index, ULONG_MAX, XA_PRESENT) { } xa_find_after() was confusing the situation where we found no entry in the tree with finding a multiorder entry, so it would look for the successor entry forever. Just check for this case explicitly. Includes a few new checks in the test suite to be sure this doesn't reappear. Signed-off-by: Matthew Wilcox

xarray: Add range store functionality

2018-10-21T14:46:46Z

This version of xa_store_range() really only supports load and store. Our only user only needs basic load and store functionality, so there's no need to do the extra work to support marking and overlapping stores correctly yet. Signed-off-by: Matthew Wilcox

xarray: Move multiorder_check to in-kernel tests

2018-10-21T14:46:46Z

This version is a little less thorough in order to be a little quicker, but tests the important edge cases. Also test adding a multiorder entry at a non-canonical index, and erasing it. Signed-off-by: Matthew Wilcox

xarray: Move multiorder_shrink to kernel tests

2018-10-21T14:46:46Z

Test this functionality inside the kernel as well as in userspace. Also remove insert_bug() as there's no comparable thing to test in the XArray code. Signed-off-by: Matthew Wilcox