From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: 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: Thu, 2 Jul 2026 14:09:53 +0800 [thread overview]
Message-ID: <8b1d5b5d-61f5-40b1-95d4-35f98a280db8@linux.dev> (raw)
In-Reply-To: <2026070210-catty-grape-2568@gregkh>
On 7/2/26 1:47 PM, 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 :(
Sorry I dropped the context:
https://lore.kernel.org/stable/tencent_C982B0201FE8F041BD5B4FC1ED7D646A740A@qq.com/
This patch is trying to fix the regression which Introduced by this series:
[PATCH 6.6 046/567] ext4: get rid of ppath in ext4_ext_insert_extent()
https://lore.kernel.org/all/20260323134534.939905793@linuxfoundation.org/
The series was also backported to 6.1 but reverted later.
https://lore.kernel.org/all/20260408010208.746177-1-sashal@kernel.org/
So I'm confused about the next action will we accept Wang Jun's patch or
we just revert it as 6.1 did ?
>
>> We rebased the 6.6 stable one week ago and also found the same regression.
> What regression? Again, no context :(
>
> confused,
>
> greg k-h
next prev parent reply other threads:[~2026-07-02 6:10 UTC|newest]
Thread overview: 15+ 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 [this message]
2026-07-02 18:20 ` Theodore Tso
2026-07-03 7:57 ` Baokun Li
2026-07-03 8:20 ` Greg KH
2026-07-03 8:44 ` Baokun Li
2026-07-03 11:48 ` Theodore Tso
2026-07-05 7:40 ` Baokun Li
2026-07-04 2:04 ` Sasha Levin
2026-07-05 7:51 ` Baokun Li
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=8b1d5b5d-61f5-40b1-95d4-35f98a280db8@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=1742789905@qq.com \
--cc=25125332@bjtu.edu.cn \
--cc=adilger.kernel@dilger.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=libaokun1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.