From: Darren Hart <dvhart@infradead.org>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, adilger@dilger.ca, sgw@linux.intel.com,
darrick.wong@oracle.com
Subject: [PATCH 0/3 V2] ext2fsprogs: Symlink support
Date: Fri, 4 Jan 2013 12:00:57 -0800 [thread overview]
Message-ID: <1357329660-28639-1-git-send-email-dvhart@infradead.org> (raw)
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.
There is one FIXME/question remaining in the symlink implementation regarding
the use of ext2fs_bmap2 where I would particularly welcome some review. I found
the various block creation, allocation, and bitmap functions to be rather
difficult to grok in terms of which to use when.
Otherwise, I believe I have addressed Ted's and Darrick's comments from the
previous RFC.
Thanks,
Darren Hart
Intel Open Source Technology Center
next reply other threads:[~2013-01-04 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 20:00 Darren Hart [this message]
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
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=1357329660-28639-1-git-send-email-dvhart@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 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).