From: Nix <nix@esperi.org.uk>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
Subject: Re: [Patch] sunrpc: NULL utsname dereference on NFS umount during namespace cleanup
Date: Tue, 03 Feb 2015 00:20:49 +0000 [thread overview]
Message-ID: <87mw4vu9pa.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <CAHQdGtT=_ZeXvG2BQjy7wYeM+APnnPiF-vTTJOu3aCyVBWG=xw@mail.gmail.com> (Trond Myklebust's message of "Mon, 2 Feb 2015 17:54:50 -0500")
On 2 Feb 2015, Trond Myklebust verbalised:
> Hmm... I'm at a loss to see how rpcb_create can ever call
> rpc_new_client() with a null value for the nodename with that patch
> applied. Are you 100% sure that the above Oops came from a patched
> kernel? That IP address of "rpc_new_client+0x13b/0x1f2" looks
> identical to the one in your original posting.
I've been swapping kernels a lot of late due to bisection -- it is
perfectly possible that I somehow ended up running an unpatched one :/
I'll do a build from scratch with the patch and reboot into it. My
apologies if this was a false positive (which it looks quite like it
might have been: your evidence is pretty persuasive!)
--
NULL && (void)
next prev parent reply other threads:[~2015-02-03 0:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 21:06 [Patch] sunrpc: NULL utsname dereference on NFS umount during namespace cleanup Bruno Prémont
2015-01-25 21:55 ` Trond Myklebust
2015-01-30 23:49 ` Trond Myklebust
2015-01-31 0:44 ` Nix
2015-02-02 17:41 ` Nix
2015-02-02 22:54 ` Trond Myklebust
2015-02-03 0:20 ` Nix [this message]
2015-01-31 9:02 ` Bruno Prémont
2015-02-04 17:08 ` Bruno Prémont
2015-02-04 19:06 ` Trond Myklebust
2015-02-04 21:52 ` Bruno Prémont
2015-02-04 22:29 ` Trond Myklebust
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=87mw4vu9pa.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=bfields@fieldses.org \
--cc=bonbons@linux-vserver.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 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.