netdev - RE: [RFC 00/11] QLogic RDMA Driver (qedr) RFC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <SN1PR07MB2207486633D88B5C65D547F9F8F10@SN1PR07MB2207.namprd07.prod.outlook.com>
Date:   Wed, 14 Sep 2016 14:44:47 +0000
From:   "Amrani, Ram" <Ram.Amrani@...ium.com>
To:     Jason Gunthorpe <jgunthorpe@...idianresearch.com>
CC:     "dledford@...hat.com" <dledford@...hat.com>,
        David Miller <davem@...emloft.net>,
        Yuval Mintz <Yuval.Mintz@...gic.com>,
        Ariel Elior <Ariel.Elior@...gic.com>,
        Michal Kalderon <Michal.Kalderon@...gic.com>,
        Rajesh Borundia <rajesh.borundia@...gic.com>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        netdev <netdev@...r.kernel.org>
Subject: RE: [RFC 00/11] QLogic RDMA Driver (qedr) RFC

> Anything that is used with copy_to/from_user, ib_copy_to/from_udata, 
> etc, etc must be in a include/uapi header.
> 
> Any constant you might want to copy into your userspace provider must 
> be in include/uapi.
> 
I understand you mean something like https://www.spinics.net/lists/linux-rdma/msg40414.html ([RFC rdma-next 0/3] Move mlx5 vendor specific to UAPI directory)

> Avoid copying headers in your user space and use the standard kernel 
> names to access your driver's uapi.
So the user library should be able to compile against these headers in their location and not hold identical copies.
What do you mean by "standard kernel names"?

Thanks,
Ram