From: Mel Gorman <mgorman@techsingularity.net>
To: Nicolai Stange <nicstange@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Junichi Nomura <j-nomura@ce.jp.nec.com>,
Hugh Dickins <hughd@google.com>,
Matthew Wilcox <willy@linux.intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/filemap: generic_file_read_iter(): check for zero reads unconditionally
Date: Tue, 29 Mar 2016 09:46:19 +0100 [thread overview]
Message-ID: <20160329084619.GK31585@techsingularity.net> (raw)
In-Reply-To: <1458817738-2753-1-git-send-email-nicstange@gmail.com>
On Thu, Mar 24, 2016 at 12:08:58PM +0100, Nicolai Stange wrote:
> If
> - generic_file_read_iter() gets called with a zero read length,
> - the read offset is at a page boundary,
> - IOCB_DIRECT is not set
> - and the page in question hasn't made it into the page cache yet,
> then do_generic_file_read() will trigger a readahead with a req_size hint
> of zero.
>
> Since roundup_pow_of_two(0) is undefined, UBSAN reports
>
> UBSAN: Undefined behaviour in include/linux/log2.h:63:13
> shift exponent 64 is too large for 64-bit type 'long unsigned int'
> CPU: 3 PID: 1017 Comm: sa1 Tainted: G L 4.5.0-next-20160318+ #14
> [...]
> Call Trace:
> [...]
> [<ffffffff813ef61a>] ondemand_readahead+0x3aa/0x3d0
> [<ffffffff813ef61a>] ? ondemand_readahead+0x3aa/0x3d0
> [<ffffffff813c73bd>] ? find_get_entry+0x2d/0x210
> [<ffffffff813ef9c3>] page_cache_sync_readahead+0x63/0xa0
> [<ffffffff813cc04d>] do_generic_file_read+0x80d/0xf90
> [<ffffffff813cc955>] generic_file_read_iter+0x185/0x420
> [...]
> [<ffffffff81510b06>] __vfs_read+0x256/0x3d0
> [...]
>
> when get_init_ra_size() gets called from ondemand_readahead().
>
> The net effect is that the initial readahead size is arch dependent for
> requested read lengths of zero: for example, since
>
> 1UL << (sizeof(unsigned long) * 8)
>
> evaluates to 1 on x86 while its result is 0 on ARMv7, the initial readahead
> size becomes 4 on the former and 0 on the latter.
>
> What's more, whether or not the file access timestamp is updated for zero
> length reads is decided differently for the two cases of IOCB_DIRECT
> being set or cleared: in the first case, generic_file_read_iter()
> explicitly skips updating that timestamp while in the latter case, it is
> always updated through the call to do_generic_file_read().
>
> According to POSIX, zero length reads "do not modify the last data access
> timestamp" and thus, the IOCB_DIRECT behaviour is POSIXly correct.
>
> Let generic_file_read_iter() unconditionally check the requested read
> length at its entry and return immediately with success if it is zero.
>
> Signed-off-by: Nicolai Stange <nicstange@gmail.com>
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
Mel Gorman
SUSE Labs
--
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:[~2016-03-29 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 11:08 [PATCH] mm/filemap: generic_file_read_iter(): check for zero reads unconditionally Nicolai Stange
2016-03-24 11:45 ` Jan Kara
2016-03-25 7:50 ` Nicolai Stange
2016-03-29 8:46 ` Mel Gorman [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=20160329084619.GK31585@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=nicstange@gmail.com \
--cc=ross.zwisler@linux.intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).