public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Sembera <jsembera@suse.cz>,
	linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
	ink@jurassic.park.msu.ru, stable@kernel.org,
	linux-ia64@vger.kernel.org, "Luck, Tony" <tony.luck@intel.com>
Subject: Re: [PATCH] binfmt_misc: Fix binfmt_misc priority
Date: Mon, 13 Sep 2010 17:47:21 -0400	[thread overview]
Message-ID: <20100913174721.5fb57678@katamari> (raw)
In-Reply-To: <20100903142003.b6f02a0c.akpm@linux-foundation.org>

On Fri, 3 Sep 2010 14:20:03 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Mon, 23 Aug 2010 16:15:20 +0200
> Jan Sembera <jsembera@suse.cz> wrote:
> 
> > Commit 74641f584da introduced a regression - binfmt_misc is now consulted
> > after binfmt_elf, which will unfortunately break ia32el. ia32 ELF binaries
> > on ia64 used to be matched using binfmt_misc and executed using wrapper. As
> > 32bit binaries are now matched by binfmt_elf before bindmt_misc kicks in,
> > the wrapper is ignored.

> Yikes, 74641f584da was merged in May 2009.  I wonder why this problem
> wasn't noticed before now?

I posted about this on Sep 15, 2009:

http://marc.info/?l=linux-kernel&m=125298891709482&w=4
"binfmt_misc takes precedence over binfmt_script in 2.6.30"

I also copied the author of the original patch, but there was no reply.

  parent reply	other threads:[~2010-09-13 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 14:15 [PATCH] binfmt_misc: Fix binfmt_misc priority Jan Sembera
2010-09-03 21:20 ` Andrew Morton
2010-09-07 10:16   ` Jan Sembera
2010-09-13 21:47   ` Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-27  9:14 Jan Sembera

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=20100913174721.5fb57678@katamari \
    --to=cebbert@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jsembera@suse.cz \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=viro@zeniv.linux.org.uk \
    /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