Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Baokun Li <libaokun@linux.alibaba.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Jiayuan Chen <jiayuan.chen@linux.dev>,
	Wang Jun <1742789905@qq.com>,
	adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	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: Sun, 5 Jul 2026 15:40:35 +0800	[thread overview]
Message-ID: <18cab6b1-d94e-4a82-a518-ba3c2ef02864@linux.alibaba.com> (raw)
In-Reply-To: <akehR1wEgK23wFp4@mit.edu>

On 2026/7/3 19:48, Theodore Tso wrote:
> On Fri, Jul 03, 2026 at 04:44:32PM -0500, Baokun Li wrote:
>>>> 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?
>> Alright, I can help review the patches.
> Can you also double check whether your patchset actually fixes a bug
> in 6.6?  As near as I can tell, it wasn't needed for 6.1 at all.
>

The earlier patches in the "get rid of ppath" series that I tagged as
bugfixes have already been backported to stable.

The remaining "get rid of ppath" patches without a Fixes: tag (the ones
recently picked up by stable) are there purely for code readability and
to reduce the risk of future misuse — they don't fix any actual bug.

Looking at what was pulled in, the patch carries a tag:

  Stable-dep-of: 22784ca541c0 ("ext4: subdivide EXT4_EXT_DATA_VALID1")

which in turn is a dependency of:

  58ddae5d77b1 ("ext4: don't zero the entire extent if
EXT4_EXT_DATA_PARTIAL_VALID1")

— a fix for a stale data read when free space is low.

However, the dependency of 22784ca541c0 on the "get rid of ppath"
series is purely a context (textual) dependency; not backporting
those patches should cause no functional issues.


Thanks,
Baokun


  reply	other threads:[~2026-07-05  7:40 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
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 [this message]
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=18cab6b1-d94e-4a82-a518-ba3c2ef02864@linux.alibaba.com \
    --to=libaokun@linux.alibaba.com \
    --cc=1742789905@qq.com \
    --cc=25125332@bjtu.edu.cn \
    --cc=adilger.kernel@dilger.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=jiayuan.chen@linux.dev \
    --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