summaryrefslogtreecommitdiff
path: root/drivers/nvdimm/Makefile
diff options
context:
space:
mode:
authorJason Gunthorpe <jgg@mellanox.com>2019-01-11 08:21:44 +0200
committerJason Gunthorpe <jgg@mellanox.com>2019-01-14 14:02:22 -0700
commitd6f4a21f309dfe10a5693ad236358dd6fcc46f7a (patch)
treee900ea13c1f32a17f7d7a9fe059d030c38ee5d3b /drivers/nvdimm/Makefile
parent9d9f59b4204bc41896c866b3e5856e5b416aa199 (diff)
RDMA/uverbs: Mark ioctl responses with UVERBS_ATTR_F_VALID_OUTPUT
When the ioctl interface for the write commands was introduced it did not mark the core response with UVERBS_ATTR_F_VALID_OUTPUT. This causes rdma-core in userspace to not mark the buffers as written for valgrind. Along the same lines it turns out we have always missed marking the driver data. Fixing both of these makes valgrind work properly with rdma-core and ioctl. Fixes: 4785860e04bc ("RDMA/uverbs: Implement an ioctl that can call write and write_ex handlers") Signed-off-by: Jason Gunthorpe <jgg@mellanox.com> Reviewed-by: Artemy Kovalyov <artemyko@mellanox.com> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
Diffstat (limited to 'drivers/nvdimm/Makefile')
0 files changed, 0 insertions, 0 deletions