All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Ingo Molnar <mingo@kernel.org>,
	arnd@arndb.de, akpm@linux-foundation.org, luto@kernel.org,
	dave.hansen@linux.intel.com, jroedel@suse.de,
	keescook@chromium.org, torvalds@linux-foundation.org,
	toshi.kani@hpe.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
	sfr@canb.auug.org.au, kernel list <linux-kernel@vger.kernel.org>,
	mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org
Subject: Re: Avoid VLA in pgd_alloc kills boot on 32-bit machines was Re: -next20181010,1011 regression: thinkpad x60 (32 bit) dies during boot.
Date: Fri, 12 Oct 2018 20:22:33 +0200	[thread overview]
Message-ID: <20181012182233.GB9098@amd> (raw)
In-Reply-To: <20181012181011.GA9098@amd>


[-- Attachment #1.1: Type: text/plain, Size: 3382 bytes --]

On Fri 2018-10-12 20:10:11, Pavel Machek wrote:
> Hi!
> 
> > > > So what came in between -next20181005 and the first bad one? kernel/sched/*
> > > > being the first place to look at.
> > > 
> > > kernel/sched does not seem to contain anything too scary.
> > > 
> > > I know that -next20181005 works ok, and I know -next20181010 is
> > > bad. Is there easy way to bisect using that information? I can do
> > > bisect between -next and mainline, but that's a lot of patches and
> > > thus not much fun :-(.
> > > 
> > > In the meantime, I reproduced the failure with T40p. Is there someone
> > > with working x86-32 in -next?
> > 
> > Does latest -tip fail too? If yes then I suspect bisection would be needed.
> 
> And the winner is...
> 
> [1be3f247c2882a82279cbcf43717581ea943b692] x86/mm: Avoid VLA in
> pgd_alloc()
> 
> "Kernel stack is corrupted in: pgd_alloc" panic kind of suggests this
> is right commit.

git bisect log, for the reference... and ~ my config.

									Pavel

# bad: [771b65e89c8a51d611b8049718693a4202e4f732] Add linux-next specific files for 20181011
# good: [7876320f88802b22d4e2daf7eb027dd14175a0f8] Linux 4.19-rc4
git bisect start '771b65e89c8a51d611b8049718693a4202e4f732' '7876320f88802b22d4e2daf7eb027dd14175a0f8'
# good: [43faff25da004eabce691268da34065b3690f5ca] Merge remote-tracking branch 'net-next/master'
git bisect good 43faff25da004eabce691268da34065b3690f5ca
# good: [3e2beb7db82a880319aa2f0dcafa820f3f5206d3] Merge remote-tracking branch 'spi/for-next'
git bisect good 3e2beb7db82a880319aa2f0dcafa820f3f5206d3
# bad: [74411e5fd30ae540491c4d6142af6ee6b2b22f09] Merge remote-tracking branch 'char-misc/char-misc-next'
git bisect bad 74411e5fd30ae540491c4d6142af6ee6b2b22f09
# bad: [c810d907775aa2aa753e836a122613fd2416b14d] Merge remote-tracking branch 'kvm/linux-next'
git bisect bad c810d907775aa2aa753e836a122613fd2416b14d
# good: [fac07d2ba7b2764e3002ff9bc7861742a84a2ef6] Merge branch 'perf/core'
git bisect good fac07d2ba7b2764e3002ff9bc7861742a84a2ef6
# bad: [d74865bd3996c7a6f3e8ce6e626c1fe474e39494] Merge branch 'x86/mm'
git bisect bad d74865bd3996c7a6f3e8ce6e626c1fe474e39494
# good: [dcd2d0cece1608b2be9184786c900807ec947076] Merge branch 'x86/asm'
git bisect good dcd2d0cece1608b2be9184786c900807ec947076
# bad: [ae9260d80e517c8702b91b8e00d117e1e2834c33] Merge branch 'x86/cache'
git bisect bad ae9260d80e517c8702b91b8e00d117e1e2834c33
# good: [d5a581d84ae6b8a4a740464b80d8d9cf1e7947b2] x86/cpufeature: Macrofy inline assembly code to work around GCC inlining bugs
git bisect good d5a581d84ae6b8a4a740464b80d8d9cf1e7947b2
# good: [245e5707dd7df01428459d97a9121f14a57dac6b] Merge branch 'x86/build'
git bisect good 245e5707dd7df01428459d97a9121f14a57dac6b
# bad: [7d27cb68cc307ee103e116d357e9baca35151c55] Merge branch 'x86/urgent' into x86/cache
git bisect bad 7d27cb68cc307ee103e116d357e9baca35151c55
# good: [2cc81c6992248ea37d0241bc325977bab310bc3b] x86/intel_rdt: Show missing resctrl mount options
git bisect good 2cc81c6992248ea37d0241bc325977bab310bc3b
# bad: [e8bd1803aec89dfce5758d88022963fe3248bc4c] x86/intel_rdt: Fix out-of-bounds memory access in CBM tests
git bisect bad e8bd1803aec89dfce5758d88022963fe3248bc4c


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: config.gz --]
[-- Type: application/gzip, Size: 27906 bytes --]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2018-10-12 18:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 19:59 -next20181010 regression: thinkpad x60 (32 bit) dies during boot Pavel Machek
2018-10-10 20:03 ` Pavel Machek
2018-10-11 18:03   ` -next20181010,1011 " Pavel Machek
2018-10-11 20:09     ` Thomas Gleixner
2018-10-12 10:24       ` Pavel Machek
2018-10-12 10:52         ` Ingo Molnar
2018-10-12 12:35           ` Pavel Machek
2018-10-12 18:10           ` Avoid VLA in pgd_alloc kills boot on 32-bit machines was " Pavel Machek
2018-10-12 18:13             ` Borislav Petkov
2018-10-12 18:57               ` Pavel Machek
2018-10-12 18:22             ` Pavel Machek [this message]

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=20181012182233.GB9098@amd \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jroedel@suse.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=toshi.kani@hpe.com \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.