public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>, Bill Davidsen <davidsen@tmr.com>,
	linux-kernel@vger.kernel.org
Subject: Re: mmap() on cdrom files fails since 2.6.9-rc2-bk2
Date: Sun, 3 Oct 2004 14:11:40 +0200	[thread overview]
Message-ID: <20041003141140.319039de.khali@linux-fr.org> (raw)
In-Reply-To: <20041003111458.GA15390@elte.hu>

Hi Ingo,

> > old_mmap(NULL, 42, PROT_READ, MAP_SHARED, 3, 0) = -1 EPERM
> > (Operation not permitted)
> 
> could you try the patch below? mmap() done from !pt_gnu_stack binaries
> on noexec mounted filesystems indeed could fail due to the extra
> PROT_EXEC bit.

Indeed, all files on which mmap was failing were located on noexec'd
devices (although for the cdrom the noexec is not explicitely stated in
my /etc/fstab file). Your patch fixes my problem, mmap on these devices
is working again. Thanks!

Now I'm only curious as to why the problem only affected me. Since it
looks like noexec is implied on cdrom devices, the problem should have
affected everyone. Or are the "!pt_gnu_stack binaries" something rare? I
admit I have no idea what it refers to.

Thanks again.

-- 
Jean Delvare
http://khali.linux-fr.org/

  reply	other threads:[~2004-10-03 12:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2Jw9b-52b-13@gated-at.bofh.it>
2004-09-29 20:26 ` mmap() on cdrom files fails since 2.6.9-rc2-bk2 (Was: in -mmX) Jean Delvare
2004-10-02  1:44   ` Andrew Morton
2004-10-02  7:01     ` mmap() on cdrom files fails since 2.6.9-rc2-bk2 Jean Delvare
2004-10-03 11:14       ` Ingo Molnar
2004-10-03 12:11         ` Jean Delvare [this message]
2004-10-03 12:16           ` Ingo Molnar
2004-10-03 12:35             ` Jean Delvare
2004-10-03 12:41               ` Ingo Molnar
2004-10-04 15:09             ` Bill Davidsen

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=20041003141140.319039de.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=akpm@osdl.org \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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