From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"David Miller" <davem@davemloft.net>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"David Ahern" <dsa@cumulusnetworks.com>,
brouer@redhat.com, "Ingo Molnar" <mingo@kernel.org>
Subject: Re: Boot failures with net-next after rebase to v4.17.0-rc1
Date: Wed, 25 Apr 2018 09:16:35 +0200 [thread overview]
Message-ID: <20180425091635.7e8a7ffd@redhat.com> (raw)
In-Reply-To: <CA+55aFx-V8L602X-EHgrJPNA49v_ZiBZW=+v=tcSQK5QZOXYJw@mail.gmail.com>
On Tue, 24 Apr 2018 13:04:23 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Apr 24, 2018 at 12:54 PM, Jesper Dangaard Brouer
> <brouer@redhat.com> wrote:
> > Hi all,
> >
> > I'm experiencing boot failures with net-next git-tree after it got
> > rebased/merged with Linus'es tree at v4.17.0-rc1.
>
> I suspect it's the global bit stuff that came in very late in the
> merge window, and had been developed and tested for a while before,
> but showed some problems under some configs.
>
> The fix is currently in the x86/pti tree in -tip, see:
>
> x86/pti: Fix boot problems from Global-bit setting
>
> and I expect it will percolate upstream soon.
>
> In the meantime, it would be good to verify that merging that x86/pti
> branch fixes it for you?
Thanks for spotting this so quickly!
I have verified that this DOES solve the issue for me :-)))
If others are hit by this, and cannot wait for Linus to pull the tip
tree, this is the pull command:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti
> There is another candidate for boot problems - do you happen to have
> CONFIG_DEFERRED_STRUCT_PAGE_INIT enabled? That can under certain
> circumstances get a percpu setup page fault because memory hadn't been
> initialized sufficiently.
CONFIG_DEFERRED_STRUCT_PAGE_INIT is not set
> The fix there is to move the mm_init() call one step earlier in
> init_main(): start_kernel() (to before trap_init()).
>
> And if it's neither of the above, I think you'll need to help bisect it.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2018-04-25 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 19:54 Boot failures with net-next after rebase to v4.17.0-rc1 Jesper Dangaard Brouer
2018-04-24 20:04 ` Linus Torvalds
2018-04-25 7:16 ` Jesper Dangaard Brouer [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=20180425091635.7e8a7ffd@redhat.com \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=toke@toke.dk \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).