[dm-devel] [dm:dm-4.12 29/37] ERROR: "__aeabi_uldivmod" [drivers/md/dm-cache-validator.ko] undefined!

2017-02-18 Thread kbuild test robot
tree:   
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git 
dm-4.12
head:   735bd9981f8f16a1d3439fd3762d52be84ea3e13
commit: 8dcadfc8c4b167fe92884b1316db7057ca5b498c [29/37] dm cache: validator 
policy
config: arm-arm5 (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget 
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
 -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 8dcadfc8c4b167fe92884b1316db7057ca5b498c
# save the attached .config to linux build tree
make.cross ARCH=arm 

All errors (new ones prefixed by >>):

>> ERROR: "__aeabi_uldivmod" [drivers/md/dm-cache-validator.ko] undefined!

---
0-DAY kernel test infrastructureOpen Source Technology Center
https://lists.01.org/pipermail/kbuild-all   Intel Corporation


.config.gz
Description: application/gzip
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: [dm-devel] [PATCHv2] scsi: use 'scsi_device_from_queue()' for scsi_dh

2017-02-18 Thread Mike Snitzer
On Fri, Feb 17, 2017 at 3:27 AM, Christoph Hellwig  wrote:
>
> On Fri, Feb 17, 2017 at 09:06:14AM +0100, Hannes Reinecke wrote:
> > We could, but why?
> > ATM we're only having SCSI devices able to use device handler; adding
> > another layer of indirection doesn't solve anything here.
> > Moving the infrastructure one level up will only make sense if we're
> > getting non-SCSI device handler (ANA?), but until then I'd think it's
> > just overengineering.
>
> Agreed.  Independent of what does the balancing between queues hardware
> handler should be attached by the low-level driver for any future
> transport without any control from DM.

But doesn't Keith's abstraction makes a lot of sense given that you're
providing a device handler interface for NVMe?

The most important part of scsi_dh that DM uses is its calls to
scsi_dh_activate.  Attachment isn't interesting or the issue (DM's
call to scsi_dh_attach is purely legacy now that SCSI attaches the
proper scsi_dh during SCSI's device scan).

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel


[dm-devel] [dm:dm-4.12 29/37] dm-cache-policy-validator.c:undefined reference to `__udivdi3'

2017-02-18 Thread kbuild test robot
tree:   
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git 
dm-4.12
head:   735bd9981f8f16a1d3439fd3762d52be84ea3e13
commit: 8dcadfc8c4b167fe92884b1316db7057ca5b498c [29/37] dm cache: validator 
policy
config: i386-randconfig-x0-02190640 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 8dcadfc8c4b167fe92884b1316db7057ca5b498c
# save the attached .config to linux build tree
make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/built-in.o: In function `create_validator_policy':
>> dm-cache-policy-validator.c:(.text+0x4e3dfc): undefined reference to 
>> `__udivdi3'

---
0-DAY kernel test infrastructureOpen Source Technology Center
https://lists.01.org/pipermail/kbuild-all   Intel Corporation


.config.gz
Description: application/gzip
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel