Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: rtm@csail.mit.edu, Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu, Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org
Subject: Re: futex(0x1ffffff81300000) on risc-v -> mm panic
Date: Wed, 18 Jun 2025 23:32:16 +0200	[thread overview]
Message-ID: <20250618212944.oFqYBNC3@linutronix.de> (raw)
In-Reply-To: <mhng-CC013FD5-8FF2-40EB-902C-AA0078E99AB4@palmerdabbelt-mac>

On Wed, Jun 18, 2025 at 12:58:44PM -0700, Palmer Dabbelt wrote:
> On Wed, 18 Jun 2025 06:25:59 PDT (-0700), namcao@linutronix.de wrote:
> > On Wed, Jun 18, 2025 at 07:10:28AM -0400, rtm@csail.mit.edu wrote:
> > > This program on risc-v:
> > > 
> > > main(){
> > >   futex((void*) 0x1ffffff81300000, FUTEX_WAIT, 0, 0, 0, 0);
> > > }
> > > 
> > > results in:
> > > 
> > > BUG: Bad page state in process a.out  pfn:81500
> > 
> > I cannot reproduce this issue. Can you please share your .config?
> 
> It's also not reproducing for me -- or even compiling for that matter, but I
> stuck one that compiles over at
> <https://github.com/palmer-dabbelt/palmer-tests/blob/main/rtm-futex.c> (I
> figured this was a good excuse to start piling up some tests).
> 
> > Also, your kernel seems to have some commits on top. Are you sure none of
> > those is the reason?
> 
> This is on my fixes branch right now, with defconfig + CONFIG_DEBUG_VM=y.
> So maybe it's one of these patches, or moybe it's some other configuration
> thing?

I can reproduce this with QEMU and Debian trixie. defconfig + DEBUG_VM=y is
enough. I have to "search for the address", as OP showed in the other
email, because 0x1ffffff81300000 doesn't trigger any issue for me.

I can also reproduce on 6.14 and 6.15, so not a recent regression.

I will look closer tomorrow.

Best regards,
Nam

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-06-18 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 11:10 futex(0x1ffffff81300000) on risc-v -> mm panic rtm
2025-06-18 13:25 ` Nam Cao
2025-06-18 18:27   ` rtm
2025-06-18 19:58   ` Palmer Dabbelt
2025-06-18 21:32     ` Nam Cao [this message]
2025-06-19 12:35 ` Alexandre Ghiti
2025-06-19 13:30   ` rtm
2025-06-19 16:02   ` Nam Cao

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=20250618212944.oFqYBNC3@linutronix.de \
    --to=namcao@linutronix.de \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rtm@csail.mit.edu \
    /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