From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
open@kvack.org, list@kvack.org,
MEMORY MANAGEMENT <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: fix mmap overflow checking
Date: Wed, 05 Sep 2012 11:20:07 +0800 [thread overview]
Message-ID: <5046C4E7.5040407@cn.fujitsu.com> (raw)
In-Reply-To: <20120904135924.b61e04e0.akpm@linux-foundation.org>
On 09/05/2012 04:59 AM, Andrew Morton wrote:
> On Tue, 4 Sep 2012 17:23:00 +0800
> Wanlong Gao <gaowanlong@cn.fujitsu.com> wrote:
>
>> POSIX said that if the file is a regular file and the value of "off"
>> plus "len" exceeds the offset maximum established in the open file
>> description associated with fildes, mmap should return EOVERFLOW.
>
> That's what POSIX says, but what does Linux do? It is important that
Current Linux checks whether the shifted off+len exceed ULONG_MAX, it seems
never happen.
> we precisely describe and understand the behaviour change, as there is
> potential here to break existing applications.
>
> I'm assuming that Linux presently permits the mmap() and then generates
> SIGBUS if an access is attempted beyond the max file size?
What I saw is ENOMEM because the "len" here is too large.
>
>> /* offset overflow? */
>> - if ((pgoff + (len >> PAGE_SHIFT)) < pgoff)
>> - return -EOVERFLOW;
>> + if (off + len < off)
>> + return -EOVERFLOW;
>
> Well, this treats sizeof(off_t) as the "offset maximum established in
> the open file". But from my reading of the above excerpt, we should in
> fact be checking against the underlying fs's s_maxbytes?
More reasonable, how about following?
---
mm/mmap.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/mm/mmap.c b/mm/mmap.c
index ae18a48..4d7bc64 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -980,6 +980,10 @@ unsigned long do_mmap_pgoff(struct file *file, unsigned long addr,
struct mm_struct * mm = current->mm;
struct inode *inode;
vm_flags_t vm_flags;
+ loff_t off = pgoff << PAGE_SHIFT;
+ loff_t maxbytes = -1;
+ if (file)
+ maxbytes = file->f_mapping->host->i_sb->s_maxbytes;
/*
* Does the application expect PROT_READ to imply PROT_EXEC?
@@ -1003,8 +1007,8 @@ unsigned long do_mmap_pgoff(struct file *file, unsigned long addr,
return -ENOMEM;
/* offset overflow? */
- if ((pgoff + (len >> PAGE_SHIFT)) < pgoff)
- return -EOVERFLOW;
+ if (off + len > maxbytes)
+ return -EOVERFLOW;
/* Too many mappings? */
if (mm->map_count > sysctl_max_map_count)
--
Thanks,
Wanlong Gao
>
--
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>
next prev parent reply other threads:[~2012-09-05 3:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 9:23 [PATCH] mm: fix mmap overflow checking Wanlong Gao
2012-09-04 9:23 ` Wanlong Gao
2012-09-04 20:59 ` Andrew Morton
2012-09-04 20:59 ` Andrew Morton
2012-09-05 3:20 ` Wanlong Gao [this message]
2012-09-05 20:41 ` Andrew Morton
2012-09-07 22:38 ` KOSAKI Motohiro
2012-09-07 22:38 ` KOSAKI Motohiro
2012-09-08 1:44 ` Wanlong Gao
2012-09-08 1:58 ` KOSAKI Motohiro
2012-09-08 1:58 ` KOSAKI Motohiro
2012-09-08 2:07 ` Wanlong Gao
2012-09-08 2:07 ` Wanlong Gao
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=5046C4E7.5040407@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=list@kvack.org \
--cc=open@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.