From: Randy Dunlap <rdunlap@xenotime.net>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] f2fs: Resolve build failures
Date: Fri, 30 Nov 2012 10:21:51 -0800 [thread overview]
Message-ID: <50B8F93F.5070909@xenotime.net> (raw)
In-Reply-To: <1354266457-3858-1-git-send-email-jaegeuk.kim@samsung.com>
On 11/30/2012 01:07 AM, Jaegeuk Kim wrote:
> There exist two build failures reported by Randy Dunlap as follows.
>
> (on i386)
> a. (config-r8857)
> ERROR: "f2fs_xattr_advise_handler" [fs/f2fs/f2fs.ko] undefined!
>
> Key configs in (config-r8857) are as follows.
> CONFIG_F2FS_FS=m
> # CONFIG_F2FS_STAT_FS is not set
> CONFIG_F2FS_FS_XATTR=y
> # CONFIG_F2FS_FS_POSIX_ACL is not set
>
> The error was occurred due to the function location that we made a mistake.
> Recently we added a new functionality for users to indicate cold files
> explicitly through xattr operations (i.e., f2fs_xattr_advise_handler).
>
> This handler should have been added in xattr.c instead of acl.c in order
> to avoid an undefined operation like in this case where XATTR is set and
> ACL is not set.
>
> b. (config-r8855)
> fs/f2fs/file.c: In function 'f2fs_vm_page_mkwrite':
> fs/f2fs/file.c:97:2: error: implicit declaration of function
> 'block_page_mkwrite_return'
>
> Key config in (config-r8855) is CONFIG_BLOCK.
>
> Obviously, f2fs works on top of the block device so that we should consider
> carefully a sort of config dependencies.
>
> The reason why this error was occurred was that f2fs_vm_page_mkwrite() calls
> block_page_mkwrite_return() which is enalbed only if CONFIG_BLOCK is set.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
> ---
> fs/f2fs/Kconfig | 1 +
> fs/f2fs/acl.c | 51 ---------------------------------------------------
> fs/f2fs/xattr.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 52 insertions(+), 51 deletions(-)
Thanks, that fixes the build errors that I saw.
Reported-by: Randy Dunlap <rdunlap@xenotime.net>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
--
~Randy
prev parent reply other threads:[~2012-11-30 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 9:07 [PATCH] f2fs: Resolve build failures Jaegeuk Kim
2012-11-30 18:21 ` Randy Dunlap [this message]
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=50B8F93F.5070909@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).