From: Muchun Song <muchun.song@linux.dev>
To: Qi Zheng <qi.zheng@linux.dev>
Cc: akpm@linux-foundation.org, david@fromorbit.com,
roman.gushchin@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Qi Zheng <zhengqi.arch@bytedance.com>
Subject: Re: [PATCH] mm: shrinker: fix NULL pointer dereference in debugfs
Date: Wed, 17 Jun 2026 17:10:50 +0800 [thread overview]
Message-ID: <C5352957-F9C3-4B65-8595-8C8AD10DF30C@linux.dev> (raw)
In-Reply-To: <20260617090052.27325-1-qi.zheng@linux.dev>
> On Jun 17, 2026, at 17:00, Qi Zheng <qi.zheng@linux.dev> wrote:
>
> From: Qi Zheng <zhengqi.arch@bytedance.com>
>
> The shrinker_debugfs_add() creates both "count" and "scan" debugfs files
> unconditionally.
>
> That assumes every shrinker implements both count_objects() and
> scan_objects(), which is not guaranteed. For example, the xen-backend
> shrinker sets count_objects() but leaves scan_objects() NULL, so writing
> to its scan file calls through a NULL function pointer and panics the
> kernel:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> RIP: 0010:0x0
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> Call Trace:
> <TASK>
> shrinker_debugfs_scan_write+0x12e/0x270
> full_proxy_write+0x5f/0x90
> vfs_write+0xde/0x420
> ? filp_flush+0x75/0x90
> ? filp_close+0x1d/0x30
> ? do_dup2+0xb8/0x120
> ksys_write+0x68/0xf0
> ? filp_flush+0x75/0x90
> do_syscall_64+0xb3/0x5b0
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> The count path has the same issue in principle if a shrinker omits
> count_objects().
>
> To fix it, only create "count" and "scan" debugfs files when the
> corresponding callbacks are present.
>
> Fixes: bbf535fd6f06 ("mm: shrinkers: add scan interface for shrinker debugfs")
> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
Reviewed-by: Muchun Song <muchun.song@linux.dev>
Thanks.
prev parent reply other threads:[~2026-06-17 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 9:00 [PATCH] mm: shrinker: fix NULL pointer dereference in debugfs Qi Zheng
2026-06-17 9:10 ` Muchun Song [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=C5352957-F9C3-4B65-8595-8C8AD10DF30C@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qi.zheng@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=zhengqi.arch@bytedance.com \
/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