From: Marcel Holtmann <marcel@holtmann.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Eugene Teo <eteo@redhat.com>
Subject: Re: Require mmap handler for a.out executables
Date: Thu, 27 Jul 2006 17:44:16 +0200 [thread overview]
Message-ID: <1154015056.9543.31.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0607270816500.4168@g5.osdl.org>
Hi Linus,
> > > diff --git a/fs/binfmt_aout.c b/fs/binfmt_aout.c
> > > index f312103..5638acf 100644
> > > --- a/fs/binfmt_aout.c
> > > +++ b/fs/binfmt_aout.c
> > > @@ -278,6 +278,9 @@ static int load_aout_binary(struct linux
> > > return -ENOEXEC;
> > > }
> > >
> > > + if (!bprm->file->f_op || !bprm->file->f_op->mmap)
> > > + return -ENOEXEC;
> > > +
> >
> > These checks need a big comment explanining why they are there, else people
> > will remove them again by accident.
>
> Since we fixed the /proc problem in a different way, I decided that it
> might be best to leave the a.out stuff alone, at least for now. It is
> conceivable that somebody actually might be using executables on some
> strange filesystem that doesn't support mmap, although I can't for the
> moment think of any good reason.
what do think about giving this a spin in -mm for some time and see if
it will break for somebody.
Andrew, please include it.
Regards
Marcel
next prev parent reply other threads:[~2006-07-27 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 10:31 Require mmap handler for a.out executables Marcel Holtmann
2006-07-27 15:07 ` Christoph Hellwig
2006-07-27 15:18 ` Linus Torvalds
2006-07-27 15:44 ` Marcel Holtmann [this message]
2006-07-27 17:21 ` Eugene Teo
[not found] <6COYh-8f0-41@gated-at.bofh.it>
2006-07-27 17:49 ` Bodo Eggert
2006-07-27 17:59 ` Eugene Teo
2006-07-27 18:25 ` Alan Cox
2006-07-27 21:18 ` Bodo Eggert
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=1154015056.9543.31.camel@localhost \
--to=marcel@holtmann.org \
--cc=akpm@osdl.org \
--cc=eteo@redhat.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox