Re: [PATCH] ext4: get rid of ppath in get_ext_path()

[Baokun Li]

On 2026/7/4 10:04, Sasha Levin wrote:
> On Fri, Jul 03, 2026 at 10:20:35AM +0200, Greg KH wrote:
>> On Fri, Jul 03, 2026 at 03:57:09PM +0800, 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?
> I've queued upstream 6b854d552711 ("ext4: get rid of ppath in get_ext_path()")
> for 6.6.y. It completes the partial series that went into 6.6.130 (which
> stopped one patch short of it) and adds the IS_ERR_OR_NULL() checks to
> ext4_free_ext_path() / ext4_ext_drop_refs(), resolving the reported oops. Yoann
> Congal also posted a backport of the same commit yesterday.
>
> Given that 6.6.y is nine patches into this series, completing it looked
> less risky than unwinding all of them plus redoing the fixes on top.
>
> Baokun, if the other two patches from yangerkun's April set
> (ext4_force_split_extent_at() / convert_initialized_extent()) are still
> needed on 6.6.y, I'm happy to take those as well.
>

Thanks for your work! Backporting just the first patch is sufficient
to address the reported issue.

The other two are there to keep the interface consistent and to avoid
potential issues with future adaptations, but it's fine to leave them
out for now.


Cheers,
Baokun