All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: tytso@mit.edu,  adilger.kernel@dilger.ca,
	 linux-ext4@vger.kernel.org, jaegeuk@kernel.org,
	 chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 kernel@collabora.com, viro@zeniv.linux.org.uk,
	 brauner@kernel.org,  jack@suse.cz,
	 Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [PATCH v13 2/9] f2fs: Simplify the handling of cached insensitive names
Date: Thu, 14 Mar 2024 10:41:10 -0400	[thread overview]
Message-ID: <8734sskha1.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <aaa4561e-fd23-4b21-8963-7ba4cc99eed3@collabora.com> (Eugen Hristev's message of "Thu, 14 Mar 2024 10:44:09 +0200")

Eugen Hristev <eugen.hristev@collabora.com> writes:

>> Please, make sure you actually stress test this patchset with fstests
>> against both f2fs and ext4 before sending each new version.
>
> I did run the xfstests, however, maybe I did not run the full suite, or maybe I am
> running it in a wrong way ?

No worries.  Did you manage to reproduce it?

> How are you running the kvm-xfstests with qemu ? Can you share your command
> arguments please ?

I don't use kvm-xfstests.  I run ./check directly:

export SCRATCH_DEV=/dev/loop1
export SCRATCH_MNT=$BASEMNT/scratch
export TEST_DEV=/dev/loop0
export TEST_DIR=$BASEMNT/test
export RESULT_BASE=${BASEMNT}/results
export REPORT_DIR=${BASEMNT}/report
export FSTYP=f2fs

mkfs.f2fs -f -C utf8 -O casefold ${TEST_DEV}

./check -g encrypt,quick

-- 
Gabriel Krisman Bertazi

WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: brauner@kernel.org, kernel@collabora.com, tytso@mit.edu,
	jack@suse.cz, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, adilger.kernel@dilger.ca,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	jaegeuk@kernel.org, linux-ext4@vger.kernel.org,
	Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [f2fs-dev] [PATCH v13 2/9] f2fs: Simplify the handling of cached insensitive names
Date: Thu, 14 Mar 2024 10:41:10 -0400	[thread overview]
Message-ID: <8734sskha1.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <aaa4561e-fd23-4b21-8963-7ba4cc99eed3@collabora.com> (Eugen Hristev's message of "Thu, 14 Mar 2024 10:44:09 +0200")

Eugen Hristev <eugen.hristev@collabora.com> writes:

>> Please, make sure you actually stress test this patchset with fstests
>> against both f2fs and ext4 before sending each new version.
>
> I did run the xfstests, however, maybe I did not run the full suite, or maybe I am
> running it in a wrong way ?

No worries.  Did you manage to reproduce it?

> How are you running the kvm-xfstests with qemu ? Can you share your command
> arguments please ?

I don't use kvm-xfstests.  I run ./check directly:

export SCRATCH_DEV=/dev/loop1
export SCRATCH_MNT=$BASEMNT/scratch
export TEST_DEV=/dev/loop0
export TEST_DIR=$BASEMNT/test
export RESULT_BASE=${BASEMNT}/results
export REPORT_DIR=${BASEMNT}/report
export FSTYP=f2fs

mkfs.f2fs -f -C utf8 -O casefold ${TEST_DEV}

./check -g encrypt,quick

-- 
Gabriel Krisman Bertazi


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2024-03-14 14:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 10:15 [PATCH v13 0/9] Cache insensitive cleanup for ext4/f2fs Eugen Hristev
2024-03-05 10:15 ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 1/9] ext4: Simplify the handling of cached insensitive names Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 2/9] f2fs: " Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-13 23:36   ` Gabriel Krisman Bertazi
2024-03-13 23:36     ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-03-14  8:44     ` Eugen Hristev
2024-03-14  8:44       ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-14 14:41       ` Gabriel Krisman Bertazi [this message]
2024-03-14 14:41         ` Gabriel Krisman Bertazi
2024-03-18  9:53         ` Eugen Hristev
2024-03-18  9:53           ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 3/9] libfs: Introduce case-insensitive string comparison helper Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-13 23:16   ` Gabriel Krisman Bertazi
2024-03-13 23:16     ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-03-05 10:16 ` [PATCH v13 4/9] ext4: Reuse generic_ci_match for ci comparisons Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 5/9] f2fs: " Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 6/9] ext4: Log error when lookup of encoded dentry fails Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 7/9] f2fs: " Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 8/9] ext4: Move CONFIG_UNICODE defguards into the code flow Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel
2024-03-05 10:16 ` [PATCH v13 9/9] f2fs: " Eugen Hristev
2024-03-05 10:16   ` [f2fs-dev] " Eugen Hristev via Linux-f2fs-devel

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=8734sskha1.fsf@mailhost.krisman.be \
    --to=krisman@suse.de \
    --cc=adilger.kernel@dilger.ca \
    --cc=brauner@kernel.org \
    --cc=chao@kernel.org \
    --cc=eugen.hristev@collabora.com \
    --cc=jack@suse.cz \
    --cc=jaegeuk@kernel.org \
    --cc=kernel@collabora.com \
    --cc=krisman@collabora.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.