From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hillf Danton <dhillf@gmail.com>,
Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH] mm, fadvise: don't return -EINVAL when filesystem has no optimization way
Date: Wed, 20 Jun 2012 14:37:41 +0800 [thread overview]
Message-ID: <4FE16FB5.1000601@cn.fujitsu.com> (raw)
In-Reply-To: <4FE16ED3.2090403@gmail.com>
On 06/20/2012 02:33 PM, KOSAKI Motohiro wrote:
> (6/20/12 2:31 AM), Wanlong Gao wrote:
>> On 06/16/2012 04:36 AM, kosaki.motohiro@gmail.com wrote:
>>> From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>>>
>>> Eric Wong reported his test suite was fail when /tmp is tmpfs.
>>>
>>> https://lkml.org/lkml/2012/2/24/479
>>>
>>> Current,input check of POSIX_FADV_WILLNEED has two problems.
>>>
>>> 1) require a_ops->readpage.
>>> But in fact, force_page_cache_readahead() only require
>>> a target filesystem has either ->readpage or ->readpages.
>>> 2) return -EINVAL when filesystem don't have ->readpage.
>>> But, posix says, it should be retrieved a hint. Thus fadvise()
>>> should return 0 if filesystem has no optimization way.
>>> Especially, userland application don't know a filesystem type
>>> of TMPDIR directory as Eric pointed out. Then, userland can't
>>> avoid this error. We shouldn't encourage to ignore syscall
>>> return value.
>>>
>>> Thus, this patch change a return value to 0 when filesytem don't
>>> support readahead.
>>>
>>> Cc: linux-mm@kvack.org
>>> Cc: Hugh Dickins <hughd@google.com>
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> Cc: Hillf Danton <dhillf@gmail.com>
>>> Signed-off-by: Eric Wong <normalperson@yhbt.net>
>>> Tested-by: Eric Wong <normalperson@yhbt.net>
>>> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>>> ---
>>> mm/fadvise.c | 18 +++++++-----------
>>> 1 files changed, 7 insertions(+), 11 deletions(-)
>>>
>>> diff --git a/mm/fadvise.c b/mm/fadvise.c
>>> index 469491e..33e6baf 100644
>>> --- a/mm/fadvise.c
>>> +++ b/mm/fadvise.c
>>> @@ -93,11 +93,6 @@ SYSCALL_DEFINE(fadvise64_64)(int fd, loff_t offset, loff_t len, int advice)
>>> spin_unlock(&file->f_lock);
>>> break;
>>> case POSIX_FADV_WILLNEED:
>>> - if (!mapping->a_ops->readpage) {
>>> - ret = -EINVAL;
>>> - break;
>>> - }
>>
>> Why not check both readpage and readpages, if they are not here,
>> just beak and no following force_page_cache_readahead ?
>
> They are checked in force_page_cache_readahead.
I see, thank you.
Reviewed-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-06-20 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 20:36 [PATCH] mm, fadvise: don't return -EINVAL when filesystem has no optimization way kosaki.motohiro
2012-06-20 5:01 ` KOSAKI Motohiro
2012-06-20 6:31 ` Wanlong Gao
2012-06-20 6:33 ` KOSAKI Motohiro
2012-06-20 6:37 ` Wanlong Gao [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=4FE16FB5.1000601@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dhillf@gmail.com \
--cc=hughd@google.com \
--cc=kosaki.motohiro@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=normalperson@yhbt.net \
/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