From: Greg KH <gregkh@linuxfoundation.org>
To: Baokun Li <libaokun@linux.alibaba.com>
Cc: Jiayuan Chen <jiayuan.chen@linux.dev>,
Wang Jun <1742789905@qq.com>,
tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, libaokun1@huawei.com,
25125332@bjtu.edu.cn, Jan Kara <jack@suse.cz>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>
Subject: Re: [PATCH] ext4: get rid of ppath in get_ext_path()
Date: Fri, 3 Jul 2026 10:20:35 +0200 [thread overview]
Message-ID: <2026070315-crescent-factoid-616d@gregkh> (raw)
In-Reply-To: <b93095c6-0717-4616-9702-570b2927429b@linux.alibaba.com>
On Fri, Jul 03, 2026 at 03:57:09PM +0800, Baokun Li wrote:
> On 2026/7/2 13:47, Greg KH wrote:
> > On Thu, Jul 02, 2026 at 09:48:33AM +0800, Jiayuan Chen wrote:
> >> Hi Greg,
> >>
> >> Any update here ?
> > What is "here"? There is no context in this email :(
> >
> >> We rebased the 6.6 stable one week ago and also found the same regression.
> > What regression? Again, no context :(
> >
> > confused,
> >
> > greg k-h
>
> For some reason, LTS only merged a subset of my patchset, causing
> some commits to lack their prerequisite patches. This leads to error
> numbers being interpreted as valid pointers.
>
> For details, see the fix patchset that Erkun submitted to 6.6.y
> (it fell through the cracks for some reason):
>
> https://lore.kernel.org/all/20260421113416.4040274-1-yangerkun@huawei.com/
>
> Either applying this fix patchset or reverting the incorrectly merged
> commit should resolve the issue.
How about submitting a revert so that we can start fresh and work from
there?
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-03 8:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 5:17 [PATCH] ext4: get rid of ppath in get_ext_path() Wang Jun
2026-06-26 6:49 ` Greg KH
2026-06-26 7:08 ` [PATCH] ext4: fix crash when ext4_ext_insert_extent() returns error Wang Jun
2026-07-02 1:48 ` [PATCH] ext4: get rid of ppath in get_ext_path() Jiayuan Chen
2026-07-02 5:47 ` Greg KH
2026-07-02 6:09 ` Jiayuan Chen
2026-07-02 18:20 ` Theodore Tso
2026-07-03 7:57 ` Baokun Li
2026-07-03 8:20 ` Greg KH [this message]
2026-07-03 8:44 ` Baokun Li
2026-07-03 11:48 ` Theodore Tso
2026-07-04 2:04 ` Sasha Levin
2026-07-02 14:12 ` Greg KH
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=2026070315-crescent-factoid-616d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=1742789905@qq.com \
--cc=25125332@bjtu.edu.cn \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=jiayuan.chen@linux.dev \
--cc=libaokun1@huawei.com \
--cc=libaokun@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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