From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Lyakas <alex.lyakas@zadara.com>
Cc: stable@vger.kernel.org
Subject: Re: stable patch 42fac18 missing from linux-6.6
Date: Mon, 23 Jun 2025 11:15:13 +0200 [thread overview]
Message-ID: <2025062326-tutu-improve-c423@gregkh> (raw)
In-Reply-To: <CAOcd+r3C3LKPv-Jc1op5t1Xn5aijV9k-M4wm1hopARu=sy+fnQ@mail.gmail.com>
On Mon, Jun 23, 2025 at 12:07:42PM +0300, Alex Lyakas wrote:
> On Mon, Jun 23, 2025 at 9:35 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Sun, Jun 15, 2025 at 06:36:44PM +0300, Alex Lyakas wrote:
> > > Greetings,
> > >
> > > The following patch [1]:
> > > "42fac18 btrfs: check delayed refs when we're checking if a ref exists"
> > > has been marked as
> > > "CC: stable@vger.kernel.org # 5.4+"
> > > but I do not see that it has been backported to linux-6.6.y branch.
> > >
> > > Can this patch be picked up in the next version of linux-6.6 please?
> >
> > It does not apply cleanly there at all, which is why we did not apply it
> > already. How did you test this change works in this tree?
> Hi Greg,
> Thank you for your response.
>
> >
> > If you want it here, great, can you provide a backported and tested
> > version?
> I backported the patch and tested it to the best of my ability. I was
> able to test the part where the reference exists in the extent tree,
> which means the patch doesn't break existing functionality. However, I
> was not able to test the case where we only have the delayed
> reference.
Then it's hard to know if it works :(
> Please let me know if this is still good enough, so that I can post
> this patch for review here (or on linux-stable-commits?).
linux-stable-commits is just for when we apply stuff to the tree,
stable@vger.kernel.org is for submitting new stuff.
If you think your backport is correct, sure, submit it, it's your call.
thanks,
greg k-h
prev parent reply other threads:[~2025-06-23 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 15:36 stable patch 42fac18 missing from linux-6.6 Alex Lyakas
2025-06-23 6:35 ` Greg KH
2025-06-23 9:07 ` Alex Lyakas
2025-06-23 9:15 ` Greg KH [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=2025062326-tutu-improve-c423@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alex.lyakas@zadara.com \
--cc=stable@vger.kernel.org \
/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