From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Paolo Abeni <pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Hal Rosenstock
<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH rdma] infiniband: call ipv6 route lookup via the stub interface
Date: Fri, 28 Apr 2017 12:56:43 -0400 [thread overview]
Message-ID: <1493398603.3041.156.camel@redhat.com> (raw)
In-Reply-To: <09d4a8a81a499ab61ed6883ae1aa17c5fa0a5b49.1493368728.git.pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Fri, 2017-04-28 at 11:20 +0200, Paolo Abeni wrote:
> The infiniband address handle can be triggered to resolve an ipv6
> address in response to MAD packets, regardless of the ipv6
> module being disabled via the kernel command line argument.
>
> That will cause a call into the ipv6 routing code, which is not
> initialized, and a conseguent oops.
>
> This commit addresses the above issue replacing the direct lookup
> call with an indirect one via the ipv6 stub, which is properly
> initialized according to the ipv6 status (e.g. if ipv6 is
> disabled, the routing lookup fails gracefully)
>
> Signed-off-by: Paolo Abeni <pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Thanks Paolo, applied. I also added a Cc: to stable for kernel 3.12+
since that's when the stub was added.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
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
prev parent reply other threads:[~2017-04-28 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 9:20 [PATCH rdma] infiniband: call ipv6 route lookup via the stub interface Paolo Abeni
[not found] ` <09d4a8a81a499ab61ed6883ae1aa17c5fa0a5b49.1493368728.git.pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-28 16:56 ` Doug Ledford [this message]
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=1493398603.3041.156.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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.