From: Greg KH <gregkh@linuxfoundation.org>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Heming Zhao <heming.zhao@suse.com>, Thomas Voegtle <tv@lio96.de>,
Su Yue <glass.su@suse.com>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: ocfs2 broken for me in 6.6.y since 6.6.55
Date: Thu, 12 Dec 2024 12:31:38 +0100 [thread overview]
Message-ID: <2024121223-causation-dainty-4472@gregkh> (raw)
In-Reply-To: <20feb966-acb8-40f7-8ee2-26d069b3f939@linux.alibaba.com>
On Thu, Dec 12, 2024 at 07:15:17PM +0800, Joseph Qi wrote:
>
>
> On 2024/12/12 19:06, Greg KH wrote:
> > On Thu, Dec 12, 2024 at 07:01:08PM +0800, Heming Zhao wrote:
> >> Hi Greg,
> >>
> >> On 12/12/24 18:54, Greg KH wrote:
> >>> On Thu, Dec 12, 2024 at 06:41:58PM +0800, Joseph Qi wrote:
> >>>> See: https://lore.kernel.org/ocfs2-devel/20241205104835.18223-1-heming.zhao@suse.com/T/#t
> >>>
> >>> And I need a working backport that I can apply to fix this :(
> >>
> >> I submitted a v2 patch set [1], which has been passed review.
> >>
> >> [1]:
> >> https://lore.kernel.org/ocfs2-devel/20241205104835.18223-1-heming.zhao@suse.com/T/#mc63e77487c4c7baba6d28fd536509e964ce3b892
> >
> > Then please submit it to the stable maintainers so that we can apply it.
> >
>
> The two patches are now in mm-tree.
> We may submit the revert patch to the affected stable trees once it goes into upstream.
Ah, sorry, I thought this was for a stable-only series. Nevermind, I'll
wait :)
thanks,
greg k-h
prev parent reply other threads:[~2024-12-12 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 10:32 ocfs2 broken for me in 6.6.y since 6.6.55 Thomas Voegtle
2024-12-12 10:41 ` Joseph Qi
2024-12-12 10:47 ` Thomas Voegtle
2024-12-12 10:54 ` Greg KH
2024-12-12 11:01 ` Heming Zhao
2024-12-12 11:06 ` Greg KH
2024-12-12 11:15 ` Joseph Qi
2024-12-12 11:31 ` 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=2024121223-causation-dainty-4472@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=glass.su@suse.com \
--cc=heming.zhao@suse.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=stable@vger.kernel.org \
--cc=tv@lio96.de \
/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