Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH v3] svcrdma: Introduce Receive buffer arenas
Date: Fri, 12 Sep 2025 09:46:16 -0400	[thread overview]
Message-ID: <52be6bdc-81cb-441d-8266-9fb5bb5b4b23@kernel.org> (raw)
In-Reply-To: <CAN-5tyHxtn=KjR-A3jDU-3Y2B8w2S2pqus7McerCZVpaEG4hcA@mail.gmail.com>

On 9/11/25 5:33 PM, Olga Kornievskaia wrote:
> When I have this patch it causes the following panic just from doing
> "systemctl start nfs-server" followed by
> "systemctl stop nfs-server"
> 
> [   69.705986] Unable to handle kernel paging request at virtual
> address dfff800000000001
> [   69.706706] KASAN: null-ptr-deref in range
> [0x0000000000000008-0x000000000000000f]
> [   69.707299] Mem abort info:
> [   69.707514]   ESR = 0x0000000096000005
> [   69.707787]   EC = 0x25: DABT (current EL), IL = 32 bits
> [   69.708186]   SET = 0, FnV = 0
> [   69.708415]   EA = 0, S1PTW = 0
> [   69.708637]   FSC = 0x05: level 1 translation fault
> [   69.708986] Data abort info:
> [   69.709203]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
> [   69.709604]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
> [   69.709986]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
> [   69.710345] [dfff800000000001] address between user and kernel address ranges
> [   69.710842] Internal error: Oops: 0000000096000005 [#1]  SMP

Yep, I've hit this. I'm dropping the patch from nfsd-testing until
the issue is addressed. Thanks for the report.


-- 
Chuck Lever

      reply	other threads:[~2025-09-12 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 15:22 [RFC PATCH v3] svcrdma: Introduce Receive buffer arenas Chuck Lever
2025-09-11 21:33 ` Olga Kornievskaia
2025-09-12 13:46   ` Chuck Lever [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=52be6bdc-81cb-441d-8266-9fb5bb5b4b23@kernel.org \
    --to=cel@kernel.org \
    --cc=aglo@umich.edu \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@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