public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Bates" <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Bates <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>,
	monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] rdma_rxe: Ensure rdma_rxe module init occurs at correct time
Date: Sun, 18 Sep 2016 18:59:16 -0500	[thread overview]
Message-ID: <a3e5f61b65cdf92c192daef1da319718.squirrel@webmail.raithlin.com> (raw)
In-Reply-To: <2fa6c4b3-6fcb-b0f1-adaf-94895710827d-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Fri, September 16, 2016 1:06 pm, Doug Ledford wrote:
> On 9/15/2016 5:45 PM, Stephen Bates wrote:
>
>> When the Soft-RoCE module is built into the kernel there is a
>> initialization issue when CONFIG_IPV6 is selected. Use late_initcall to
>> ensure the rxe module is loaded later. This fix is based on one proposed
>> by Logan Gunthorpe on a much older code base [1].
>
> Your commit message doesn't make sense.  You start by saying that
> soft-RoCE is compiled in, then say "the rxe module is loaded later". Well,
> which is it?  I'm not sure exactly the problem you are fixing. However, I
> know that the series Leon posted for the rxe driver included a fix
> specifically for IPv6 tunnel creation issues that result in an oops.  I
> suspect that patch might solve your problem.  So, I'm going to drop this
> patch.  Once you get a chance to test with the other patch applied, if
> your problem still exists, then please repost this patch with a clearer
> commit message and we can add this as well.

Doug

Yes on reflection the commit message associated with this patch was not as
clear as it could have been. Apologies. I will be more explicit on the v1.
To answer your questions:

1. This patch should be applied on top of the three patches that came from
Leon [1]. I will make that clear in v1.

2. My patch applies to the case where rmda_rxe is built-in and not when it
is a module. Currently the module_init is called before IPv6 is setup and
that results in a load failure of rxe.

3. When rdma_rxe is built as a module the problem is not observed because
the rdma_rxe module is not probed until the system is up and running.

4. The change from module_init to late_initcall means that IPv6 has had
enough time to come up befoe the rdma_rxe init is executed.

I hope that clarifies things. I will get a v1 out shortly with an improved
commit log.

[1] http://marc.info/?l=linux-rdma&m=147307739626544&w=2

Cheers

Stephen Bates

>
>> [1] https://github.com/sbates130272/qemu-minimal/blob/rdma/patches/\
>> 0001-Changes-needed-to-use-rxe-compiled-into-the-kernel.patch
>>
>>
>> Signed-off-by: Stephen Bates <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
>> ---
>> drivers/infiniband/sw/rxe/rxe.c | 2 +- 1 file changed, 1 insertion(+), 1
>> deletion(-)
>>
>> diff --git a/drivers/infiniband/sw/rxe/rxe.c
>> b/drivers/infiniband/sw/rxe/rxe.c index 08e09d9..97bc74a 100644 ---
>> a/drivers/infiniband/sw/rxe/rxe.c +++ b/drivers/infiniband/sw/rxe/rxe.c
>> @@ -392,5 +392,5 @@ static void __exit rxe_module_exit(void)
>> pr_info("rxe: unloaded\n");
>> }
>>
>>
>> -module_init(rxe_module_init);
>> +late_initcall(rxe_module_init);
>> module_exit(rxe_module_exit);
>>
>
>
> --
> Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> GPG Key ID: 0E572FDD
>
>
>

--
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

  parent reply	other threads:[~2016-09-18 23:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 21:45 [PATCH] rdma_rxe: Ensure rdma_rxe module init occurs at correct time Stephen Bates
     [not found] ` <1473975936-9970-1-git-send-email-sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
2016-09-16 18:06   ` Doug Ledford
     [not found]     ` <2fa6c4b3-6fcb-b0f1-adaf-94895710827d-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-18 23:59       ` Stephen Bates [this message]
     [not found]         ` <a3e5f61b65cdf92c192daef1da319718.squirrel-2RFepEojUI2m/tTznewQxVaTQe2KTcn/@public.gmane.org>
2016-09-20 13:59           ` Yonatan Cohen

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=a3e5f61b65cdf92c192daef1da319718.squirrel@webmail.raithlin.com \
    --to=sbates-pv7u853semvwk0htik3j/w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=monis-VPRAkNaXOzVWk0Htik3J/w@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