From: Andi Kleen <andi@firstfloor.org>
To: Theodore Ts'o <tytso@mit.edu>, Andi Kleen <andi@firstfloor.org>,
tahsin@google.com, adilger@dilger.ca,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: regression: 4.13 cannot follow symlinks on some ext3 fs
Date: Thu, 23 Nov 2017 15:31:01 -0800 [thread overview]
Message-ID: <20171123233101.GP2482@two.firstfloor.org> (raw)
In-Reply-To: <20171123222317.bq2v26zm5i2jspui@thunk.org>
On Thu, Nov 23, 2017 at 05:23:17PM -0500, Theodore Ts'o wrote:
> On Thu, Nov 23, 2017 at 12:33:30PM -0800, Andi Kleen wrote:
> >
> > 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.
>
> Hmm, do you know roughly when (what krenel version) this image was
> created? We had done quite a lot of research and the belief was
> kernels never would create a "slow" symlink which was less than 60
> bytes.
The date of the inode is from 2007, the original kernel was 2.6.17
with a 32bit kernel.
> Or was this image something that was created manually (e.g., using debugfs)?
No, it was installed.
-Andi
next prev parent reply other threads:[~2017-11-23 23:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 20:33 regression: 4.13 cannot follow symlinks on some ext3 fs Andi Kleen
2017-11-23 22:23 ` Theodore Ts'o
2017-11-23 23:31 ` Andi Kleen [this message]
2017-11-24 0:41 ` Andreas Dilger
2017-11-24 2:04 ` Andi Kleen
2017-11-24 6:12 ` Andreas Dilger
2017-11-24 16:51 ` Andi Kleen
2017-11-24 22:03 ` Andreas Dilger
2017-11-24 22:28 ` James Bottomley
2017-11-25 1:42 ` Andi Kleen
2017-11-25 22:32 ` Dave Chinner
2017-11-25 22:45 ` Reindl Harald
2017-11-25 22:57 ` Dave Chinner
2017-11-26 15:40 ` Theodore Ts'o
2017-11-26 21:14 ` Dave Chinner
2017-11-26 21:35 ` Reindl Harald
2017-11-26 22:43 ` Dave Chinner
2017-11-27 17:11 ` Theodore Ts'o
2017-11-28 0:42 ` Dave Chinner
2017-12-04 16:35 ` Jan Kara
2017-11-25 3:54 ` Theodore Ts'o
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=20171123233101.GP2482@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=adilger@dilger.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tahsin@google.com \
--cc=tytso@mit.edu \
/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.