public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mv at binarysec dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2007] mmap seg faults on marginally improper arguments
Date: Sun, 25 Dec 2005 19:01:00 -0000	[thread overview]
Message-ID: <20051225190106.7059.qmail@sourceware.org> (raw)
In-Reply-To: <20051208233503.2007.bkorb@gnu.org>


------- Additional Comments From mv at binarysec dot com  2005-12-25 19:01 -------
I think you have a programming error.
You can't use MAP_ANON with MAP_PRIVATE or MAP_SHARED.
MAP_ANON, MAP_PRIVATE or MAP_SHARED *must* be used distinctly.

MAP_ANON : No file 
MAP_PRIVATE : Read sync
MAP_SHARED : Read sync + write sync (when you write datas in the mem map the kernel will sync asap 
the mem content into the file... You can force the write operation with sync()). 

When i see MAP_ANONYMOUS|MAP_FIXED|MAP_SHARED i say to me that you miss understanding the 
mmap() behavior (no offence).

And as Ulrich Drepper said mmap() is just a syscall wrapper so the return value is handled by kernel 
devels so you may ask the kernel ml.

I suggest to you to make this bug INVALID.

mv-

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2007

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2005-12-25 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 23:35 [Bug libc/2007] New: " bkorb at gnu dot org
2005-12-12 19:14 ` [Bug libc/2007] " decimal at us dot ibm dot com
2005-12-12 19:57 ` bkorb at gnu dot org
2005-12-23  4:31 ` drepper at redhat dot com
2005-12-24 16:32 ` bkorb at gnu dot org
2005-12-25 17:52   ` Michael Vergoz
2005-12-25 17:52 ` mv at binarysec dot com
2005-12-25 18:17 ` bkorb at gnu dot org
2005-12-25 19:01 ` mv at binarysec dot com [this message]
2005-12-27  1:21 ` bkorb at gnu dot org
2005-12-27 13:33 ` mv at binarysec dot com
2005-12-30  9:36 ` aj at suse dot de
2006-01-27 14:23 ` bkorb at gnu dot org
2006-02-03 21:58 ` drepper at redhat dot com

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=20051225190106.7059.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).