sparclinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Christoph Hellwig <hch@lst.de>, Frank Scheiner <frank.scheiner@web.de>
Cc: Jan Engelhardt <jengelh@inai.de>,
	Sparc kernel list <sparclinux@vger.kernel.org>,
	debian-sparc <debian-sparc@lists.debian.org>
Subject: Re: Regression in 028abd92 for Sun UltraSPARC T1
Date: Tue, 02 Sep 2025 22:18:07 +0200	[thread overview]
Message-ID: <e705404a9f66e0cffc0c474b565b2755d8d560c2.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20210325075036.GA27022@lst.de>

Hi Christoph,

On Thu, 2021-03-25 at 08:50 +0100, Christoph Hellwig wrote:
> I have to admit I'm completely lost at this point.  This new trace looks
> totally strange to me, and I'm pretty sure whatever symptoms you see are
> due to different alignments / code sections etc just triggered by the
> removal, we need help from the real sparc experts.

This has finally been tracked down to a regression in the copy_{to,from}_user
code on SPARC as it's found in arch/sparc/lib. Patches to fix these issues
have already been posted in [1].

I'm waiting for Frank to test the patches on his SPARC T1 which is the only
SPARC sub-arch we don't have test results for yet.

Adrian

> [1] https://lore.kernel.org/all/20250826160312.2070-1-kernel@mkarcher.dialup.fu-berlin.de/

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

      reply	other threads:[~2025-09-02 20:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 21:30 Regression in 028abd92 for Sun UltraSPARC T1 Frank Scheiner
2021-03-22 21:48 ` John Paul Adrian Glaubitz
2021-03-22 21:55   ` Frank Scheiner
2021-03-23 16:50     ` Jan Engelhardt
2021-03-23 16:57       ` Christoph Hellwig
2021-03-23 17:39         ` Frank Scheiner
2021-03-23 22:17         ` Frank Scheiner
2021-03-24  8:28           ` Christoph Hellwig
2021-03-24 12:30             ` Frank Scheiner
2021-03-24 12:42               ` Anatoly Pugachev
2021-03-24 12:48                 ` Frank Scheiner
2021-03-24 12:49               ` John Paul Adrian Glaubitz
2021-03-24 13:09             ` Frank Scheiner
2021-03-24 13:16               ` John Paul Adrian Glaubitz
2021-03-24 13:19                 ` Frank Scheiner
2021-03-24 13:24                   ` Anatoly Pugachev
2021-03-24 13:29                     ` Frank Scheiner
2021-03-24 13:57             ` Frank Scheiner
2021-03-24 15:22               ` Jan Engelhardt
2021-03-24 15:58                 ` Frank Scheiner
2021-03-24 16:10                   ` Christoph Hellwig
2021-03-24 16:33                     ` Frank Scheiner
2021-03-24 16:37                       ` Frank Scheiner
2021-03-25  7:50                         ` Christoph Hellwig
2025-09-02 20:18                           ` John Paul Adrian Glaubitz [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=e705404a9f66e0cffc0c474b565b2755d8d560c2.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=debian-sparc@lists.debian.org \
    --cc=frank.scheiner@web.de \
    --cc=hch@lst.de \
    --cc=jengelh@inai.de \
    --cc=sparclinux@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).