Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA

Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA

[Jason Gunthorpe]

> However, it would of course be better to teach udma_barrier.h about
> these architectures.

The issue is that some architectures just can't do cache coherent DMA
on any implementation. eg m68k

There is no correct udma_barrier.h at all in those cases.

We need to teach debian to follow cmake and exclude the missing
installables in these cases..

Or do not build at all on these arch's..

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA

[Don Dutile]

On 11/14/2017 02:08 PM, Jason Gunthorpe wrote:
>> However, it would of course be better to teach udma_barrier.h about
>> these architectures.
>
> The issue is that some architectures just can't do cache coherent DMA
> on any implementation. eg m68k
>
> There is no correct udma_barrier.h at all in those cases.
>
> We need to teach debian to follow cmake and exclude the missing
> installables in these cases..
>
> Or do not build at all on these arch's..
>
> Jason
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Jason:
Why am I being cc'd on this debian bug?
I also received a notice about a bug fix in debian, and I had zip to do with it.

Is my name tagged in Debian wrt rdma for some reason? by someone? other?

-dd
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA

[Leon Romanovsky]

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

On Tue, Nov 14, 2017 at 03:41:13PM -0500, Don Dutile wrote:
> On 11/14/2017 02:08 PM, Jason Gunthorpe wrote:
> > > However, it would of course be better to teach udma_barrier.h about
> > > these architectures.
> >
> > The issue is that some architectures just can't do cache coherent DMA
> > on any implementation. eg m68k
> >
> > There is no correct udma_barrier.h at all in those cases.
> >
> > We need to teach debian to follow cmake and exclude the missing
> > installables in these cases..
> >
> > Or do not build at all on these arch's..
> >
> > Jason
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> Jason:
> Why am I being cc'd on this debian bug?
> I also received a notice about a bug fix in debian, and I had zip to do with it.
>
> Is my name tagged in Debian wrt rdma for some reason? by someone? other?

Don,

All of us received this email [1], because maintainer of rdma-core package
is mailing list:

"Package: src:rdma-core; Maintainer for src:rdma-core is Linux RDMA
Mailing List <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>;"

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881731

Thanks

>
> -dd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA

[Bart Van Assche]

On 11/14/17 21:44, Leon Romanovsky wrote:
> On Tue, Nov 14, 2017 at 03:41:13PM -0500, Don Dutile wrote:
>> Jason:
>> Why am I being cc'd on this debian bug?
>> I also received a notice about a bug fix in debian, and I had zip to do with it.
>>
>> Is my name tagged in Debian wrt rdma for some reason? by someone? other?
> 
> Don,
> 
> All of us received this email [1], because maintainer of rdma-core package
> is mailing list:
> 
> "Package: src:rdma-core; Maintainer for src:rdma-core is Linux RDMA
> Mailing List <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>;"
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881731

Something that's very annoying is that "linux-rdma" is not in the 
Cc-list of the bug tracker e-mails so these e-mails escape from filter 
rules. I would appreciate it if either linux-rdma would be removed as a 
maintainer from the Debian bug tracker, if it would be made visible in 
the e-mail Cc-list.

Thanks,

Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Bug#881731: marked as done (rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA)

[Debian Bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

Your message dated Thu, 16 Nov 2017 12:34:16 +0000
with message-id <E1eFJN2-000FNY-O1-zBwJlDMnrE7yUObV3Cmqeti2O/JbrIOy@public.gmane.org>
and subject line Bug#881731: fixed in rdma-core 15-2
has caused the Debian Bug report #881731,
regarding rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
immediately.)


-- 
881731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881731
Debian Bug Tracking System
Contact owner-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org with problems

[-- Attachment #2: Type: message/rfc822, Size: 4410 bytes --]

From: "Aaron M. Ucko" <ucko-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Debian Bug Tracking System <submit-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org>
Subject: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA
Date: Tue, 14 Nov 2017 10:36:57 -0500
Message-ID: <151067381730.19157.7563136692092597267.reportbug-zzSRVt8NT6e1HqDL4FJmnCRvllpaP1wPhfTf9rENOI/R7s880joybQ@public.gmane.org>

Source: rdma-core
Version: 15-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-mips-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org
Usertags: mips mips64el mipsel

Builds of rdma-core for armhf and mips* have been failing:

  -- Performing Test HAVE_COHERENT_DMA
  -- Performing Test HAVE_COHERENT_DMA - Failed
  [...]
  -- Missing Optional Items:
  --  Compiler attribute ifunc NOT supported
  --  Architecture NOT able to do coherent DMA (check util/udma_barrier.h) some providers disabled!
  [...]
  dh_install --fail-missing -X"etc/init.d/srpd" -X"usr/sbin/run_srp_daemon" -X"usr/sbin/srp_daemon.sh"
  dh_install: Please use dh_missing --list-missing/--fail-missing instead
  dh_install: This feature will be removed in compat 12.
  dh_install: Cannot find (any matches for) "etc/modprobe.d/mlx4.conf" (tried in ., debian/tmp)
  [...]
  dh_install: libibverbs-dev missing files: usr/share/man/man7/mlx5dv.7
  dh_install: missing files, aborting
  debian/rules:45: recipe for target 'override_dh_install' failed
  make[1]: *** [override_dh_install] Error 25

As the log indicates, upstream compensates for udma_barrier.h's
limited architecture coverage by disabling providers that need
coherent DMA rather than failing the build altogether.  As such, one
possibility would be to accommodate these providers' potential absence
by (e.g.) wildcarding more aggressively.  However, it would of course
be better to teach udma_barrier.h about these architectures.  I don't
know what appropriate definitions of udma_to_device_barrier,
udma_from_device_barrier, and mmio_flush_writes would be there, but
I'm usertagging porters who presumably will know what to use.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu-KmzlPT+mPuP2fBVCVOL8/A@public.gmane.org

[-- Attachment #3: Type: message/rfc822, Size: 6907 bytes --]

From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: 881731-close-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
Subject: Bug#881731: fixed in rdma-core 15-2
Date: Thu, 16 Nov 2017 12:34:16 +0000
Message-ID: <E1eFJN2-000FNY-O1-zBwJlDMnrE7yUObV3Cmqeti2O/JbrIOy@public.gmane.org>

Source: rdma-core
Source-Version: 15-2

We believe that the bug you reported is fixed in the latest version of
rdma-core, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 881731-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org> (supplier of updated rdma-core package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster-Lx6IQGP78c/Z1gQgfCZkLYSLwOllVvif@public.gmane.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 16 Nov 2017 12:55:28 +0100
Source: rdma-core
Binary: rdma-core ibacm ibverbs-providers ibverbs-utils libibverbs-dev libibverbs1 libibcm-dev libibcm1 libibumad-dev libibumad3 librdmacm-dev librdmacm1 rdmacm-utils srptools
Architecture: source
Version: 15-2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Changed-By: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Description:
 ibacm      - InfiniBand Communication Manager Assistant (ACM)
 ibverbs-providers - User space provider drivers for libibverbs
 ibverbs-utils - Examples for the libibverbs library
 libibcm-dev - Development files for the libibcm library
 libibcm1   - InfiniBand Communication Manager (CM) library
 libibumad-dev - Development files for libibumad
 libibumad3 - InfiniBand Userspace Management Datagram (uMAD) library
 libibverbs-dev - Development files for the libibverbs library
 libibverbs1 - Library for direct userspace use of RDMA (InfiniBand/iWARP)
 librdmacm-dev - Development files for the librdmacm library
 librdmacm1 - Library for managing RDMA connections
 rdma-core  - RDMA core userspace infrastructure and documentation
 rdmacm-utils - Examples for the librdmacm library
 srptools   - Tools for Infiniband attached storage (SRP)
Closes: 881731
Changes:
 rdma-core (15-2) unstable; urgency=medium
 .
   * Do not build ibacm for non-Linux architectures
   * Do not require valgrind if not available
   * Let libibverbs1 15 break ibverbs-providers 14
   * Drop dh-systemd build dependency
   * Bump Standards-Version to 4.1.1 (no changes needed)
   * Drop lintian overrides for false positives
   * Set myself as maintainer (instead of linux-rdma)
   * Do not try to install disabled ibverbs providers on architectures that do
     not provide cache coherent DMA (Closes: #881731)
   * Explicitly list private libibverbs symbols
Checksums-Sha1:
 36eff0afe60382053018f7866b615b03d0a9b558 2782 rdma-core_15-2.dsc
 7e9699b32b6120e075b0d7397bc232f55ab98822 17336 rdma-core_15-2.debian.tar.xz
 99492dd9fad4c4821610aadaef086aec28af6628 8498 rdma-core_15-2_source.buildinfo
Checksums-Sha256:
 05bd4c6e600109fb0ca332af6396c09318c1bc8963fd61bcfec17ad6c9d656af 2782 rdma-core_15-2.dsc
 9962dbb5019b144fe1528e427a786caab8ffd53c75385a4832bf037dff3bbb21 17336 rdma-core_15-2.debian.tar.xz
 a0c83d1bb167c06bc7dd02c87263423d379d18cbb820a941b10771eb77765125 8498 rdma-core_15-2_source.buildinfo
Files:
 68528e3fc865833c7fa7fb3de4997d39 2782 net optional rdma-core_15-2.dsc
 802fd5e813c8a6003ac51e8baa5615b7 17336 net optional rdma-core_15-2.debian.tar.xz
 ed674b1d66cf68c6a0a22f91c27c8ea9 8498 net optional rdma-core_15-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJaDYBQAAoJEN2M1aXejH56IUsQAJ1pCykPrQhmMqpZFS55abWm
wufFH1ZR1ExSes1Vt/9qRwiAg8yVAY/19+ZEhSPbd5zSL51FJdp8dVhACRP1oLj3
n2JZPKCWGijok1A3xBY48+xK7/+U6Qgh8TdbXG2YEnQ6nuJE6snytMIltIOKjh8T
Qz5nfU8OT5MG+3CNC+U7lmM15srRyAeTi9Efl9O6rUFGs5fDkw+BQ0nlZA4GUvKW
FqiTk93UvfoYilqJRb/AykNRjDUxQbFabQXiQ/PMBi41p4LeVC1J2jWj3NhPrOJy
viTp0YOGe+BDRsqXOaksUqUmD/sqXe6GoxFftpUnRfJCFrXnny8jG1xQQQnRbPSe
Uqe1jEOU30ioaj9oXcIQcmDY8+HxcpJzep3qDrwgeQkuEzgJX1HBOwLpJmg81VSq
ra0HDZhBSeEiSSMKTkExxIlXHevwKS5185Ra1dhVnzsBEiPjvQ0VrGkQcBhOXtRA
8qRKGrOV+L7AFYSfQxwDzra6JFnzeirMw8QGiMgTPh4ma7lyEPzQWGYA5qeamOAs
u9JPGiAIZvgTjFI4upUS2xv70uwN7vlN9jIHBRH/2Gx19Ym9khJvnZ6HJ18OLu+0
XHGllGEkJKbF/ccSrHCTzDdQfglr4i5mPuCKVSb/fYzq4gWs0y/ynEZ/+dK5+R7K
LBICGAgJMMOKmjJ45qI1
=h96j
-----END PGP SIGNATURE-----