From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@kernel.org>
Cc: Venkat <venkat88@linux.ibm.com>,
quwenruo.btrfs@gmx.com, linux-btrfs@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
ritesh.list@gmail.com, disgoel@linux.ibm.com,
David Sterba <dsterba@suse.com>
Subject: Re: [linux-next-20250320][btrfs] Kernel OOPs while running btrfs/108
Date: Wed, 7 May 2025 16:14:09 +0200 [thread overview]
Message-ID: <20250507141409.GG9140@suse.cz> (raw)
In-Reply-To: <CAL3q7H7PqVRnDuooSr6OhvUQ3G5V2gq6VEDpqTqNX9jHmq97aw@mail.gmail.com>
On Wed, May 07, 2025 at 02:04:47PM +0100, Filipe Manana wrote:
> On Wed, May 7, 2025 at 10:02 AM Venkat <venkat88@linux.ibm.com> wrote:
> >
> > +Disha,
> >
> > Hello Qu,
> >
> > I still see this failure on next-20250505.
> >
> > May I know, when will this be fixed.
>
> The two patches pointed out before by Qu are still being added to linux-next.
> Qu reported this on the thread for the patches:
>
> https://lore.kernel.org/linux-btrfs/0146825e-a1b1-4789-b4f5-a0894347babe@gmx.com/
>
> There was no reply from the author and David added them again to
> for-next/linux-next.
>
> David, can you drop them out from for-next? Why are they being added
> again when there were no changes since last time?
The patches have been there for like 4 -rc kernels without reported
problems. I will remove them again.
next prev parent reply other threads:[~2025-05-07 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 9:01 [linux-next-20250320][btrfs] Kernel OOPs while running btrfs/108 Venkat
2025-05-07 13:04 ` Filipe Manana
2025-05-07 14:14 ` David Sterba [this message]
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=20250507141409.GG9140@suse.cz \
--to=dsterba@suse.cz \
--cc=disgoel@linux.ibm.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--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 \
--cc=venkat88@linux.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).