linux-kernel - Re: NFSroot regression in next with handle inode->i

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1515532316.3571.20.camel@redhat.com>
Date:   Tue, 09 Jan 2018 16:11:56 -0500
From:   Jeff Layton <jlayton@...hat.com>
To:     Tony Lindgren <tony@...mide.com>,
        Krzysztof Kozlowski <krzk@...nel.org>
Cc:     Jan Kara <jack@...e.cz>, Stephen Rothwell <sfr@...b.auug.org.au>,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-omap@...r.kernel.org
Subject: Re: NFSroot regression in next with handle inode->i_version

On Tue, 2018-01-09 at 13:01 -0800, Tony Lindgren wrote:
> 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

Hi Tony,

Krzysztof Kozlowski reported this late last week, and I just pushed an
updated branch earlier this morning that should fix this. It looks like
the current linux-next HEAD has the fixed patchset now too. Let me know
if that doesn't help you.

Thanks,
-- 
Jeff Layton <jlayton@...hat.com>