On Mon, Jun 25, 2018 at 03:34:38PM -0600, Jason Gunthorpe wrote:
On Sun, Jun 24, 2018 at 11:23:41AM +0300, Leon Romanovsky wrote:
quoted
From: Leon Romanovsky <redacted>
Hi,
This is bunch of patches trigged by running syzkaller internally.
I'm sending them based on rdma-next mainly for two reasons:
1, Most of the patches fix the old issues and it doesn't matter when
they will hit the Linus's tree: now or later in a couple of weeks
during merge window.
2. They interleave with code cleanup, mlx5-next patches and Michael's
feedback on flow counters series.
Thanks
Leon Romanovsky (12):
RDMA/uverbs: Protect from attempts to create flows on unsupported QP
RDMA/uverbs: Fix slab-out-of-bounds in ib_uverbs_ex_create_flow
I applied these two to for-rc
quoted
RDMA/uverbs: Check existence of create_flow callback
RDMA/verbs: Drop kernel variant of create_flow
RDMA/verbs: Drop kernel variant of destroy_flow
net/mlx5: Rate limit errors in command interface
RDMA/uverbs: Don't overwrite NULL pointer with ZERO_SIZE_PTR
RDMA/umem: Don't check for negative return value of dma_map_sg_attrs()
RDMA/uverbs: Remove redundant check
These to for-next
Jason,
We would like to see patch "[PATCH mlx5-next 05/12] net/mlx5:
Rate limit errors in command interface" in out mlx5-next. Is it possible
at this point to drop it from for-next, so I'll be able to take it into
mlx5-next?
Thanks
quoted
overflow.h: Add arithmetic shift helper
RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq
RDMA/mlx5: Reuse existed shift_overlow helper
And these will have to be respun.
Thanks,
Jason