From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: Olaf Hering <olaf@aepfle.de>, Anna Schumaker <Anna.Schumaker@Netapp.com>
Cc: Jakub Kicinski <kubakici@wp.pl>, Yotam Gigi <yotamg@mellanox.com>,
"Andy Adamson" <andros@Netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Yotam Gigi <yotam.gi@gmail.com>, mlxsw <mlxsw@mellanox.com>
Subject: Re: nfs NULL-dereferencing in net-next
Date: Thu, 10 Nov 2016 10:02:41 -0500 [thread overview]
Message-ID: <512b06f0-31a6-f397-d618-bd2e7b79c06b@Netapp.com> (raw)
In-Reply-To: <20161110144721.GA30540@aepfle.de>
On 11/10/2016 09:47 AM, Olaf Hering wrote:
> On Thu, Nov 03, Anna Schumaker wrote:
>
>> Aww, I was hoping that patch would work. It still seemed to fix some
>> issues for me when mounting multiple servers, so I'm planning to keep
>> it. Unfortunately I'm out of town this week, so I haven't had much of
>> a chance to keep poking at this issue. I should be able to get back
>> to it next week!
>
> Is this supposed to be fixed already? I get an oops in
> rpc_clnt_xprt_switch_has_addr+0xc/0x40 with 4.9.0-rc4.
Not yet, sorry. I'm waiting on one bugfix patch before sending my pull request.
Thanks for waiting patiently,
Anna
>
> Olaf
>
prev parent reply other threads:[~2016-11-10 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161017201943.64529739@jkicinski-Precision-T1700>
2016-10-25 17:19 ` nfs NULL-dereferencing in net-next Yotam Gigi
2016-10-26 14:40 ` Anna Schumaker
[not found] ` <DB3PR05MB0764B39F6EDF851A8A52EBACACAB0@DB3PR05MB0764.eurprd05.prod.outlook.com>
2016-10-26 18:08 ` Jakub Kicinski
2016-10-26 18:17 ` Anna Schumaker
2016-10-27 6:50 ` Yotam Gigi
2016-10-31 15:25 ` Jakub Kicinski
2016-11-03 13:06 ` Anna Schumaker
2016-11-10 14:47 ` Olaf Hering
2016-11-10 15:02 ` Anna Schumaker [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=512b06f0-31a6-f397-d618-bd2e7b79c06b@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=andros@Netapp.com \
--cc=kubakici@wp.pl \
--cc=linux-nfs@vger.kernel.org \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=trond.myklebust@primarydata.com \
--cc=yotam.gi@gmail.com \
--cc=yotamg@mellanox.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;
as well as URLs for NNTP newsgroup(s).