From: Bagas Sanjaya <bagasdotme@gmail.com>
To: matoro <matoro_mailinglist_kernel@matoro.tk>,
Linux PA-RISC Mailing List <linux-parisc@vger.kernel.org>,
Helge Deller <deller@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam James <sam@gentoo.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Regressions <regressions@lists.linux.dev>
Cc: "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jens Axboe <axboe@kernel.dk>,
John David Anglin <dave@parisc-linux.org>
Subject: Re: Bisected stability regression in 6.6
Date: Sat, 11 Nov 2023 14:02:49 +0700 [thread overview]
Message-ID: <ZU8nGV4sg-l9-pkf@archie.me> (raw)
In-Reply-To: <75318812c588816e0c741b4cd094524f@matoro.tk>
[-- Attachment #1: Type: text/plain, Size: 2560 bytes --]
On Sat, Nov 11, 2023 at 01:31:01AM -0500, matoro wrote:
> Hi Helge, I have bisected a regression in 6.6 which is causing userspace
> segfaults at a significantly increased rate in kernel 6.6. There seems to
> be a pathological case triggered by the ninja build tool. The test case I
> have been using is cmake with ninja backend to attempt to build the nghttp2
> package. In 6.6, this segfaults, not at the same location every time, but
> with enough reliability that I was able to use it as a bisection regression
> case, including immediately after a reboot. In the kernel log, these show
> up as "trap #15: Data TLB miss fault" messages. Now these messages can and
> do show up in 6.5 causing segfaults, but never immediately after a reboot
> and infrequently enough that the system is stable. With kernel 6.6 I am
> completely unable to build nghttp2 under any circumstances.
>
> I have bisected this down to the following commit:
>
> $ git bisect good
> 3033cd4307681c60db6d08f398a64484b36e0b0f is the first bad commit
> commit 3033cd4307681c60db6d08f398a64484b36e0b0f
> Author: Helge Deller <deller@gmx.de>
> Date: Sat Aug 19 00:53:28 2023 +0200
>
> parisc: Use generic mmap top-down layout and brk randomization
>
> parisc uses a top-down layout by default that exactly fits the generic
> functions, so get rid of arch specific code and use the generic version
> by selecting ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT.
>
> Note that on parisc the stack always grows up and a "unlimited stack"
> simply means that the value as defined in
> CONFIG_STACK_MAX_DEFAULT_SIZE_MB
> should be used. So RLIM_INFINITY is not an indicator to use the legacy
> memory layout.
>
> Signed-off-by: Helge Deller <deller@gmx.de>
>
> arch/parisc/Kconfig | 17 +++++++++++++
> arch/parisc/kernel/process.c | 14 -----------
> arch/parisc/kernel/sys_parisc.c | 54
> +----------------------------------------
> mm/util.c | 5 +++-
> 4 files changed, 22 insertions(+), 68 deletions(-)
>
> I have tried applying ad4aa06e1d92b06ed56c7240252927bd60632efe ("parisc: Add
> nop instructions after TLB inserts") on top of 6.6, but it does NOT fix the
> issue.
>
> Let me know if there is anything I can answer on this. I can provide full
> remote access with BMC if it would help.
Thanks for the regression report. I'm adding it to regzbot:
#regzbot ^introduced: 3033cd4307681c
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-11 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 6:31 Bisected stability regression in 6.6 matoro
2023-11-11 7:02 ` Bagas Sanjaya [this message]
2023-11-22 9:07 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-11 21:21 ` Helge Deller
2023-11-11 21:27 ` Sam James
2023-11-11 23:33 ` matoro
2023-11-12 1:22 ` Dr. David Alan Gilbert
2023-11-12 8:03 ` Helge Deller
2023-11-12 12:07 ` Dr. David Alan Gilbert
2023-11-12 20:22 ` Helge Deller
2023-11-12 23:37 ` matoro
2023-11-11 21:28 ` matoro
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=ZU8nGV4sg-l9-pkf@archie.me \
--to=bagasdotme@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dave@parisc-linux.org \
--cc=deller@gmx.de \
--cc=gautham.shenoy@amd.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=regressions@lists.linux.dev \
--cc=sam@gentoo.org \
--cc=tglx@linutronix.de \
/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).