linux-kernel - Re: PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y+z4XlhDzokAMTI1@x1n>
Date:   Wed, 15 Feb 2023 10:21:02 -0500
From:   Peter Xu <peterx@...hat.com>
To:     Linux regressions mailing list <regressions@...ts.linux.dev>
Cc:     Nick Bowler <nbowler@...conx.ca>, linux-kernel@...r.kernel.org,
        sparclinux@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: PROBLEM: sparc64 random crashes starting w/ Linux 6.1
 (regression)

On Wed, Feb 15, 2023 at 03:49:56PM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 31.01.23 02:46, Nick Bowler wrote:
> > On 2023-01-29, Peter Xu <peterx@...hat.com> wrote:
> >> On Sat, Jan 28, 2023 at 09:17:31PM -0500, Nick Bowler wrote:
> >>> Starting with Linux 6.1.y, my sparc64 (Sun Ultra 60) system is very
> >>> unstable, with userspace processes randomly crashing with all kinds of
> >>> different weird errors.  The same problem occurs on 6.2-rc5.  Linux
> >>> 6.0.y is OK.
> > [...]
> >> Could you try below patch to see whether it fixes your problem?  It should
> >> cover the last piece of possible issue with dirty bit on sparc after that
> >> patchset.  It's based on latest master branch (commit ab072681eabe1ce0).
> > 
> > Haven't seen any failures yet, so it seems this patch on top of 6.2-rc6
> > makes things much better.
> > 
> > I'll keep running this for a while to see if any other problems come up.
> 
> Nick, I assume no other problems showed up?
> 
> In that case Peter could send the patch in for merging. Or did you do
> that already?

Thanks for raising this again.  Nop, I'm just waiting for a final ack from
Nick to make sure that nothing went wrong after the longer run.

-- 
Peter Xu