From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Christian Brauner <brauner@kernel.org>
Cc: willy@infradead.org, viro@zeniv.linux.org.uk, jack@suse.cz,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] fs: improve dump_mapping() robustness
Date: Thu, 18 Jan 2024 09:27:41 +0800 [thread overview]
Message-ID: <07ccff45-a728-4ed1-86f4-91517c656609@linux.alibaba.com> (raw)
In-Reply-To: <20240116-privat-zeitplan-21db23926f45@brauner>
On 1/16/2024 7:16 PM, Christian Brauner wrote:
> On Tue, 16 Jan 2024 15:53:35 +0800, Baolin Wang wrote:
>> We met a kernel crash issue when running stress-ng testing, and the
>> system crashes when printing the dentry name in dump_mapping().
>>
>> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
>> pc : dentry_name+0xd8/0x224
>> lr : pointer+0x22c/0x370
>> sp : ffff800025f134c0
>> ......
>> Call trace:
>> dentry_name+0xd8/0x224
>> pointer+0x22c/0x370
>> vsnprintf+0x1ec/0x730
>> vscnprintf+0x2c/0x60
>> vprintk_store+0x70/0x234
>> vprintk_emit+0xe0/0x24c
>> vprintk_default+0x3c/0x44
>> vprintk_func+0x84/0x2d0
>> printk+0x64/0x88
>> __dump_page+0x52c/0x530
>> dump_page+0x14/0x20
>> set_migratetype_isolate+0x110/0x224
>> start_isolate_page_range+0xc4/0x20c
>> offline_pages+0x124/0x474
>> memory_block_offline+0x44/0xf4
>> memory_subsys_offline+0x3c/0x70
>> device_offline+0xf0/0x120
>> ......
>>
>> [...]
>
> Seems fine for debugging purposes. Let me know if this needs to go through
> somewhere else.
Going through VFS tree is fine to me. Thanks.
next prev parent reply other threads:[~2024-01-18 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 7:53 [PATCH] fs: improve dump_mapping() robustness Baolin Wang
2024-01-16 11:16 ` Christian Brauner
2024-01-18 1:27 ` Baolin Wang [this message]
2024-01-18 1:38 ` Al Viro
2024-01-18 2:12 ` Matthew Wilcox
2024-01-18 14:04 ` Christian Brauner
2024-01-18 2:43 ` Baolin Wang
2024-01-19 15:48 ` Charan Teja Kalla
2024-01-22 7:17 ` Baolin Wang
2024-01-22 16:28 ` Charan Teja Kalla
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=07ccff45-a728-4ed1-86f4-91517c656609@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).