From: Trond Myklebust <trondmy@hammerspace.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"daniel@zonque.org" <daniel@zonque.org>,
"jlayton@kernel.org" <jlayton@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 5.1.0-rc4: Oops in __rpc_execute() when trying to boot from NFS
Date: Thu, 11 Apr 2019 19:50:15 +0000 [thread overview]
Message-ID: <be1368dce21d38bb1e90d2c84671ed51498d77ea.camel@hammerspace.com> (raw)
In-Reply-To: <78dbd13a-9a91-9a67-eaa6-ea7f0190898b@zonque.org>
Hi Daniel,
On Tue, 2019-04-09 at 19:54 +0200, Daniel Mack wrote:
> On 9/4/2019 6:55 PM, Trond Myklebust wrote:
> > On Tue, 2019-04-09 at 18:25 +0200, Daniel Mack wrote:
> > > On 8/4/2019 8:51 PM, Trond Myklebust wrote:
> > > > On Mon, 2019-04-08 at 19:01 +0200, Daniel Mack wrote:
> > > > > Hi,
> > > > >
> > > > > I'm seeing the Oops below when trying to boot 5.1.0-rc4 on an
> > > > > ARM
> > > > > PXA3xx
> > > > > platform. v5.0 did not show this effect with the same
> > > > > cmdline.
> > > > >
> > > > Please do bisect if that is at all practical. I'm having
> > > > trouble
> > > > interpreting this Oops.
> > >
> > > Here you go:
> > >
> > > 009a82f6437490c262584d65a14094a818bcb747 is the first bad commit
> > > commit 009a82f6437490c262584d65a14094a818bcb747
> > > Author: Trond Myklebust <trond.myklebust@hammerspace.com>
> > > Date: Sat Mar 9 12:07:17 2019 -0500
> > >
> > > SUNRPC: Micro-optimise when the task is known not to be
> > > sleeping
> > >
> > > In cases where we know the task is not sleeping, try to
> > > optimise
> > > away the indirect call to task->tk_action() by replacing it
> > > with
> > > a direct call.
> > > Only change tail calls, to allow gcc to perform tail call
> > > elimination.
> >
> > Ah... It looks like we explicitly turn off tail call optimisation
> > in
> > some ARM configs, so this might be a stack overflow.
> >
> > Does your config file have THUMB2_AVOID_R_ARM_THM_JUMP11 set?
>
> Nope. I don't even have THUMB2_KERNEL.
>
> In the meantime, I tried to trace that with some printks, but the bug
> appears evasive, and the backtrace changes as soon as I modify the
> timing. Hmm.
>
> Happy to test patches if you have any idea.
>
Could you please try pulling the 'testing' branch from
http://git.linux-nfs.org/?p=trondmy/linux-nfs.git;a=shortlog;h=refs/heads/testing
i.e. 'git pull git://git.linux-nfs.org/projects/trondmy/linux-nfs.git
testing'
to see if that suffices to fix the issue you're reporting?
Thanks
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-04-11 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 17:01 5.1.0-rc4: Oops in __rpc_execute() when trying to boot from NFS Daniel Mack
2019-04-08 18:51 ` Trond Myklebust
2019-04-09 16:25 ` Daniel Mack
2019-04-09 16:55 ` Trond Myklebust
2019-04-09 17:54 ` Daniel Mack
2019-04-11 19:50 ` Trond Myklebust [this message]
2019-04-12 5:57 ` Daniel Mack
2019-04-12 13:34 ` 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=be1368dce21d38bb1e90d2c84671ed51498d77ea.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=bfields@fieldses.org \
--cc=daniel@zonque.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox