linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Simek <michal.simek@petalogix.com>,
	LKML <linux-kernel@vger.kernel.org>,
	hpa@zytor.com, John Williams <john.williams@petalogix.com>
Subject: Re: Split 'flush_old_exec' into two functions - 221af7f87b97431e3ee21ce4b0e77d5411cf1549
Date: Mon, 01 Feb 2010 12:07:33 -0600	[thread overview]
Message-ID: <4B671865.5030705@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1002010741560.4206@localhost.localdomain>

Linus Torvalds wrote:
> On Mon, 1 Feb 2010, Michal Simek wrote:
>   
>> Hi Peter and Linus,
>>
>> commit 221af7f87b97431e3ee21ce4b0e77d5411cf1549 breaks anything on Microblaze.
>>     
>
> Are the failing binaries all setuid ones, for example? Or shared vs 
> non-shared? Or ELF vs FLAT or whatever?
>   

Add to the afflicted architecture list a ppc64 kernel running 32 bit
user space apps such as a dynamically linked busybox:

file bin/busybox

ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV),
dynamically linked (uses shared libs), stripped


All that is reported on boot is:

[clip]
VFS: Mounted root (nfs filesystem) readonly on device 0:13.
Freeing unused kernel memory: 264k freed
/sbin/init: error while loading shared libraries: out of memory: Cannot
allocate memory
Kernel panic - not syncing: Attempted to kill init!
Rebooting in 180 seconds..QEMU: Terminated


Reverting the patch solves the problem.

Jason.

  reply	other threads:[~2010-02-01 18:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 14:00 Split 'flush_old_exec' into two functions - 221af7f87b97431e3ee21ce4b0e77d5411cf1549 Michal Simek
2010-02-01 15:57 ` Linus Torvalds
2010-02-01 18:07   ` Jason Wessel [this message]
2010-02-01 18:41     ` H. Peter Anvin
2010-02-01 18:41     ` Linus Torvalds
2010-02-01 18:56       ` Jason Wessel
2010-02-01 19:32   ` H. Peter Anvin
2010-02-02 10:14     ` Michal Simek
2010-02-02 10:16   ` Michal Simek
2010-02-02 15:50     ` Linus Torvalds
2010-02-02 19:52       ` Michal Simek
2010-02-02 21:45       ` H. Peter Anvin

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=4B671865.5030705@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=hpa@zytor.com \
    --cc=john.williams@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@petalogix.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).