From: Theodore Ts'o <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH] create_inode: fix gcc -Wall complaints
Date: Tue, 11 Mar 2014 23:41:10 -0400 [thread overview]
Message-ID: <1394595670-11193-1-git-send-email-tytso@mit.edu> (raw)
We had several functions that were not returning zero on success. Fix
this.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
misc/create_inode.c | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/misc/create_inode.c b/misc/create_inode.c
index 42ac6b2..964c66a 100644
--- a/misc/create_inode.c
+++ b/misc/create_inode.c
@@ -86,10 +86,9 @@ static errcode_t set_inode_extra(ext2_filsys fs, ext2_ino_t cwd,
fill_inode(&inode, st);
retval = ext2fs_write_inode(fs, ino, &inode);
- if (retval) {
+ if (retval)
com_err(__func__, retval, "while writing inode %u", ino);
- return retval;
- }
+ return retval;
}
/* Make a special file which is block, character and fifo */
@@ -115,6 +114,9 @@ errcode_t do_mknod_internal(ext2_filsys fs, ext2_ino_t cwd, const char *name,
mode = LINUX_S_IFIFO;
filetype = EXT2_FT_FIFO;
break;
+ default:
+ abort();
+ /* NOTREACHED */
}
if (!(fs->flags & EXT2_FLAG_RW)) {
@@ -204,11 +206,9 @@ try_again:
}
goto try_again;
}
- if (retval) {
+ if (retval)
com_err("ext2fs_symlink", retval, 0);
- return retval;
- }
next reply other threads:[~2014-03-12 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 3:41 Theodore Ts'o [this message]
2014-03-12 3:45 ` [PATCH] create_inode: fix gcc -Wall complaints Theodore Ts'o
2014-03-12 3:48 ` Darrick J. Wong
2014-03-12 6:33 ` Robert Yang
2014-03-12 6:34 ` Robert Yang
2014-03-12 14:32 ` Theodore Ts'o
2014-03-12 17:59 ` Darrick J. Wong
2014-03-12 20:02 ` Darrick J. Wong
2014-03-12 20:51 ` Theodore Ts'o
2014-03-13 2:21 ` 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=1394595670-11193-1-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).