public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: fstests@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>
Subject: [PATCH 1/2] generic/360: Create symlink with valid path
Date: Wed, 14 Jun 2017 09:19:20 +0200	[thread overview]
Message-ID: <20170614071921.6741-1-jack@suse.cz> (raw)

A test is creating symlink with a path containing name 1023 characters
long. Such file name is invalid for most filesystems (the limit on file
name lenght is mostly 255 characters) and UDF actually complains about
this and so the test fails. Since the point of this test is to verify
storage of the symlink, change the test to use a valid path where each
component name has only 254 characters.

Signed-off-by: Jan Kara <jack@suse.cz>
---
 tests/generic/360     | 4 +++-
 tests/generic/360.out | 2 +-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/tests/generic/360 b/tests/generic/360
index 86e554bb5fec..cc5623f552e0 100755
--- a/tests/generic/360
+++ b/tests/generic/360
@@ -50,9 +50,11 @@ _require_test
 linkfile=$TEST_DIR/$seq.symlink
 rm -f $linkfile
 
+FNAME=$(perl -e 'print "a"x254')
+
 # Create a symlink points to a very long path, so that the path could not be
 # hold in inode
-ln -s `perl -e 'print "a"x1023'` $linkfile
+ln -s $FNAME/$FNAME/$FNAME/$FNAME $linkfile
 
 # Check symlink contains the correct path.
 # 1023 chars are a bit long for golden image output, compute the md5 checksum
diff --git a/tests/generic/360.out b/tests/generic/360.out
index 1f0459bbcb5d..a076d99bb091 100644
--- a/tests/generic/360.out
+++ b/tests/generic/360.out
@@ -1,2 +1,2 @@
 QA output created by 360
-cd3b0a56bc304075e28a20a4edd57068  -
+36c1641ab5d82b582cd2baa1ace16277  -
-- 
2.12.3


             reply	other threads:[~2017-06-14  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  7:19 Jan Kara [this message]
2017-06-14  7:19 ` [PATCH 2/2] common: UDF does not support journalling Jan Kara

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=20170614071921.6741-1-jack@suse.cz \
    --to=jack@suse.cz \
    --cc=fstests@vger.kernel.org \
    /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