From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Laurence Oberman <loberman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Issues with starting srp_daemon userspace for a 4.13 kernel
Date: Tue, 18 Jul 2017 13:48:46 -0600 [thread overview]
Message-ID: <20170718194846.GA6048@obsidianresearch.com> (raw)
In-Reply-To: <b74ff7c3-734b-71ae-6b67-9a8ccf255bf6-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, Jul 18, 2017 at 02:07:08PM -0400, Laurence Oberman wrote:
> Hello
>
> What changed in 4.13 so SRP will no longer start because QP cannot modify
> state.
>
> Same test bed as always (based on RHEL 7.3)
>
> Linux dhcp40-139.desklab.eng.bos.redhat.com 4.12.0
>
> Works and srp_daemon activates using:
>
> run_srp_daemon -f /etc/ddn/srp_daemon.conf -R 30 -T 10 -t 7000 -ance -i
> mlx5_0 -p 1 1>/root/srp1.log 2>&1 &
> run_srp_daemon -f /etc/ddn/srp_daemon.conf -R 30 -T 10 -t 7000 -ance -i
> mlx5_1 -p 1 1>/root/srp2.log 2>&1 &
>
> [ 158.020366] scsi host2: SRP.T10:7CFE900300726E4E
> [ 158.574651] scsi host1: SRP.T10:7CFE900300726E4E
>
> Now Testing 4.13, same back-end target that IS running 4.13
>
> Client now booted into 4.13
>
> Linux dhcp40-139.desklab.eng.bos.redhat.com 4.13.0-rc1+
>
> [root@dhcp40-139 ~]# run_srp_daemon -f /etc/ddn/srp_daemon.conf -R 30 -T 10
> -t 7000 -ance -i mlx5_0 -p 1
> srp_daemon[4573]: failed to modify QP state to RTR
> srp_daemon[4573]: failed to modify QP state from RESET to RTS
> [root@dhcp40-139 ~]# run_srp_daemon -f /etc/ddn/srp_daemon.conf -R 30 -T 10
> -t 7000 -ance -i mlx5_1 -p 1
> srp_daemon[4616]: failed to modify QP state to RTR
> srp_daemon[4616]: failed to modify QP state from RESET to RTS
Do you have this patch?
> Subject: [PATCH v2 1/2] RDMA/uverbs: Fix the check for port number
>
> The port number is only valid if IB_QP_PORT is set in the mask.
> So only check port number if it is valid to prevent modify_qp from
> failing due to an invalid port number.
>
> Fixes: 5ecce4c9b17b("Check port number supplied by user verbs cmds")
> Cc: <stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> # v2.6.14+
> Reviewed-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
> Signed-off-by: Mustafa Ismail <mustafa.ismail-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-07-18 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 18:07 Issues with starting srp_daemon userspace for a 4.13 kernel Laurence Oberman
[not found] ` <b74ff7c3-734b-71ae-6b67-9a8ccf255bf6-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-18 19:48 ` Jason Gunthorpe [this message]
[not found] ` <20170718194846.GA6048-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-18 20:01 ` Laurence Oberman
[not found] ` <ef6d29a5-9632-bd9b-1113-1de6671031cc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-18 20:05 ` Bart Van Assche
[not found] ` <1500408333.2664.6.camel-Sjgp3cTcYWE@public.gmane.org>
2017-07-18 20:27 ` Laurence Oberman
[not found] ` <5ca055dc-199f-ee29-fc99-126db132df10-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-18 20:59 ` Laurence Oberman
[not found] ` <8357b19a-26f4-4c27-1b61-b122d4d1a9fd-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-19 19:40 ` Laurence Oberman
[not found] ` <026eedf1-175d-b8df-8396-2bc378e7a5df-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-19 19:49 ` Jason Gunthorpe
[not found] ` <20170719194924.GA14799-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-19 20:03 ` Laurence Oberman
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=20170718194846.GA6048@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=loberman-H+wXaHxf7aLQT0dZR+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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox