linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	John Williams <john.williams@petalogix.com>
Subject: Re: Split 'flush_old_exec' into two functions - 221af7f87b97431e3ee21ce4b0e77d5411cf1549
Date: Tue, 02 Feb 2010 11:14:43 +0100	[thread overview]
Message-ID: <4B67FB13.9000005@petalogix.com> (raw)
In-Reply-To: <4B672C31.9070302@zytor.com>

H. Peter Anvin wrote:
> On 02/01/2010 07:57 AM, Linus Torvalds wrote:
>> That said, Microblaze is not one of the architectures I would have 
>> expected to have problems. It has one of the most straightforward 
>> "flush_thread()" implementations in the whole kernel (it's a no-op ;), and 
>> that's where most of the hacky things were for the architectures that 
>> needed the change. And it has no "arch_pick_mmap_layout()" issues or 
>> anything else that tends to depend on personality bits or whatever.
>>
>> Microblaze is a no-MMU platform, isn't it? Which binary format does it 
>> use? It looks like _some_ binaries work (it seems to happily be running a 
>> shell to actually do those startup scripts) while others have problems. Is 
>> there a difference between "/bin/sh" and the binaries that seem to be 
>> problematic (like /bin/mount and /bin/ifup).
>>
>> Are the failing binaries all setuid ones, for example? Or shared vs 
>> non-shared? Or ELF vs FLAT or whatever?
>>
> 
> Another thing... it looks like you [Michal] is running a test image
> under Qemu... could you perhaps point us to that image or another test
> image which reproduces the problem?

Yes, you are right. I am doing every day testing on qemu.
I have prepared package which contain all things which you need.
Please download it from http://www.monstr.eu/20100202-flush.tar.gz
md5sum cfe59b19e52dff2319a2b1919839d5cd  20100202-flush.tar.gz

I added there README where you will find more information. Also there is 
rootfs.cpio which you can use. Compile kernel with this patch and try. 
Then you can revert it and retest - you should be able to see that behavior.

If you have any problem with it, please let me know.

Michal

P.S.: you don't need to care about FPU error in bootlog - fpu is not used.

> 
> Nothing like having a hands-on testcase...
> 
> 	-hpa
> 


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663

  reply	other threads:[~2010-02-02 10:16 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
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 [this message]
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=4B67FB13.9000005@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=hpa@zytor.com \
    --cc=john.williams@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).