All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Moni Shoua <monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Mukesh Kacker
	<mukesh.kacker-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	Daniel Jurgens <danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-rc v1 2/2] RDMA/cma: Make sure that PSN is not over max allowed
Date: Tue, 28 Nov 2017 09:37:31 +0200	[thread overview]
Message-ID: <20171128073731.GP29104@mtr-leonro.local> (raw)
In-Reply-To: <20171127183755.GB13966-uk2M96/98Pc@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

On Mon, Nov 27, 2017 at 11:37:55AM -0700, Jason Gunthorpe wrote:
> On Sun, Nov 26, 2017 at 08:23:54PM +0200, Leon Romanovsky wrote:
> > From: Moni Shoua <monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> >
> > This patch limits the initial value for PSN to 24 bits as
> > spec requires.
>
> Since this is for-rc, what is the user visible bug this corrects?
>
> I think it is because the QP setup can fail if reserved bits in the
> CMA message happen to be set?

It won't fail, but will print nasty warning down the road after commit
from Majd "IB/core: Make sure that PSN does not overflow" will be
accepted.

The flow is PSN ->
		seq_num ->
			rq_psn ->
				rdma_init_qp_attr() ->
					ib_modify_qp ->
						ib_modify_qp_with_udata ->

1334                 if (attr_mask & IB_QP_RQ_PSN && attr->rq_psn & ~0xffffff) {
1335                         pr_warn("%s: %s rq_psn overflow, masking to 24 bits\n",
1336                                 __func__, qp->device->name);
1337                         attr->rq_psn &= 0xffffff;
1338                 }

Thanks

>
> Jason

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-11-28  7:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 18:23 [PATCH rdma-rc v1 0/2] RDMA fixes for 4.15 Leon Romanovsky
2017-11-26 18:23 ` [PATCH rdma-rc v1 1/2] IB/core: Only enforce security for InfiniBand Leon Romanovsky
     [not found]   ` <20171126182354.18709-2-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-27  5:12     ` Leon Romanovsky
2017-11-27  5:12       ` Leon Romanovsky
     [not found] ` <20171126182354.18709-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-26 18:23   ` [PATCH rdma-rc v1 2/2] RDMA/cma: Make sure that PSN is not over max allowed Leon Romanovsky
     [not found]     ` <20171126182354.18709-3-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-27 18:37       ` Jason Gunthorpe
     [not found]         ` <20171127183755.GB13966-uk2M96/98Pc@public.gmane.org>
2017-11-28  7:37           ` Leon Romanovsky [this message]
2017-12-02  0:01       ` [rdma-rc, v1, " Jason Gunthorpe

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=20171128073731.GP29104@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=mukesh.kacker-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.