Re: [PATCH v7 16/18] MAINTAINERS: add entry for KUnit the unit testing framework

2019-07-09 Thread shuah
On 7/9/19 12:30 AM, Brendan Higgins wrote: Add myself as maintainer of KUnit, the Linux kernel's unit testing framework. Signed-off-by: Brendan Higgins Reviewed-by: Greg Kroah-Hartman Reviewed-by: Logan Gunthorpe --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) diff --gi

Re: [PATCH v7 16/18] MAINTAINERS: add entry for KUnit the unit testing framework

2019-07-09 Thread Brendan Higgins
On Tue, Jul 9, 2019 at 7:53 AM shuah wrote: > > On 7/9/19 12:30 AM, Brendan Higgins wrote: > > Add myself as maintainer of KUnit, the Linux kernel's unit testing > > framework. > > > > Signed-off-by: Brendan Higgins > > Reviewed-by: Greg Kroah-Hartman > > Reviewed-by: Logan Gunthorpe > > --- >

[v7 1/3] device-dax: fix memory and resource leak if hotplug fails

2019-07-09 Thread Pavel Tatashin
When add_memory() function fails, the resource and the memory should be freed. Fixes: c221c0b0308f ("device-dax: "Hotplug" persistent memory for use like normal RAM") Signed-off-by: Pavel Tatashin Reviewed-by: Dave Hansen --- drivers/dax/kmem.c | 5 - 1 file changed, 4 insertions(+), 1 de

[v7 0/3] "Hotremove" persistent memory

2019-07-09 Thread Pavel Tatashin
Changelog: v7 - Added Dan Williams Reviewed-by to the last patch, and small change to dev_err() otput format as was suggested by Dan. v6 - A few minor changes and added reviewed-by's. - Spent time studying lock ordering issue that was reported by Vishal Verma, but that issue already exists in

[v7 2/3] mm/hotplug: make remove_memory() interface useable

2019-07-09 Thread Pavel Tatashin
As of right now remove_memory() interface is inherently broken. It tries to remove memory but panics if some memory is not offline. The problem is that it is impossible to ensure that all memory blocks are offline as this function also takes lock_device_hotplug that is required to change memory sta

[v7 3/3] device-dax: "Hotremove" persistent memory that is used like normal RAM

2019-07-09 Thread Pavel Tatashin
It is now allowed to use persistent memory like a regular RAM, but currently there is no way to remove this memory until machine is rebooted. This work expands the functionality to also allows hotremoving previously hotplugged persistent memory, and recover the device for use for other purposes.

Re: [PATCH v7 08/18] objtool: add kunit_try_catch_throw to the noreturn list

2019-07-09 Thread Josh Poimboeuf
On Mon, Jul 08, 2019 at 11:30:13PM -0700, Brendan Higgins wrote: > Fix the following warning seen on GCC 7.3: > kunit/test-test.o: warning: objtool: kunit_test_unsuccessful_try() falls > through to next function kunit_test_catch() > > kunit_try_catch_throw is a function added in the following p

Re: [PATCH v7 06/18] kbuild: enable building KUnit

2019-07-09 Thread Masahiro Yamada
On Tue, Jul 9, 2019 at 3:34 PM Brendan Higgins wrote: > > KUnit is a new unit testing framework for the kernel and when used is > built into the kernel as a part of it. Add KUnit to the root Kconfig and > Makefile to allow it to be actually built. > > Signed-off-by: Brendan Higgins > Cc: Masahiro

Re: [PATCH v4 0/6] Fixes related namespace alignment/page size/big endian

2019-07-09 Thread Aneesh Kumar K.V
Hi Dan, Can you merge this to your tree? -aneesh "Aneesh Kumar K.V" writes: > This series handle configs where hugepage support is not enabled by default. > Also, we update some of the information messages to make sure we use > PAGE_SIZE instead > of SZ_4K. We now store page size and struct p