linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Mark Salter <msalter@redhat.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
	linux-next <linux-next@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: nfs root problem in linux-next
Date: Fri, 29 Jun 2012 22:53:32 +0800	[thread overview]
Message-ID: <20120629145332.GA11745@localhost> (raw)
In-Reply-To: <1340981329.2514.23.camel@deneb.redhat.com>

On Fri, Jun 29, 2012 at 10:48:48AM -0400, Mark Salter wrote:
> On Fri, 2012-06-29 at 13:55 +0000, Myklebust, Trond wrote:
> > Hi Mark and Fengguang,
> > 
> > I believe that I've found the bug that was being triggered in the
> > above
> > patch. It was a mistake in the earlier patch "SUNRPC: Don't decode
> > beyond the end of the RPC reply message", which was failing to
> > correctly
> > initialise the xdr->nwords field.
> > 
> > I've now fixed it and updated the linux-next branch.
> 
> Yes, I can confirm that today's linux-next is booting correctly
> for me on an nfsroot.
> 
> Thanks!
 
I can confirm it, too. Thanks!

      reply	other threads:[~2012-06-29 14:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 20:26 nfs root problem in linux-next Mark Salter
     [not found] ` <1340656006.20557.30.camel-PDpCo7skNiwAicBL8TP8PQ@public.gmane.org>
2012-06-25 23:14   ` Myklebust, Trond
     [not found]     ` <1340666049.4362.9.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2012-06-26  3:17       ` Mark Salter
2012-06-29 13:55         ` Myklebust, Trond
2012-06-29 14:48           ` Mark Salter
2012-06-29 14:53             ` Fengguang Wu [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=20120629145332.GA11745@localhost \
    --to=fengguang.wu@intel.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=msalter@redhat.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).