From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
open@kvack.org,
"list@kvack.org:MEMORY MANAGEMENT" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: fix mmap overflow checking
Date: Sat, 08 Sep 2012 10:07:39 +0800 [thread overview]
Message-ID: <504AA86B.9040302@cn.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rPYAU6X2eXqyBxHV=PtguBceK=n_C89dTDbUk54-+6ww@mail.gmail.com>
On 09/08/2012 09:58 AM, KOSAKI Motohiro wrote:
>>> I've seen the exactly same patch from another fujitsu guys several
>>> month ago. and as I pointed
>>> out at that time, this line don't work when 32bit kernel + mmap2 syscall case.
>>>
>>> Please don't think do_mmap_pgoff() is for mmap(2) specific and read a
>>> past thread before resend
>>> a patch.
>>
>> So, what's your opinion about this bug? How to fix it in your mind?
>
> Fix glibc instead of kernel.
>
OK, I will send a patch to glibc community. Thank you.
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>
WARNING: multiple messages have this Message-ID (diff)
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
open@kvack.org,
"list@kvack.org:MEMORY MANAGEMENT" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: fix mmap overflow checking
Date: Sat, 08 Sep 2012 10:07:39 +0800 [thread overview]
Message-ID: <504AA86B.9040302@cn.fujitsu.com> (raw)
In-Reply-To: <CAHGf_=rPYAU6X2eXqyBxHV=PtguBceK=n_C89dTDbUk54-+6ww@mail.gmail.com>
On 09/08/2012 09:58 AM, KOSAKI Motohiro wrote:
>>> I've seen the exactly same patch from another fujitsu guys several
>>> month ago. and as I pointed
>>> out at that time, this line don't work when 32bit kernel + mmap2 syscall case.
>>>
>>> Please don't think do_mmap_pgoff() is for mmap(2) specific and read a
>>> past thread before resend
>>> a patch.
>>
>> So, what's your opinion about this bug? How to fix it in your mind?
>
> Fix glibc instead of kernel.
>
OK, I will send a patch to glibc community. Thank you.
Wanlong Gao
next prev parent reply other threads:[~2012-09-08 2:08 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
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 [this message]
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=504AA86B.9040302@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=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.