From: Or Gerlitz <ogerlitz@mellanox.com>
To: <roland@kernel.org>
Cc: <linux-rdma@vger.kernel.org>, <haggaie@mellanox.com>,
Eli Cohen <eli@mellanox.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Roland Dreier" <roland@purestorage.com>
Subject: Re: [PATCH for 3.16] IB/mlx5: Enable block multicast loopback for kernel consumers too
Date: Tue, 15 Jul 2014 11:42:56 +0300 [thread overview]
Message-ID: <53C4E990.6080402@mellanox.com> (raw)
In-Reply-To: <1403703854-14328-1-git-send-email-ogerlitz@mellanox.com>
On 25/06/2014 16:44, Or Gerlitz wrote:
> Under commit f360d88 we advertize blocking multicast loopback to both
> kernel and user-space consumers, but disallow the kernel ones (e.g IPoIB)
> to use it with their UD QPs, fix that.
>
> Fixes: f360d88 ('IB/mlx5: Add block multicast loopback support')
> Reported-by: Haggai Eran <haggaie@mellanox.com>
> Signed-off-by: Eli Cohen <eli@mellanox.com>
> Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
> ---
Roland, this needs to go into 3.16 and 3.15-stable too as the bug was
introduced in 3.15-rc2, please make sure to add it to your 3.16 rc pull
request, OK?
Or.
> drivers/infiniband/hw/mlx5/qp.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/infiniband/hw/mlx5/qp.c b/drivers/infiniband/hw/mlx5/qp.c
> index d13ddf1..bbbcf38 100644
> --- a/drivers/infiniband/hw/mlx5/qp.c
> +++ b/drivers/infiniband/hw/mlx5/qp.c
> @@ -675,7 +675,7 @@ static int create_kernel_qp(struct mlx5_ib_dev *dev,
> int err;
>
> uuari = &dev->mdev.priv.uuari;
> - if (init_attr->create_flags & ~IB_QP_CREATE_SIGNATURE_EN)
> + if (init_attr->create_flags & ~(IB_QP_CREATE_SIGNATURE_EN | IB_QP_CREATE_BLOCK_MULTICAST_LOOPBACK))
> return -EINVAL;
>
> if (init_attr->qp_type == MLX5_IB_QPT_REG_UMR)
>
parent reply other threads:[~2014-07-15 8:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1403703854-14328-1-git-send-email-ogerlitz@mellanox.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C4E990.6080402@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=eli@mellanox.com \
--cc=haggaie@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@kernel.org \
--cc=roland@purestorage.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox