linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <tytso@mit.edu>, <dvhart@linux.intel.com>
Cc: <linux-ext4@vger.kernel.org>
Subject: [PATCH V2 06/11] misc/create_inode.c: create directory
Date: Tue, 24 Dec 2013 03:47:22 -0500	[thread overview]
Message-ID: <1387874847-4922-7-git-send-email-liezhi.yang@windriver.com> (raw)
In-Reply-To: <1387874847-4922-1-git-send-email-liezhi.yang@windriver.com>

The do_mkdir_internal() is used for making dir on the target fs, most of
the code are from debugfs/debugfs.c, the debugfs/debugfs.c will be
modified to use this function.

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
---
 misc/create_inode.c |   31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/misc/create_inode.c b/misc/create_inode.c
index d199bf4..be967bd 100644
--- a/misc/create_inode.c
+++ b/misc/create_inode.c
@@ -127,6 +127,37 @@ try_again:
 /* Make a directory in the fs */
 errcode_t do_mkdir_internal(ext2_ino_t cwd, const char *name, struct stat *st)
 {
+	char			*cp;
+	ext2_ino_t		parent_ino, ino;
+	errcode_t		retval;
+	struct ext2_inode	inode;
+
+
+	cp = strrchr(name, '/');
+	if (cp) {
+		*cp = 0;
+		if ((retval =  ext2fs_namei(current_fs, root, cwd, name, &parent_ino))){
+			com_err(name, retval, 0);
+			return retval;
+		}
+		name = cp+1;
+	} else
+		parent_ino = cwd;
+
+try_again:
+	retval = ext2fs_mkdir(current_fs, parent_ino, 0, name);
+	if (retval == EXT2_ET_DIR_NO_SPACE) {
+		retval = ext2fs_expand_dir(current_fs, parent_ino);
+		if (retval) {
+			com_err(__FUNCTION__, retval, "while expanding directory");
+			return retval;
+		}
+		goto try_again;
+	}
+	if (retval) {
+		com_err("ext2fs_mkdir", retval, 0);
+		return retval;
+	}
 }
 
 static errcode_t copy_file(int fd, ext2_ino_t newfile, int bufsize, int make_holes)
-- 
1.7.10.4


  parent reply	other threads:[~2013-12-24  8:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  8:47 [PATCH V2 00/11] e2fsprogs/mke2fs: add an option: -d root-directory Robert Yang
2013-12-24  8:47 ` [PATCH V2 01/11] mke2fs: add the ability to copy files from a given directory Robert Yang
2013-12-24  8:47 ` [PATCH V2 02/11] misc/create_inode.c: copy files recursively Robert Yang
2013-12-24  8:47 ` [PATCH V2 03/11] misc/create_inode.c: create special file Robert Yang
2013-12-24  8:47 ` [PATCH V2 04/11] misc/create_inode.c: create symlink Robert Yang
2013-12-24  8:47 ` [PATCH V2 05/11] misc/create_inode.c: copy regular file Robert Yang
2013-12-24  8:47 ` Robert Yang [this message]
2013-12-24  8:47 ` [PATCH V2 07/11] misc/create_inode.c: set owner/mode/time for the inode Robert Yang
2013-12-24  8:47 ` [PATCH V2 08/11] mke2fs.c: add an option: -d root-directory Robert Yang
2013-12-24  8:47 ` [PATCH V2 09/11] misc/create_inode.c: handle hardlinks Robert Yang
2013-12-25  3:14   ` Robert Yang
2013-12-25  3:21   ` [PATCH V3 " Robert Yang
2013-12-24  8:47 ` [PATCH V2 10/11] debugfs: use the functions in misc/create_inode.c Robert Yang
2013-12-24  8:47 ` [PATCH V2 11/11] mke2fs.8.in: update the manual for the -d option Robert Yang

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=1387874847-4922-7-git-send-email-liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=linux-ext4@vger.kernel.org \
    --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).