Hi!
> > According to www.kernel.org, the 6.9 stable branch is already EOL. Is it planned
> > to backport the kernel fix to other longterm branches?
> I just checked this commit 5f75e081ab5c ("loop: Disable fallocate() zero and discard
> if not supported") hasn't been backported to any of the longterm stable kernel yet.
> However I don't know if there's any plan to backport it on longterm stable kernel.
The patch will not apply into older branches since the in kernel API did
change, so I suppose that nobody will invest into rewriting the patch
since it's mostly cosmetic.
> Maybe, Cyril should know about it?
>
> If not planned for backport on longterm stable kernel then we may consider the
> proposed changes in loop/011 as-is.
That's strange, I got an email shortly after the patch got into
mailinine about the backport:
Subject: Patch "loop: Disable fallocate() zero and discard if not supported" has been added to the 6.9-stable tree
Reply-To: stable@xxxxxxxxxxxxxxx
This is a note to let you know that I've just added the patch titled
loop: Disable fallocate() zero and discard if not supported
to the 6.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
loop-disable-fallocate-zero-and-discard-if-not-suppo.patch
and it can be found in the queue-6.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
commit 6718aa792b7d297ece53024a138ea679e8153ea6
Author: Cyril Hrubis <chrubis@xxxxxxx>
Date: Thu Jun 13 18:38:17 2024 +0200
loop: Disable fallocate() zero and discard if not supported
--
Cyril Hrubis
chrubis@xxxxxxx
