From: "Richard W.M. Jones" <rjones@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: Tahsin Erdogan <tahsin@google.com>
Subject: Fast symlinks stored slow
Date: Wed, 12 Jul 2017 18:07:11 +0100 [thread overview]
Message-ID: <20170712170711.GA19996@redhat.com> (raw)
https://bugzilla.redhat.com/show_bug.cgi?id=1470157
To cut a long story short, we were using libext2fs to create
filesystems where short symlinks (< 60 bytes) were stored the same way
as long symlinks, ie. stored as an ordinary file instead of being
stored in the inode.
This actually worked fine until very recently when this change was
made to the upstream kernel:
commit 407cd7fb83c0ebabb490190e673d8c71ee7df97e
Author: Tahsin Erdogan <tahsin@google.com>
Date: Tue Jul 4 00:11:21 2017 -0400
ext4: change fast symlink test to not rely on i_blocks
which broke these filesystems.
I think the reason we were creating filesystems wrongly in the first
place is because our code has been around since about 2008, and the
nice ext2fs_symlink function that deals properly with fast/slow
symlinks wasn't added until 2013.
It's not too much trouble for us to recreate the incorrect
filesystems. Mostly we're creating one-off throwaway filesystems for
appliances anyway and they don't live for long.
But I suppose this might be a warning that other incorrect filesystems
exist which will break with Linux >= 4.13.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
next reply other threads:[~2017-07-12 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 17:07 Richard W.M. Jones [this message]
2017-07-12 20:52 ` Fast symlinks stored slow Richard W.M. Jones
2017-07-12 21:36 ` Tahsin Erdogan
2017-07-12 23:17 ` Theodore Ts'o
2017-07-13 8:02 ` Richard W.M. Jones
2017-07-13 16:49 ` Theodore Ts'o
2017-07-13 17:13 ` Richard W.M. Jones
2017-07-13 18:50 ` Theodore Ts'o
2017-07-13 20:27 ` Richard W.M. Jones
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=20170712170711.GA19996@redhat.com \
--to=rjones@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tahsin@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).