Re: [dm-devel] [PATCH 2/2] dm-writecache

2017-12-22 Thread Dan Williams
On Fri, Dec 22, 2017 at 12:56 PM, Mikulas Patocka wrote: > > > On Fri, 8 Dec 2017, Dan Williams wrote: > >> > > What about memcpy_flushcache? >> > >> > but >> > >> > - using memcpy_flushcache is overkill if we need just one or two 8-byte >> > writes to the metadata area. Why

Re: [dm-devel] [PATCH 2/2] dm-writecache

2017-12-22 Thread Mikulas Patocka
On Fri, 8 Dec 2017, Dan Williams wrote: > > > What about memcpy_flushcache? > > > > but > > > > - using memcpy_flushcache is overkill if we need just one or two 8-byte > > writes to the metadata area. Why not use movnti directly? > > > > The driver performs so many 8-byte moves that the cost

Re: [dm-devel] regression 4.15-rc: kernel oops in dm-multipath

2017-12-22 Thread Christian Borntraeger
I will give that commit a try. Thanks. On 12/22/2017 05:00 PM, Bart Van Assche wrote: > On Fri, 2017-12-22 at 10:53 +0100, Christian Borntraeger wrote: >> any quick ideas? > > Hello Christian, > > Was commit afc567a4977b ("dm table: fix regression from improper > dm_dev_internal.count >

Re: [dm-devel] [for-4.16 PATCH 0/5] block, nvme, dm: allow DM multipath to use NVMe's error handler

2017-12-22 Thread Mike Snitzer
On Tue, Dec 19 2017 at 4:05pm -0500, Mike Snitzer wrote: > These patches enable DM multipath to work well on NVMe over Fabrics > devices. Currently that implies CONFIG_NVME_MULTIPATH is _not_ set. > > But follow-on work will be to make it so that native NVMe multipath >

Re: [dm-devel] regression 4.15-rc: kernel oops in dm-multipath

2017-12-22 Thread Mike Snitzer
On Fri, Dec 22 2017 at 11:00am -0500, Bart Van Assche wrote: > On Fri, 2017-12-22 at 10:53 +0100, Christian Borntraeger wrote: > > any quick ideas? > > Hello Christian, > > Was commit afc567a4977b ("dm table: fix regression from improper > dm_dev_internal.count >

[dm-devel] [PATCH 01/11] block_dev: Support checking inode permissions in lookup_bdev()

2017-12-22 Thread Dongsu Park
From: Seth Forshee When looking up a block device by path no permission check is done to verify that the user has access to the block device inode at the specified path. In some cases it may be necessary to check permissions towards the inode, such as allowing

[dm-devel] regression 4.15-rc: kernel oops in dm-multipath

2017-12-22 Thread Christian Borntraeger
Since 4.15-rc1 I get the following during boot relatively often (but not 100% reproducable) Seems to be 2 oopses... "[5.851954] device-mapper: multipath service-time: version 0.3.0 loaded "[5.902244] Unable to handle kernel pointer dereference in virtual kernel address space "[