linux-kernel - 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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 9 Jan 2018 13:01:21 -0800
From:   Tony Lindgren <tony@...mide.com>
To:     Jeff Layton <jlayton@...hat.com>
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: NFSroot regression in next with handle inode->i_version

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