From: Christoph Hellwig <hch@infradead.org>
To: Jianan Wang <wangjianan.zju@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: Question on xfs related kernel panic
Date: Tue, 21 Nov 2023 08:08:39 -0800 [thread overview]
Message-ID: <ZVzWB5JFW9vqpJ6F@infradead.org> (raw)
In-Reply-To: <179cca2a-65ee-45cf-8d5c-ca09fc18212e@gmail.com>
On Fri, Nov 10, 2023 at 02:23:53PM -0800, Jianan Wang wrote:
> Hi Darrick,
>
> Thanks for your response. I will open a case to Ubuntu on this issue. However, can you give me a hint on what could be wrong? Failed to kmalloc seems to be a pretty severe issue, and is that related to any kind of kernel memory corruption by certain kernel modules or so?
The P taint suggest you have a proprietary module loaded. Nothing
is even remotely supportable for that case.
prev parent reply other threads:[~2023-11-21 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 8:14 Question on xfs related kernel panic Jianan Wang
2023-11-10 8:48 ` Jianan Wang
2023-11-10 19:34 ` Darrick J. Wong
2023-11-10 22:23 ` Jianan Wang
2023-11-21 11:20 ` Carlos Maiolino
2023-11-21 16:08 ` Christoph Hellwig [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=ZVzWB5JFW9vqpJ6F@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=wangjianan.zju@gmail.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