public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: xfs@oss.sgi.com, linux-next@vger.kernel.org,
	Al Viro <viro@zeniv.linux.org.uk>, Eric Paris <eparis@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next: vfs/fsnotify trees build warning
Date: Mon, 25 Jan 2010 15:29:25 +1100	[thread overview]
Message-ID: <20100125042925.GM25842@discord.disaster> (raw)
In-Reply-To: <20100125150456.c796f0b0.sfr@canb.auug.org.au>

On Mon, Jan 25, 2010 at 03:04:56PM +1100, Stephen Rothwell wrote:
> Hi Eric, Al,
> 
> Today's linux-next build (x86_64 allmodconfig) produced these warnings:
> 
> In file included from include/linux/security.h:26,
>                  from fs/xfs/linux-2.6/xfs_iops.c:56:
> include/linux/fsnotify.h: In function 'fsnotify_move':
> include/linux/fsnotify.h:87: warning: pointer targets in initialization differ in signedness
> include/linux/fsnotify.h: In function 'fsnotify_create':
> include/linux/fsnotify.h:154: warning: pointer targets in passing argument 5 of 'fsnotify' differ in signedness
> include/linux/fsnotify_backend.h:300: note: expected 'const char *' but argument is of type 'const unsigned char *'
> include/linux/fsnotify.h: In function 'fsnotify_link':
> include/linux/fsnotify.h:167: warning: pointer targets in passing argument 5 of 'fsnotify' differ in signedness
> include/linux/fsnotify_backend.h:300: note: expected 'const char *' but argument is of type 'const unsigned char *'
> include/linux/fsnotify.h: In function 'fsnotify_mkdir':
> include/linux/fsnotify.h:180: warning: pointer targets in passing argument 5 of 'fsnotify' differ in signedness
> include/linux/fsnotify_backend.h:300: note: expected 'const char *' but argument is of type 'const unsigned char *'
> 
> I am not sure why these started turning up (they were there on Friday as
> well and I may have missed them earlier).

I cleaned up the all the sign warnings in the XFS code because
we mirror the kernel code into userspace for tool building (libxfs)
and that results in lots of sign warnings. I left the kernel
warnings switched on in the XFS makefile so we wouldn't re-introduce
the same problems.

Don't know why this isn't showing up in my build though, because:

CONFIG_FSNOTIFY=y

is set and it is obvious the fsnotify wrappers are passing an
unsigned char * (dentry name) to fsnotify() which takes a const char
* for the file name. There's mismatches like this all over the VFS,
so I'm not going to try to fix them....

The patch below should silence the warnings, though.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

xfs: turn off sign warnings

Because they cause warnings in static inline functions conditionally
compiled into XFS from the VFS (e.g. fsnotify).

Signed-off-by: Dave Chinner <david@fromorbit.com>
---
 fs/xfs/Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/xfs/Makefile b/fs/xfs/Makefile
index 1926701..5c5a366 100644
--- a/fs/xfs/Makefile
+++ b/fs/xfs/Makefile
@@ -16,7 +16,7 @@
 # Inc.,  51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
 #
 
-EXTRA_CFLAGS +=	 -I$(src) -I$(src)/linux-2.6 -Wpointer-sign
+EXTRA_CFLAGS +=	 -I$(src) -I$(src)/linux-2.6
 
 XFS_LINUX := linux-2.6
 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

       reply	other threads:[~2010-01-25  4:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100125150456.c796f0b0.sfr@canb.auug.org.au>
2010-01-25  4:29 ` Dave Chinner [this message]
2010-02-08 18:01   ` linux-next: vfs/fsnotify trees build warning Eric Paris
2010-02-08 19:36     ` Christoph Hellwig

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=20100125042925.GM25842@discord.disaster \
    --to=david@fromorbit.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xfs@oss.sgi.com \
    /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