Linux block layer
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>
Subject: Re: [PATCH blktests] loop/011: skip if running on kernel older than v6.10
Date: Wed, 31 Jul 2024 14:46:06 +0200	[thread overview]
Message-ID: <ZqoyDjCpaXPaU1uN@yuki> (raw)
In-Reply-To: <914eec96-eb46-4cf1-9cbd-0e1f98059d1b@linux.ibm.com>

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@vger.kernel.org

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@vger.kernel.org> know about it.



commit 6718aa792b7d297ece53024a138ea679e8153ea6
Author: Cyril Hrubis <chrubis@suse.cz>
Date:   Thu Jun 13 18:38:17 2024 +0200

    loop: Disable fallocate() zero and discard if not supported


-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2024-07-31 12:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 11:17 [PATCH blktests] loop/011: skip if running on kernel older than v6.10 Nilay Shroff
2024-07-31 11:23 ` Cyril Hrubis
2024-07-31 12:01   ` Shinichiro Kawasaki
2024-07-31 12:41     ` Nilay Shroff
2024-07-31 12:46       ` Cyril Hrubis [this message]
2024-07-31 13:59         ` Nilay Shroff
2024-08-01  6:27           ` Shinichiro Kawasaki
2024-08-01  9:12             ` Nilay Shroff

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=ZqoyDjCpaXPaU1uN@yuki \
    --to=chrubis@suse.cz \
    --cc=gjoyce@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=nilay@linux.ibm.com \
    --cc=shinichiro.kawasaki@wdc.com \
    /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