From: Rock Gordon <rockgordon@yahoo.com>
To: Terje Eggestad <terje.eggestad@scali.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Executing binaries on new filesystem
Date: Mon, 19 Nov 2001 08:34:55 -0800 (PST) [thread overview]
Message-ID: <20011119163455.11507.qmail@web14804.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0111181602220.1899-100000@elin.scali.no>
All said and done, the file is with correct
permissions (for that matter any binary that I execute
on my filesystem has correct permissions). The only
thing strace tells me is "bad file format". The same
binary works perfectly elsewhere.
I don't think mmap is the problem; you don't need it
in order to run binaries ...
--- Terje Eggestad <terje.eggestad@scali.no> wrote:
> On Sat, 17 Nov 2001, Rock Gordon wrote:
>
> > Hi,
> >
> > I've written a modest filesystem for fun, it works
> > pretty ok, but when I try to execute binaries from
> it,
> > bash says "cannot execute binary file" ... If I
> copy
> > the same binary elsewhere, it executes perfectly.
> >
> > Does anybody have any clue ?
>
> Yes
>
> keep in mind taht the kernel do demand paging of the
> text (code) in our
> executable, meaning that a page of code is not
> loaded into the procs
> memory spce (and thus phys mem) until the proc
> actually tries to exec the
> code page. This is one manifestation of the funny
> term "page fault"!
>
> I do belive that the current kernel uses mmap to map
> in the exec file text
> segment. (Even if I can hear the ice cracking under
> my feet, never
> actually looked at the code handling execs) but if
> you strace anexec that
> uses shared libs you'll note that the sh.libs are
> mmaped into the process
> space. (also note the MMAP_EXEC flag in the mmap(2)
> man page).
>
>
> TJ
>
> >
> > Regards,
> > Rock
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Find the one for you at Yahoo! Personals
> > http://personals.yahoo.com
> > -
> > To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> --
>
_________________________________________________________________________
>
> Terje Eggestad
> terje.eggestad@scali.no
> Scali Scalable Linux Systems http://www.scali.com
>
> Olaf Helsets Vei 6 tel: +47 22 62 89
> 61 (OFFICE)
> P.O.Box 70 Bogerud +47 975 31
> 574 (MOBILE)
> N-0621 Oslo fax: +47 22 62 89
> 51
> NORWAY
>
_________________________________________________________________________
>
__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
next prev parent reply other threads:[~2001-11-19 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-17 22:18 Rock Gordon
2001-11-17 22:24 ` Mike Fedyk
2001-11-18 0:08 ` Eric W. Biederman
2001-11-18 0:54 ` Jeff Dike
2001-11-18 15:13 ` Terje Eggestad
2001-11-19 16:34 ` Rock Gordon [this message]
2001-11-19 23:45 ` Ryan Cumming
2001-11-20 3:39 ` Eric W. Biederman
2001-11-20 9:34 ` Terje Eggestad
2001-11-28 1:43 ` Rock Gordon
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=20011119163455.11507.qmail@web14804.mail.yahoo.com \
--to=rockgordon@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terje.eggestad@scali.no \
/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
all inboxes | Powered by JetHome®