public inbox for linux-alpha@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Magnus Lindholm <linmag7@gmail.com>,
	linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
	hch@infradead.org, macro@orcam.me.uk, mattst88@gmail.com,
	richard.henderson@linaro.org, ink@unseen.parts
Subject: Re: [PATCH 0/1] alpha: fix user-space corruption during memory compaction
Date: Tue, 20 Jan 2026 20:44:00 +1300	[thread overview]
Message-ID: <aW8yQMNTNEfxu6Fn@creeky> (raw)
In-Reply-To: <63b2087350d6990f0e348a8028f006924363c5d0.camel@physik.fu-berlin.de>

On Fri, Jan 02, 2026 at 06:57:28PM +0100, John Paul Adrian Glaubitz wrote:
> Hi Magnus,
> 
> On Fri, 2026-01-02 at 18:30 +0100, Magnus Lindholm wrote:
> > This patch fixes long-standing user-space crashes on Alpha systems
> > when memory compaction is enabled.
> > 
> > Observed symptoms include:
> >   - sporadic SIGSEGV in unrelated user programs
> >   - glibc allocator failures (e.g. "unaligned tcache chunk detected")
> >   - gcc "internal compiler error"
> >   - heap corruption detected by malloc consistency checks
> > 
> > The failures occur only when page migration / compaction is active
> > and disappear when compaction is disabled. They affect both UP and
> > SMP kernels and are not specific to a particular Alpha CPU model.
> 
> Wow, thanks for fixing this! This has been indeed a longstanding issue and
> seeing it fixed would be great.
> 
> I'm CC'ing Michael Cree who has been observing the issue as well and could
> help testing your series.

I've successfully run a 6.18.3 kernel with this patch and
CONFIG_COMPACTION on for almost four days on an XP1000 without
any problem. I would normally see one of the observed problems
described above within a day, and certainly within two days, when
running with a bad kernel, so this is looking good.

Feel free to add:

Tested-by: Michael Cree <mcree@orcon.net.nz>

Cheers,
Michael.

  reply	other threads:[~2026-01-20  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 17:30 [PATCH 0/1] alpha: fix user-space corruption during memory compaction Magnus Lindholm
2026-01-02 17:30 ` [PATCH 1/1] " Magnus Lindholm
2026-01-03 13:41   ` Ivan Kokshaysky
2026-01-10 23:50   ` matoro
2026-01-02 17:57 ` [PATCH 0/1] " John Paul Adrian Glaubitz
2026-01-20  7:44   ` Michael Cree [this message]
2026-01-20 22:44     ` Magnus Lindholm

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=aW8yQMNTNEfxu6Fn@creeky \
    --to=mcree@orcon.net.nz \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hch@infradead.org \
    --cc=ink@unseen.parts \
    --cc=linmag7@gmail.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=mattst88@gmail.com \
    --cc=richard.henderson@linaro.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