From: Jesse Millan <jessem@cs.pdx.edu>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] [PATCH] Fix misleading gcc4 warning,
Date: Fri, 03 Jun 2005 18:52:54 +0000 [thread overview]
Message-ID: <42A0A706.1030109@cs.pdx.edu> (raw)
In-Reply-To: <42966B18.6020802@cs.pdx.edu>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Similar story as the ext2 version of acl.c.
The function ext3_set_acl() declares a size_t called 'size' without
setting it to an initial value. 'size' is not referred to again until
you see:
if (acl) {
// Email KJ comments: size IS initialized in this function
// only if acl != NULL
value = ext3_acl_to_disk(acl, &size);
...
}
// Email KJ comments: If acl == NULL, size is passed to
// this function uninitialized.
error = ext3_xattr_set_handle(handle, inode, name_index, "",
value, size, 0);
...
The external function ext3_xattr_set_handle() initializes a member of a
ext3_xattr_info structure to the value of size.
Initializing 'size' to zero eliminates the compiler warning and the
possibility of passing an uninitialized variable around.
*Note unlike previous patches, initializing 'size' in the function
ext3_acl_to_disk() does not eliminate this particular warning. This is
because of the conditional call to the function that initializes it.
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 424 bytes --]
Signed-off-by: Jesse Millan <jessem@cs.pdx.edu>
--- linux-2.6.12-rc5.kj/fs/ext3/acl.c~ 2005-06-01 16:46:37.735581769 -0700
+++ linux-2.6.12-rc5.kj/fs/ext3/acl.c 2005-06-01 16:48:11.361096097 -0700
@@ -225,7 +225,7 @@ ext3_set_acl(handle_t *handle, struct in
struct ext3_inode_info *ei = EXT3_I(inode);
int name_index;
void *value = NULL;
- size_t size;
+ size_t size = 0;
int error;
if (S_ISLNK(inode->i_mode))
[-- Attachment #3: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-06-03 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 0:34 [KJ] [PATCH] Fix misleading gcc4 warning, Jesse Millan
2005-05-27 3:52 ` [KJ] [PATCH] Fix misleading gcc4 warning, addr may be used randy_dunlap
2005-05-30 0:03 ` [KJ] [PATCH] Fix misleading gcc4 warning, Adrian Bunk
2005-05-30 0:14 ` Jesse Millan
2005-05-30 1:59 ` Adrian Bunk
2005-05-30 4:56 ` Jesse Millan
2005-05-30 8:24 ` Arnd Bergmann
2005-06-01 21:35 ` Jesse Millan
2005-06-03 18:52 ` Jesse Millan [this message]
2005-06-16 22:16 ` [KJ] [PATCH] Fix misleading gcc4 warning: (160) offset and block Jesse Millan
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=42A0A706.1030109@cs.pdx.edu \
--to=jessem@cs.pdx.edu \
--cc=kernel-janitors@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 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.