linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: dhowells@redhat.com, ebiggers@google.com,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>
Subject: Re: [BUG BISECT] NFS root failure (NULL pointer)
Date: Mon, 10 Sep 2018 08:46:40 +0200	[thread overview]
Message-ID: <CAJKOXPdTigJ7DZO3CiHM=zrWqb9MebNmbpbeJB5w0UDWS9FbqA@mail.gmail.com> (raw)
In-Reply-To: <CAJKOXPfc5O0c6HBtM=h2NUXwaiCWVgFC9eVeirLYynfUpU6d3Q@mail.gmail.com>

On Mon, 10 Sep 2018 at 08:44, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On Thu, 6 Sep 2018 at 09:10, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >
> > Hi,
> >
> > Today's next fails to mount NFS root under my ARM targets and fails to
> > mount root from file image under QMU.
> >
> > [ 21.512866] Unable to handle kernel NULL pointer dereference at
> > virtual address 00000000
> > [ 21.695484] [<c03bcc04>] (nfs_fs_mount) from [<c02cf6a4>]
> > (legacy_get_tree+0x34/0xec)
> > [ 21.703225] [<c02cf6a4>] (legacy_get_tree) from [<c029442c>]
> > (vfs_get_tree+0x64/0x180)
> > [ 21.711119] [<c029442c>] (vfs_get_tree) from [<c02b9140>]
> > (do_mount+0x21c/0x958)
> > [ 21.718478] [<c02b9140>] (do_mount) from [<c02b9c38>] (ksys_mount+0x8c/0xbc)
> > [ 21.725513] [<c02b9c38>] (ksys_mount) from [<c0101000>]
> > (ret_fast_syscall+0x0/0x28)
> >
> > Full log from ARM (NFS root):
> > https://krzk.eu/#/builders/25/builds/750/steps/12/logs/serial0
> >
> > The NFS root failure bisected to:
> > bae551929c5433bd56ec4dcb97c7d4a50153d357 is the first bad commit
> > commit bae551929c5433bd56ec4dcb97c7d4a50153d357
> > Author: David Howells <dhowells@redhat.com>
> > Date:   Tue Jul 10 21:43:37 2018 +0100
>
> FYI, the bug is still present in linux-next. All boards fail to boot up.
>
> Let me know if I can help anymore in debugging this.

Hm, my mistake. Today's next boots up fine. Seems fixed. Thanks!

Best regards,
Krzysztof

      reply	other threads:[~2018-09-10 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06  7:10 [BUG BISECT] NFS root failure (NULL pointer) Krzysztof Kozlowski
2018-09-10  6:44 ` Krzysztof Kozlowski
2018-09-10  6:46   ` Krzysztof Kozlowski [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='CAJKOXPdTigJ7DZO3CiHM=zrWqb9MebNmbpbeJB5w0UDWS9FbqA@mail.gmail.com' \
    --to=krzk@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).