From: Andi Kleen <ak@muc.de>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: ak@suse.de, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 072/198] x86_64: Use a VMA for the 32bit vsyscall
Date: 13 Apr 2005 20:20:19 +0200
Date: Wed, 13 Apr 2005 20:20:19 +0200 [thread overview]
Message-ID: <20050413182019.GA50241@muc.de> (raw)
In-Reply-To: <20050412170230.GD2758@granada.merseine.nu>
> > + /* MAYWRITE to allow gdb to COW and set breakpoints */
> > + vma->vm_flags = VM_READ|VM_EXEC|VM_MAYREAD|VM_MAYEXEC|VM_MAYEXEC|VM_MAYWRITE;
>
> Any reason for VM_MAYEXEC to be specified twice? did you mean something else?
No reason, must have been a typo. Anyways, it is correct, just redundant.
I will clean it up in a future patch. Thanks.
-Andi
prev parent reply other threads:[~2005-04-13 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 10:31 [patch 072/198] x86_64: Use a VMA for the 32bit vsyscall akpm
2005-04-12 17:02 ` Muli Ben-Yehuda
2005-04-13 18:20 ` Andi Kleen [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=20050413182019.GA50241@muc.de \
--to=ak@muc.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.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