[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100228102937.cac7dc55.sfr@canb.auug.org.au>
Date: Sun, 28 Feb 2010 10:29:37 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Eric Paris <eparis@...hat.com>, viro@...iv.linux.org.uk,
hch@...radead.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] notification: including fanotify
Hi Linus,
On Sat, 27 Feb 2010 13:33:21 -0800 (PST) Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
> On Sat, 27 Feb 2010, Linus Torvalds wrote:
> >
> > (b) the compile has obviously never been tested with any modern gcc
> > version. I get tons of warnings after the pull, like
>
> In fact, this seems to be due to a commit that explicitly says:
>
> I do not add -Wpointer-sign to the fsnotify
> code as there are still issues with kstrdup and strlen which would pop
> out needless warnings.
>
> but then the patch actually has
>
> --- a/fs/notify/Makefile
> +++ b/fs/notify/Makefile
> @@ -1,3 +1,5 @@
> +EXTRA_CFLAGS += -Wpointer-sign
> +
>
> WTF? Which part of this was tested AT ALL? Clearly there was not even a
> compile test going on.
You also forgot to mention that this whole tree has been rebased since
(my) Friday and the version of the above commit in linux-next does not
have that hunk.
As that commit does say, these warnings first came to light when the xfs
tree added that flag to its build. It was removed again after a couple of
days because it generates quite a few warnings (as you have seen). It
appears that thee needs to be more cleanup before it is enabled again.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists