From: Paul Mundt <lethal@linux-sh.org>
To: graff.yang@gmail.com
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org,
uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH] mm/nommu.c: check read permission in validate_mmap_request()
Date: Fri, 14 Aug 2009 13:57:34 +0900 [thread overview]
Message-ID: <20090814045734.GB9570@linux-sh.org> (raw)
In-Reply-To: <1250219961-11681-1-git-send-email-graff.yang@gmail.com>
On Fri, Aug 14, 2009 at 11:19:21AM +0800, graff.yang@gmail.com wrote:
> From: Graff Yang <graff.yang@gmail.com>
>
> According to the POSIX (1003.1-2008), the file shall have been opened
> with read permission, regardless of the protection options specified.
> The ltp test cases mmap06/07 need this.
>
> Signed-off-by: Graff Yang <graff.yang@gmail.com>
Looks good. This brings it more in line with MMU Linux anyways, so it's
worthwhile regardless.
Acked-by: Paul Mundt <lethal@linux-sh.org>
prev parent reply other threads:[~2009-08-14 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 3:19 [PATCH] mm/nommu.c: check read permission in validate_mmap_request() graff.yang
2009-08-14 4:57 ` Paul Mundt [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=20090814045734.GB9570@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=graff.yang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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