From: Muli Ben-Yehuda <mulix@mulix.org>
To: Andi Kleen <ak@muc.de>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
bos@serpentine.com
Subject: Re: [PATCH] Fix mlockall for PROT_NONE mappings
Date: Thu, 9 Oct 2003 12:49:18 +0200 [thread overview]
Message-ID: <20031009104918.GB4699@actcom.co.il> (raw)
In-Reply-To: <20031009104218.GA1935@averell>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Thu, Oct 09, 2003 at 12:42:18PM +0200, Andi Kleen wrote:
> I added a new argument force==2 to get_user_pages that means to ignore
> SIGBUS or unaccessible pages errors. MAY_* is still checked for like
> with the old force ==1, it just doesn't error out now for SIGBUS
> errors on handle_mm_fault.
How about making it an enum or define for code readability? I'd much
rather see an IGNORE_BAD_PAGES or some such than a cryptic '2' in the
code. I can send a patch to that effect if you'd like?
Cheers,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-09 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 10:42 [PATCH] Fix mlockall for PROT_NONE mappings Andi Kleen
2003-10-09 10:49 ` Muli Ben-Yehuda [this message]
2003-10-09 11:22 ` Andi Kleen
2003-10-09 11:24 ` Muli Ben-Yehuda
2003-10-09 11:31 ` Andi Kleen
2003-10-09 14:44 ` Linus Torvalds
2003-10-09 14:52 ` Andi Kleen
2003-10-09 14:56 ` Linus Torvalds
2003-10-09 15:12 ` Andi Kleen
2003-10-09 15:17 ` Linus Torvalds
2003-10-09 15:33 ` Andi Kleen
2003-10-09 15:40 ` Linus Torvalds
2003-10-09 16:34 ` Andi Kleen
2003-10-09 17:28 ` Linus Torvalds
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=20031009104918.GB4699@actcom.co.il \
--to=mulix@mulix.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bos@serpentine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.