public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Leroy van Logchem <leroy.vanlogchem@wldelft.nl>
Cc: linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>,
	Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>
Subject: Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
Date: Wed, 14 Mar 2007 17:01:13 -0800	[thread overview]
Message-ID: <20070314170113.9c3c75c7.akpm@linux-foundation.org> (raw)
In-Reply-To: <loom.20070314T184515-284@post.gmane.org>

> On Wed, 14 Mar 2007 17:52:01 +0000 (UTC) Leroy van Logchem <leroy.vanlogchem@wldelft.nl> wrote:
> Leroy van Logchem <leroy.vanlogchem <at> wldelft.nl> writes:
> 
> > 
> > > > None whatsoever.  Three people are reporting this and it's a drop-dead
> > > > showstopper for a 2.6.21 release so we just have to wait until someone
> > > > wakes up and thinks about it.
> > 
> > The topic should be "when CONFIG_HIGHMEM64G=y" imo.
> > 
> > I'll try to do my first bi-sect today.

Thanks.   Please always do reply-to-all.  Cc's restored (and added..)

> Bisecting went well, after 13 compiles this commit was found:
> 
> a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit
> commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f
> Author: Roland McGrath <roland@redhat.com>
> Date:   Fri Jan 26 00:56:46 2007 -0800
> 
>     [PATCH] Fix CONFIG_COMPAT_VDSO
>     
>     I wouldn't mind if CONFIG_COMPAT_VDSO went away entirely.  But if it's there,
>     it should work properly.  Currently it's quite haphazard: both real vma and
>     fixmap are mapped, both are put in the two different AT_* slots, sysenter
>     returns to the vma address rather than the fixmap address, and core dumps yet
>     are another story.
>     
>     This patch makes CONFIG_COMPAT_VDSO disable the real vma and use the fixmap
>     area consistently.  This makes it actually compatible with what the old vdso
>     implementation did.
>     
>     Signed-off-by: Roland McGrath <roland@redhat.com>
>     Cc: Ingo Molnar <mingo@elte.hu>
>     Cc: Paul Mackerras <paulus@samba.org>
>     Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>     Cc: Andi Kleen <ak@suse.de>
>     Signed-off-by: Andrew Morton <akpm@osdl.org>
>     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> 
> :040000 040000 802ab3366a651ecba28c8677fa84a9f7c506392b
> f44adc4dcdab733e5965b68ccd0d643f0a550a80 M      arch
> :040000 040000 be1e217152d8b3fcd05f09aa2b3f4f9dcb8208aa
> 46cc86427e861350dd3fef9469474c55119f27ce M      include
> 
> I had both CONFIG_COMPAT_VDSO=y and CONFIG_HIGHMEM64G=y configured.
> Using a 4GB Supermicro 7044 SMP dual Xeon. Details upon request.
> 
> --
> Leroy
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2007-03-15  0:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703141013.l2EADP6c027144@fire-2.osdl.org>
2007-03-14 12:17 ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y Andrew Morton
2007-03-14 11:25   ` Randy.Dunlap
2007-03-14 11:30   ` Michal Piotrowski
2007-03-14 12:16     ` Leroy van Logchem
2007-03-14 17:52       ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad Leroy van Logchem
2007-03-15  1:01         ` Andrew Morton [this message]
2007-03-15  0:13           ` Andi Kleen
2007-03-15 14:12             ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad? Leroy van Logchem
2007-03-16  7:41               ` Nilshar
2007-03-15 15:31         ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad Chuck Ebbert
2007-03-15 15:49           ` Leroy van Logchem
2007-03-15 10:02       ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y Nilshar

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=20070314170113.9c3c75c7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ak@suse.de \
    --cc=leroy.vanlogchem@wldelft.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    /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