Linux Test Project
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Andrea Cervesato" <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1 1/1] swap: Add exfat to filesystems requiring tst_fill_file
Date: Wed, 17 Jun 2026 15:19:07 +0000	[thread overview]
Message-ID: <6a32baec.95d0a0ea.22b4a3.6ffe@mx.google.com> (raw)
In-Reply-To: <6a32b644.f32a6769.150c63.1270@mx.google.com>

> I'm just wondering how to implement it better.
> 
> First of all, we should mention the commit that introduced fallocate()
> support into exfat inside the patch commit message.
> 
> Secondly, since the code was already working before v7.1, maybe we should
> fill the file in exfat only for kernel >= 7.1. But I don't want to touch
> the core library.

Second update: .swap_activate is not implemented in the linux kernel
for exfat and the commit causes EINVAL only for swap allocation. That
is caused by bmap() due to the generic swap activation.

So instead of working around the issue, we probably should have a feature
in the kernel along with fallocate() support in exfat.

Probably a kernel bug/missing feature.

--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2026-06-17 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 15:52 [LTP] [PATCH v1 1/1] swap: Add exfat to filesystems requiring tst_fill_file Jan Polensky
2026-06-08 16:29 ` [LTP] " linuxtestproject.agent
2026-06-09  9:19 ` [LTP] [PATCH v1 1/1] " Cyril Hrubis
2026-06-09 14:17   ` Jan Polensky
2026-06-12  9:06     ` Andrea Cervesato via ltp
2026-06-12  9:07       ` Cyril Hrubis
2026-06-17 13:56         ` Andrea Cervesato via ltp
2026-06-17 14:59           ` Andrea Cervesato via ltp
2026-06-17 15:19             ` Andrea Cervesato via ltp [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=6a32baec.95d0a0ea.22b4a3.6ffe@mx.google.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.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