Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
	linux-kernel@vger.kernel.org
Cc: usama.anjum@collabora.com,
	Christian Kellner <ckellner@redhat.com>,
	Alexander Larsson <alexl@redhat.com>,
	Alberto Ruiz <aruiz@redhat.com>, Peter Jones <pjones@redhat.com>,
	Lennart Poettering <lennart@poettering.net>,
	Colin Walters <walters@verbum.org>,
	Chung-Chiang Cheng <cccheng@synology.com>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 3/3] selftests/filesystems: add a vfat RENAME_EXCHANGE test
Date: Fri, 27 May 2022 11:09:23 +0500	[thread overview]
Message-ID: <193aad3f-82dd-76a8-a44c-5000ab203dc2@collabora.com> (raw)
In-Reply-To: <20220526134119.242182-4-javierm@redhat.com>

On 5/26/22 6:41 PM, Javier Martinez Canillas wrote:
> Add a test for the renameat2 RENAME_EXCHANGE support in vfat, but split it
> in a tool that just does the rename exchange and a script that is run by
> the kselftests framework on `make TARGETS="filesystems/fat" kselftest`.
> 
> That way the script can be easily extended to test other file operations.
> 
> The script creates a 1 MiB disk image, that is then formated with a vfat
> filesystem and mounted using a loop device. That way all file operations
> are done on an ephemeral filesystem.
> 
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Acked-by: Muhammad Usama Anjum <usama.anjum@collabora.com>

-- 
Muhammad Usama Anjum

      reply	other threads:[~2022-05-27  6:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 13:41 [PATCH v3 0/3] fat: add support for the renameat2 RENAME_EXCHANGE flag Javier Martinez Canillas
2022-05-26 13:41 ` [PATCH v3 3/3] selftests/filesystems: add a vfat RENAME_EXCHANGE test Javier Martinez Canillas
2022-05-27  6:09   ` Muhammad Usama Anjum [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=193aad3f-82dd-76a8-a44c-5000ab203dc2@collabora.com \
    --to=usama.anjum@collabora.com \
    --cc=alexl@redhat.com \
    --cc=aruiz@redhat.com \
    --cc=cccheng@synology.com \
    --cc=ckellner@redhat.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=javierm@redhat.com \
    --cc=lennart@poettering.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pjones@redhat.com \
    --cc=shuah@kernel.org \
    --cc=walters@verbum.org \
    /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