From: Neil Brown <neilb@suse.de>
To: Elimar Riesebieter <riesebie@lxtec.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, nfs@lists.sourceforge.net
Subject: Re: 2.6.22-rc2 built on ppc
Date: Tue, 22 May 2007 15:40:50 +1000 [thread overview]
Message-ID: <18002.33378.2388.800348@notabene.brown> (raw)
In-Reply-To: message from Elimar Riesebieter on Sunday May 20
On Sunday May 20, riesebie@lxtec.de wrote:
> Hi,
>
> FYI, building the kernel modules with
> gcc (GCC) 4.1.3 20070514 (prerelease) (Debian 4.1.2-7)
> on my powerbook (PPC) gives:
>
> ...
> fs/nfsd/nfs4acl.c: In function '_posix_to_nfsv4_one':
> fs/nfsd/nfs4acl.c:227: warning: 'pas.owner' may be used uninitialized in this function
> fs/nfsd/nfs4acl.c:227: warning: 'pas.group' may be used uninitialized in this function
> fs/nfsd/nfs4acl.c:227: warning: 'pas.other' may be used uninitialized in this function
> ...
Yes....
The reality is that these fields will not be used uninitialised. This
is because every 'posix_acl' always has an ACL_USER_OBJ, and
ACL_GROUP_OBJ, and an ACL_OTHER. Isn't it Bruce ??
Maybe we could set all three to zero at the top of
summarize_posix_acl, but doing that just to get the compiler to be
quite is sometimes frowned upon.
Bruce? Do you have an opinion?
NeilBrown
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-05-22 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 11:25 2.6.22-rc2 built on ppc Elimar Riesebieter
2007-05-22 5:40 ` Neil Brown [this message]
2007-05-22 17:20 ` J. Bruce Fields
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=18002.33378.2388.800348@notabene.brown \
--to=neilb@suse.de \
--cc=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=riesebie@lxtec.de \
/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