From: Greg KH <gregkh@linuxfoundation.org>
To: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Cc: johannes.berg@intel.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Kernel Warnings at fs/debugfs/file.c 90
Date: Fri, 10 Jan 2025 09:34:52 +0100 [thread overview]
Message-ID: <2025011024-yearning-prism-020f@gregkh> (raw)
In-Reply-To: <a1cf98f7-c16b-472a-b56d-f745e94017ef@linux.vnet.ibm.com>
On Fri, Jan 10, 2025 at 12:14:13PM +0530, Venkat Rao Bagalkote wrote:
> Greetings!!!
>
>
> Observing Kernel Warnings on kernel 6.13.0-rc6-next-20250109, while running
> fstests ext4/001.
What is fstests doing in debugfs?
> Traces:
>
> [ 433.607975] ------------[ cut here ]------------
> [ 433.607984] WARNING: CPU: 2 PID: 32051 at fs/debugfs/file.c:90
> __debugfs_file_get+0xcc/0x274
This is an assertion firing, Johannes, any ideas?
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-10 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 6:44 Kernel Warnings at fs/debugfs/file.c 90 Venkat Rao Bagalkote
2025-01-10 8:34 ` Greg KH [this message]
2025-01-10 8:35 ` Greg KH
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=2025011024-yearning-prism-020f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=venkat88@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).