From: Darren Hart <dvhart@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, adilger@dilger.ca,
sgw@linux.intel.com, darrick.wong@oracle.com
Subject: Re: [PATCH 0/3 V2] ext2fsprogs: Symlink support
Date: Fri, 04 Jan 2013 16:26:43 -0800 [thread overview]
Message-ID: <50E77343.4010807@infradead.org> (raw)
In-Reply-To: <20130105001521.GD6501@thunk.org>
On 01/04/2013 04:15 PM, Theodore Ts'o wrote:
> On Fri, Jan 04, 2013 at 12:00:57PM -0800, Darren Hart wrote:
>> The following series adds symlink support the libext2fs and adds the command to
>> debugfs. Basic testing demonstrates functional duplication of a small test
>> directory including fastlinks and slowlinks in both the root and a single
>> subdirectory.
>
> One thing I'd really appreciate is if you could write a regression
> test for this new code. You can use tests/d_loaddump and
> tests/f_dup4/script as a model; I'd suggest calling it d_symlink, and
> it would be good if it created a short symlink and a long symlink, and
> that the script verified that you get the expected output when you
> stat the small and long symlinks using debugfs. Then run e2fsck on
> the file system and make sure the file system is consistent.
>
> Note the use of the debugfs commands:
>
> set_current_time 200704102100
> set_super_value lastcheck 0
> set_super_value hash_seed null
> set_super_value mkfs_time 0
>
> and the environment variable:
>
> E2FSCK_TIME=200704102100
>
> in f_dup4's script. These are used to control various variable
> (random or time-specific) values such that so that you can use a
> simple comparison of the output of programs such as debugfs, mke2fs,
> and dumpe2fs using "diff".
>
> Thanks again!!
>
> - Ted
>
> P.S. Actually, while you're at it, if you could also have the script
> create some block and character device files using the debugfs mknod
> command, and perhaps call the test d_create_spec_files instead of
> d_symlink, that would be great! (Since I don't think those functions
> currently any good test coverage.)
Ah, great. I'm all for built-in tests. I'll get on it next week.
Thanks Ted.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2013-01-05 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 20:00 [PATCH 0/3 V2] ext2fsprogs: Symlink support Darren Hart
2013-01-04 20:00 ` [PATCH 1/3] lib/ext2fs: Add ext2fs_symlink Darren Hart
2013-01-04 20:00 ` [PATCH 2/3] debugfs: Add symlink command Darren Hart
2013-01-04 20:01 ` [PATCH 3/3] libext2fs: Remove obsolete redefinition of EXT2_FT_DIR Darren Hart
2013-01-05 20:07 ` [PATCH 1/3] lib/ext2fs: Add ext2fs_symlink Darrick J. Wong
2013-01-05 22:40 ` Theodore Ts'o
2013-01-15 19:17 ` Theodore Ts'o
2013-01-15 19:43 ` Theodore Ts'o
2013-01-15 19:53 ` [PATCH 1/2] debugfs: fix mknod command so that it updates the block group statistics Theodore Ts'o
2013-01-15 19:53 ` [PATCH 2/2] tests: create test for debugfs creating special files Theodore Ts'o
2013-01-19 5:29 ` [PATCH 1/3] lib/ext2fs: Add ext2fs_symlink Darren Hart
2013-01-05 0:15 ` [PATCH 0/3 V2] ext2fsprogs: Symlink support Theodore Ts'o
2013-01-05 0:26 ` Darren Hart [this message]
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=50E77343.4010807@infradead.org \
--to=dvhart@infradead.org \
--cc=adilger@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sgw@linux.intel.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.