From: Venkat <venkat88@linux.ibm.com>
To: quwenruo.btrfs@gmx.com
Cc: linux-btrfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
ritesh.list@gmail.com, venkat88@linux.ibm.com,
disgoel@linux.ibm.com
Subject: Re: [linux-next-20250320][btrfs] Kernel OOPs while running btrfs/108
Date: Wed, 7 May 2025 14:31:34 +0530 [thread overview]
Message-ID: <0B1A34F5-2EEB-491E-9DD0-FC128B0D9E07@linux.ibm.com> (raw)
+Disha,
Hello Qu,
I still see this failure on next-20250505.
May I know, when will this be fixed.
Same traces are seen, while running other Tests also.
Disha,
Can you please share the details of Test and the traces.
Regards,
Venkat.
next reply other threads:[~2025-05-07 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 9:01 Venkat [this message]
2025-05-07 13:04 ` Filipe Manana
2025-05-07 14:14 ` David Sterba
2025-05-08 10:44 ` Venkat Rao Bagalkote
-- strict thread matches above, loose matches on Subject: below --
2025-03-21 10:20 Venkat Rao Bagalkote
2025-03-21 10:30 ` Venkat Rao Bagalkote
2025-03-21 15:56 ` Ritesh Harjani (IBM)
2025-03-21 21:18 ` Qu Wenruo
2025-03-22 14:15 ` Venkat Rao Bagalkote
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=0B1A34F5-2EEB-491E-9DD0-FC128B0D9E07@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=disgoel@linux.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=ritesh.list@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
all inboxes | Powered by JetHome®