From: Chen Chen via Bugspray Bot <bugbot@kernel.org>
To: jlayton@kernel.org, cel@kernel.org, linux-nfs@vger.kernel.org,
anna@kernel.org, trondmy@kernel.org
Subject: Re: Possible memory leak on nfsd
Date: Sat, 07 Dec 2024 08:35:12 +0000 [thread overview]
Message-ID: <20241207-b219535c8-544381616c66@bugzilla.kernel.org> (raw)
In-Reply-To: <20241127-b219535c0-4d5445e74947@bugzilla.kernel.org>
Chen Chen added an attachment on Kernel.org Bugzilla:
Created attachment 307330
dmesg of another 3 crashes
Since reporting I got another 3 crashes. All killed by nfsd.
First one:
[136965.765431] Out of memory and no killable processes...
[136965.765433] Kernel panic - not syncing: System is deadlocked on memory
[136965.766148] CPU: 2 PID: 1856 Comm: nfsd Kdump: loaded Tainted: G E 6.1.119-1.el9.elrepo.x86_64 #1
[136965.766852] Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 2.22.2 09/12/2024
[136965.767546] Call Trace:
[136965.768230] <TASK>
[136965.768903] dump_stack_lvl+0x45/0x5e
[136965.769571] panic+0x10c/0x2c2
[136965.770231] out_of_memory.cold+0x2f/0x7e
[136965.770874] __alloc_pages_slowpath.constprop.0+0x707/0x9d0
[136965.771518] __alloc_pages+0x35d/0x370
[136965.772147] __alloc_pages_bulk+0x3e5/0x680
[136965.772766] svc_alloc_arg+0x81/0x1f0 [sunrpc]
[136965.773431] svc_recv+0x1f/0x190 [sunrpc]
[136965.774089] ? nfsd_inet6addr_event+0x110/0x110 [nfsd]
[136965.774726] nfsd+0x87/0xc0 [nfsd]
[136965.775347] kthread+0xe5/0x110
[136965.775926] ? kthread_complete_and_exit+0x20/0x20
[136965.776499] ret_from_fork+0x1f/0x30
[136965.777062] </TASK>
Second:
[167723.787640] WARNING: CPU: 3 PID: 1872 at mm/slab_common.c:957 free_large_kmalloc+0x5a/0x80
[167723.787667] Modules linked in: <cut here>
[167723.787874] CPU: 3 PID: 1872 Comm: nfsd Kdump: loaded Not tainted 5.14.0-503.15.1.el9_5.x86_64 #1
[167723.787882] Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 2.22.2 09/12/2024
[167723.787886] RIP: 0010:free_large_kmalloc+0x5a/0x80
Third:
[ 3883.748094] ------------[ cut here ]------------
[ 3883.748105] WARNING: CPU: 9 PID: 1886 at mm/slab_common.c:957 free_large_kmalloc+0x5a/0x80
[ 3883.748131] Modules linked in: <cut here>
[ 3883.748339] CPU: 9 PID: 1886 Comm: nfsd Kdump: loaded Not tainted 5.14.0-503.15.1.el9_5.x86_64 #1
[ 3883.748342] Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 2.22.2 09/12/2024
[ 3883.748344] RIP: 0010:free_large_kmalloc+0x5a/0x80
File: crash.log (text/plain)
Size: 31.77 KiB
Link: https://bugzilla.kernel.org/attachment.cgi?id=307330
---
dmesg of another 3 crashes
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2024-12-07 8:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 2:35 Possible memory leak on nfsd Chen Chen via Bugspray Bot
2024-11-27 2:35 ` Chen Chen via Bugspray Bot
2024-11-27 2:35 ` Chen Chen via Bugspray Bot
2024-11-27 2:35 ` Chen Chen via Bugspray Bot
2024-11-27 2:35 ` Chen Chen via Bugspray Bot
2024-11-27 2:35 ` Chen Chen via Bugspray Bot
2024-11-27 2:35 ` Chen Chen via Bugspray Bot
2024-11-27 2:35 ` Chen Chen via Bugspray Bot
2024-12-07 8:35 ` Chen Chen via Bugspray Bot [this message]
2024-12-07 15:30 ` Chuck Lever via Bugspray Bot
2024-12-10 5:20 ` Chen Chen via Bugspray Bot
2024-12-10 14:45 ` Chuck Lever via Bugspray Bot
2024-12-11 1:15 ` Chen Chen via Bugspray Bot
2024-12-12 16:00 ` Chuck Lever via Bugspray Bot
2024-12-12 16:15 ` Fwd: " Chuck Lever
2025-01-10 16:50 ` Chen Chen via Bugspray Bot
2025-01-10 20:35 ` Chuck Lever
2025-01-22 20:45 ` JJ Jordan via Bugspray Bot
2025-01-22 21:25 ` JJ Jordan via Bugspray Bot
2025-01-22 21:25 ` JJ Jordan via Bugspray Bot
2025-01-22 21:25 ` JJ Jordan via Bugspray Bot
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=20241207-b219535c8-544381616c66@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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