Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760166AbeAIVB2 (ORCPT + 1 other); Tue, 9 Jan 2018 16:01:28 -0500 Received: from muru.com ([72.249.23.125]:40020 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753056AbeAIVBZ (ORCPT ); Tue, 9 Jan 2018 16:01:25 -0500 Date: Tue, 9 Jan 2018 13:01:21 -0800 From: Tony Lindgren To: Jeff Layton Cc: Jan Kara , Stephen Rothwell , 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 Message-ID: <20180109210121.GX3875@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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