From: Tony Lindgren <tony@atomide.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Jan Kara <jack@suse.cz>, Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: NFSroot regression in next with handle inode->i_version
Date: Tue, 9 Jan 2018 13:01:21 -0800 [thread overview]
Message-ID: <20180109210121.GX3875@atomide.com> (raw)
Hi all,
Commit 4b5bd6a8e7cf ("fs: handle inode->i_version more efficiently")
causes NFSroot to not boot to login in Linux next on my ARM boxes.
Also the attempted boot seems really slow, so the reason for not
reaching login might be not being able to kick the watchdog as
I'm seeing spontaneous reboots.
Reverting the patch makes things work again, any ideas?
Can you guys please revert this in next while this is being
investigated?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: NFSroot regression in next with handle inode->i_version
Date: Tue, 9 Jan 2018 13:01:21 -0800 [thread overview]
Message-ID: <20180109210121.GX3875@atomide.com> (raw)
Hi all,
Commit 4b5bd6a8e7cf ("fs: handle inode->i_version more efficiently")
causes NFSroot to not boot to login in Linux next on my ARM boxes.
Also the attempted boot seems really slow, so the reason for not
reaching login might be not being able to kick the watchdog as
I'm seeing spontaneous reboots.
Reverting the patch makes things work again, any ideas?
Can you guys please revert this in next while this is being
investigated?
Regards,
Tony
next reply other threads:[~2018-01-09 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 21:01 Tony Lindgren [this message]
2018-01-09 21:01 ` NFSroot regression in next with handle inode->i_version Tony Lindgren
2018-01-09 21:11 ` Jeff Layton
2018-01-09 21:11 ` Jeff Layton
2018-01-09 21:21 ` Tony Lindgren
2018-01-09 21:21 ` Tony Lindgren
2018-01-10 10:59 ` Keerthy
2018-01-10 10:59 ` Keerthy
2018-01-10 10:59 ` Keerthy
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=20180109210121.GX3875@atomide.com \
--to=tony@atomide.com \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.