linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Erley <pat-lkml@erley.org>
To: linux-next@vger.kernel.org
Cc: richard@nod.at
Subject: Possible regression from "fs/exec.c: call arch_pick_mmap_layout() only once"
Date: Thu, 02 Jan 2014 15:41:27 -0600	[thread overview]
Message-ID: <52C5DD07.40208@erley.org> (raw)

On my 64bit kernel, commit 283fe963095b38a6ab75dda1436ee66b9e45c7c2 
seems to have broken 32bit compatibility.  I've run the bisection twice, 
and verified that reverting this on HEAD fixes the problem.  I've 
uploaded my .config to pastebin at http://pastebin.com/kVcr9H65

Even this simple program:

main(){puts("HELLO");}

compiled with:

gcc -m32 test.c

Will crash with a segfault.  Stracing shows that it's failing to 
allocate memory.

Pat Erley

             reply	other threads:[~2014-01-02 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 21:41 Pat Erley [this message]
2014-01-02 22:24 ` Possible regression from "fs/exec.c: call arch_pick_mmap_layout() only once" Richard Weinberger
2014-01-02 22:39   ` Pat Erley
2014-01-03  4:35     ` Pat Erley

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=52C5DD07.40208@erley.org \
    --to=pat-lkml@erley.org \
    --cc=linux-next@vger.kernel.org \
    --cc=richard@nod.at \
    /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).