public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: dsterba@suse.cz, Filipe Manana <fdmanana@kernel.org>
Cc: 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: Thu, 8 May 2025 16:14:56 +0530	[thread overview]
Message-ID: <3096704a-84ec-4709-89ed-43ab1ed2b7c1@linux.ibm.com> (raw)
In-Reply-To: <20250507141409.GG9140@suse.cz>


On 07/05/25 7:44 pm, David Sterba wrote:
> 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.
Added again, was this removed? Can you please point me to patch or 
commit id. I was under impression, it never got removed.
>>
>> 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.


David,


While reverting those patches, please add below tags. And really 
appriciate, if you can keep me in CC.


Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>

Reported-by: Disha Goel <disgoel@linux.ibm.com>

Tested-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>

Closes: 
https://lore.kernel.org/all/e4b1ccf8-c626-4683-82db-219354a27e61@linux.ibm.com/



Regards,

Venkat.


  reply	other threads:[~2025-05-08 10:45 UTC|newest]

Thread overview: 7+ 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
2025-05-08 10:44     ` Venkat Rao Bagalkote [this message]
     [not found] <e4b1ccf8-c626-4683-82db-219354a27e61@linux.ibm.com>
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=3096704a-84ec-4709-89ed-43ab1ed2b7c1@linux.ibm.com \
    --to=venkat88@linux.ibm.com \
    --cc=disgoel@linux.ibm.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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 \
    /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