| 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
| ||
|
Message-Id: <1332113668-4364-4-git-send-email-daniel.vetter@ffwll.ch> Date: Mon, 19 Mar 2012 00:34:28 +0100 From: Daniel Vetter <daniel.vetter@...ll.ch> To: linaro-mm-sig@...ts.linaro.org, LKML <linux-kernel@...r.kernel.org>, DRI Development <dri-devel@...ts.freedesktop.org>, linux-media@...r.kernel.org Cc: Daniel Vetter <daniel.vetter@...ll.ch> Subject: [PATCH 4/4] dma-buf: document fd flags and O_CLOEXEC requirement Otherwise subsystems will get this wrong and end up with and second export ioctl with the flag and O_CLOEXEC support added. Signed-Off-by: Daniel Vetter <daniel.vetter@...ll.ch> --- Documentation/dma-buf-sharing.txt | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/Documentation/dma-buf-sharing.txt b/Documentation/dma-buf-sharing.txt index 9f3aeef..087e261 100644 --- a/Documentation/dma-buf-sharing.txt +++ b/Documentation/dma-buf-sharing.txt @@ -319,6 +319,11 @@ Miscellaneous notes - Any exporters or users of the dma-buf buffer sharing framework must have a 'select DMA_SHARED_BUFFER' in their respective Kconfigs. +- To avoid the wrath of userspace library writers exporting subsystems must have + a flag parameter in the ioctl that creates the dma-buf fd which needs to + support at least the O_CLOEXEC fd flag. This needs to be passed in the flag + parameter of dma_buf_export. + References: [1] struct dma_buf_ops in include/linux/dma-buf.h [2] All interfaces mentioned above defined in include/linux/dma-buf.h -- 1.7.7.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists