linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: Michael Cree <mcree@orcon.net.nz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Alpha: rare random memory corruption/segfault in user space bisected
Date: Sat,  7 May 2022 09:56:46 +0800	[thread overview]
Message-ID: <20220507015646.5377-1-hdanton@sina.com> (raw)
In-Reply-To: <YnWRVd5slCy5H0fC@creeky>

On Sat, 7 May 2022 09:21:25 +1200 Michael Cree wrote:
> Alpha kernel has been exhibiting rare and random memory
> corruptions/segaults in user space since the 5.9.y kernel.  First seen
> on the Debian Ports build daemon when running 5.10.y kernel resulting
> in the occasional (one or two a day) build failures with gcc ICEs either
> due to self detected corrupt memory structures or segfaults.  Have been
> running 5.8.y kernel without such problems for over six months.
> 
> Tried bisecting last year but went off track with incorrect good/bad
> determinations due to rare nature of bug.  After trying a 5.16.y kernel
> early this year and seen the bug is still present retried the bisection
> and have got to:
> 
> aae466b0052e1888edd1d7f473d4310d64936196 is the first bad commit
> commit aae466b0052e1888edd1d7f473d4310d64936196
> Author: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Date:   Tue Aug 11 18:30:50 2020 -0700
> 
>     mm/swap: implement workingset detection for anonymous LRU
> 
> 
> Pretty confident this is the bad commit as the kernel built to the parent
> commit (3852f6768ede54...) has not failed in four days running. Always have
> seen the failure within one day of running in past.

See if the fix to the syzbot bisection [1] is not a cure to your issue.

[1] https://lore.kernel.org/lkml/000000000000625fa705dd1802e3@google.com/


       reply	other threads:[~2022-05-07  1:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YnWRVd5slCy5H0fC@creeky>
2022-05-07  1:56 ` Hillf Danton [this message]
2022-05-07 18:27   ` Yu Zhao
2022-05-11 20:36     ` Michael Cree
2022-05-23 20:56       ` Yu Zhao
2022-05-30  8:25         ` Michael Cree
2022-06-08  0:20           ` Yu Zhao

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=20220507015646.5377-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcree@orcon.net.nz \
    /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