Re: [stable] Linux 2.6.28.8 (ocfs2 build failure)

[Greg KH]

On Tue, Mar 17, 2009 at 01:26:47PM -0700, Randy Dunlap wrote:
> Enable all possible OCFS2 kconfig options:
> 
> 
> 
> In file included from fs/ocfs2/alloc.c:42:
> fs/ocfs2/journal.h: In function 'ocfs2_begin_ordered_truncate':
> fs/ocfs2/journal.h:451: warning: passing argument 1 of 'jbd2_journal_begin_ordered_truncate' from incompatible pointer type
> fs/ocfs2/journal.h:451: warning: passing argument 2 of 'jbd2_journal_begin_ordered_truncate' makes integer from pointer without a cast
> fs/ocfs2/journal.h:451: error: too many arguments to function 'jbd2_journal_begin_ordered_truncate'
>   CC [M]  fs/ocfs2/buffer_head_io.o
> In file included from fs/ocfs2/aops.c:42:
> fs/ocfs2/journal.h: In function 'ocfs2_begin_ordered_truncate':
> fs/ocfs2/journal.h:451: warning: passing argument 1 of 'jbd2_journal_begin_ordered_truncate' from incompatible pointer type
> fs/ocfs2/journal.h:451: warning: passing argument 2 of 'jbd2_journal_begin_ordered_truncate' makes integer from pointer without a cast
> fs/ocfs2/journal.h:451: error: too many arguments to function 'jbd2_journal_begin_ordered_truncate'
> make[2]: *** [fs/ocfs2/aops.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> In file included from fs/ocfs2/buffer_head_io.c:37:
> fs/ocfs2/journal.h: In function 'ocfs2_begin_ordered_truncate':
> fs/ocfs2/journal.h:451: warning: passing argument 1 of 'jbd2_journal_begin_ordered_truncate' from incompatible pointer type
> fs/ocfs2/journal.h:451: warning: passing argument 2 of 'jbd2_journal_begin_ordered_truncate' makes integer from pointer without a cast
> fs/ocfs2/journal.h:451: error: too many arguments to function 'jbd2_journal_begin_ordered_truncate'
> make[2]: *** [fs/ocfs2/buffer_head_io.o] Error 1
> make[2]: *** [fs/ocfs2/alloc.o] Error 1

Did this show up in 2.6.28.7?

Odds are it's one of the jbd2 patches from Ted.  Ted, any ideas?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/