From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from one.firstfloor.org ([193.170.194.197]:34178 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753276AbdKWUdc (ORCPT ); Thu, 23 Nov 2017 15:33:32 -0500 Date: Thu, 23 Nov 2017 12:33:30 -0800 From: Andi Kleen To: tahsin@google.com, adilger@dilger.ca, tytso@mit.edu Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: regression: 4.13 cannot follow symlinks on some ext3 fs Message-ID: <20171123203330.GN2482@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, I have an older qemu VM image that i sometimes use for testing. It stopped booting with 4.13-4.14 because it couldn't run init. It uses ext3 for the root file system. I instrumented the code and found that it failed to follow the /lib/ld-linux.so.2 -> ld-2.3.6.so symlink for init's ELF interpreter. I bisected it to down to commit 407cd7fb83c0ebabb490190e673d8c71ee7df97e (refs/bisect/bad) Author: Tahsin Erdogan Date: Tue Jul 4 00:11:21 2017 -0400 ext4: change fast symlink test to not rely on i_blocks when I revert this commit 4.14 my VM runs fine again. Dump of the inode in debugfs: debugfs: Inode: 1767 Type: symlink Mode: 0777 Flags: 0x0 Generation: 0 User: 0 Group: 0 Size: 11 File ACL: 0 Directory ACL: 0 Links: 1 Blockcount: 8 Fragment: Address: 0 Number: 0 Size: 0 ctime: 0x45ad7ba0 -- Wed Jan 17 01:28:00 2007 atime: 0x5a164be5 -- Thu Nov 23 04:17:41 2017 mtime: 0x45ad7ba0 -- Wed Jan 17 01:28:00 2007 BLOCKS: (0):11006 TOTAL: 1 -Andi