Linux block layer
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Cyril Hrubis <chrubis@suse.cz>,
	"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: Thu, 1 Aug 2024 14:42:45 +0530	[thread overview]
Message-ID: <d28b3e25-d464-4949-91fe-1752db6c5d5a@linux.ibm.com> (raw)
In-Reply-To: <4dhpiheoz4qjgg3zq67tjnkpx36hop2gpsnd5rublsht7zegyh@nw3mtu3zl54n>



On 8/1/24 11:57, Shinichiro Kawasaki wrote:
> On Jul 31, 2024 / 19:29, Nilay Shroff wrote:
>> Hi Shinichiro,
>>
>> On 7/31/24 18:16, Cyril Hrubis wrote:
>>> 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.
>>>
>>
>> This commit 5f75e081ab5c has been backported to kernel v6.9.11 and per the above 
>> comment from Cyril, this commit shall not be backported further to any other longterm 
>> kernel.
>>
>> So is it reasonable to assume that this test would fail on kernel older than v6.9.11?
> 
> I have the same guess.
> 
>> And if this is true then how about rewriting the patch as below ?
>>
>> diff --git a/tests/loop/011 b/tests/loop/011
>> index 35eb39b..a454848 100755
>> --- a/tests/loop/011
>> +++ b/tests/loop/011
>> @@ -9,6 +9,7 @@
>>  DESCRIPTION="Make sure unsupported backing file fallocate does not fill dmesg with errors"
>>  
>>  requires() {
>> +       _have_kver 6 9 11
>>         _have_program mkfs.ext2
>>  }
> 
> I think this change is reasonable. Would you repost the patch?
Sure, I will send another patch.

Thanks,
--Nilay

      reply	other threads:[~2024-08-01  9:12 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
2024-07-31 13:59         ` Nilay Shroff
2024-08-01  6:27           ` Shinichiro Kawasaki
2024-08-01  9:12             ` Nilay Shroff [this message]

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=d28b3e25-d464-4949-91fe-1752db6c5d5a@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=chrubis@suse.cz \
    --cc=gjoyce@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --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