public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Changjian Liu <driz2t@qq.com>
Cc: stable@vger.kernel.org,
	syzbot+1dd53396e7124586dca9@syzkaller.appspotmail.com,
	Dmitry Antipov <dmantipov@yandex.ru>,
	syzbot+77026564530dbc29b854@syzkaller.appspotmail.com,
	syzbot+5054473a31f78f735416@syzkaller.appspotmail.com,
	Joseph Qi <joseph.qi@linux.alibaba.com>,
	Junxiao Bi <junxiao.bi@oracle.com>, Jun Piao <piaojun@huawei.com>,
	Deepanshu Kartikey <kartikey406@gmail.com>,
	Heming Zhao <heming.zhao@suse.com>,
	Joel Becker <jlbec@evilplan.org>, Mark Fasheh <mark@fasheh.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] PATCH] This is a backport for 6.6.y.
Date: Sun, 29 Mar 2026 09:56:35 +0200	[thread overview]
Message-ID: <2026032927-graded-singer-06bd@gregkh> (raw)
In-Reply-To: <tencent_2A43212936E23BCA7ED345CADA51A8B2390A@qq.com>

On Sun, Mar 29, 2026 at 03:44:22PM +0800, Changjian Liu wrote:
> [ Upstream commit e1c70505ee8158c1108340d9cd67182ade93af4a ]
> 
> ocfs2: add extra consistency checks for chain allocator dinodes

Your subject line is very odd.

And why just this one branch?  What is the reason to do this here?

We obviously can not take a fix for only an older branch but not a newer
one, otherwise you would have a regression when you update to a newer
kernel release, right?

thanks,

greg k-h

      reply	other threads:[~2026-03-29  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29  7:44 [PATCH] PATCH] This is a backport for 6.6.y Changjian Liu
2026-03-29  7:56 ` 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=2026032927-graded-singer-06bd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dmantipov@yandex.ru \
    --cc=driz2t@qq.com \
    --cc=heming.zhao@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=junxiao.bi@oracle.com \
    --cc=kartikey406@gmail.com \
    --cc=mark@fasheh.com \
    --cc=piaojun@huawei.com \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+1dd53396e7124586dca9@syzkaller.appspotmail.com \
    --cc=syzbot+5054473a31f78f735416@syzkaller.appspotmail.com \
    --cc=syzbot+77026564530dbc29b854@syzkaller.appspotmail.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