linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andreas Dilger <adilger@dilger.ca>, Andi Kleen <andi@firstfloor.org>
Cc: Theodore Ts'o <tytso@mit.edu>, Tahsin Erdogan <tahsin@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: regression: 4.13 cannot follow symlinks on some ext3 fs
Date: Fri, 24 Nov 2017 17:28:19 -0500	[thread overview]
Message-ID: <1511562499.4182.13.camel@HansenPartnership.com> (raw)
In-Reply-To: <706E8F37-95C7-4321-AACA-2ED11F82E625@dilger.ca>

[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]

On Fri, 2017-11-24 at 15:03 -0700, Andreas Dilger wrote:
> On Nov 24, 2017, at 9:51 AM, Andi Kleen <andi@firstfloor.org> wrote:
> > 
> > 
> > > 
> > > We checked old kernels, and old e2fsprogs, and didn't see any
> > > cases
> > > where fast (<= 60 chars) symlinks were created using external
> > > blocks.
> > > It seems that _something_ did create them, and it would be good
> > > to
> > > figure that out so we can determine if it is a widespread problem
> > 
> > I assume it was the original kernel.
> > 
> > > 
> > > 
> > > I think e2fsck can fix this quite easily, and there really isn't
> > > an easy way to revert to the old method if the large xattr
> > > feature
> > > is enabled.  If you are willing to run a new kernel, you should
> > > also
> > > be willing to run a new e2fsck.
> > 
> > It's obviously not enabled on ext3.
> > 
> > > 
> > > We could probably add a fallback to the old mechanism (and print
> > > a one-time warning to upgrade to a newer e2fsck) if an external
> > > fast symlink is found and the large xattr  feature is not
> > > enabled, which would give more time to fix this (hopefully rare
> > > in the wild) case.
> > 
> > If the old kernel created it, then likely all the
> > /lib{,64}/ld-linux.so.2 symlinks have that, which breaks all ELF
> > executables. I suspect in these old file systems it's not
> > particularly rare.
> 
> Sure, but not many people are going to be running a 4.14 kernel with
> a 2007 system. 

I really disagree on this ... most of us who are doing kernel testing
will be running with older systems.  It's true, some of us do install
from scratch and then test, but most of us upgrade (which doesn't
necessarily modify the symlinks).  On your creation test, this is my
cloud system:

bedivere:~# dumpe2fs -h $(df -P / | awk '/dev/ { print $1 }') 2>&1 | grep created
Filesystem created:       Tue Mar 24 20:21:35 2009

Your find command turns up nothing untoward.

My older system is the home entertainment system, but that has an xfs
root dating back to 2005.

I bet I have a laptop even older (currently travelling, so can't
check).

James

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-11-24 22:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171123203330.GN2482@two.firstfloor.org>
     [not found] ` <20171123222317.bq2v26zm5i2jspui@thunk.org>
     [not found]   ` <20171123233101.GP2482@two.firstfloor.org>
     [not found]     ` <700971AC-BDE2-4993-BD56-7497AD8A0FC4@dilger.ca>
     [not found]       ` <20171124020435.GQ2482@two.firstfloor.org>
2017-11-24  6:12         ` regression: 4.13 cannot follow symlinks on some ext3 fs Andreas Dilger
2017-11-24 16:51           ` Andi Kleen
2017-11-24 22:03             ` Andreas Dilger
2017-11-24 22:28               ` James Bottomley [this message]
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=1511562499.4182.13.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=adilger@dilger.ca \
    --cc=andi@firstfloor.org \
    --cc=linux-ext4@vger.kernel.org \
    --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 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).