linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Lukáš Czerner" <lczerner@redhat.com>, "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
	Namjae Jeon <linkinjeon@gmail.com>
Subject: Re: [PATCH] ext4: add fallocate mode blocking for debugging purposes
Date: Tue, 15 Apr 2014 11:15:41 -0500	[thread overview]
Message-ID: <534D5B2D.70408@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1404151749490.2146@localhost.localdomain>

On 4/15/14, 11:02 AM, Lukáš Czerner wrote:
> On Sun, 13 Apr 2014, Theodore Ts'o wrote:
> 
>> Date: Sun, 13 Apr 2014 18:00:16 -0400
>> From: Theodore Ts'o <tytso@mit.edu>
>> To: Ext4 Developers List <linux-ext4@vger.kernel.org>
>> Cc: Namjae Jeon <linkinjeon@gmail.com>
>> Subject: Re: [PATCH] ext4: add fallocate mode blocking for debugging purposes
>>
>> On Sun, Apr 13, 2014 at 04:21:58PM -0400, Theodore Ts'o wrote:
>>> If a particular fallocate mode is causing test failures, give the
>>> tester the ability to block a particular fallocate mode so that the
>>> use of a particular fallocate mode will be reported as not supported.
>>>
>>> For example, if the COLLAPSE_RANGE fallocate mode is causing test
>>> failures, this allows us to suppress it so we can more easily test the
>>> rest of the file system code.
>>
>> Hi Namjae,
>>
>> One of the reasons this patch set is that after Lukas added
>> COLLAPSE_RANGE support into fsx, we've started seeing a number of
>> failures which seem to be directly related to COLLAPSE_RANGE.
> 
> Ah, I did mentioned it when I added COLLAPSE_RANGE to the fsx and
> fsstress, but I forgot to cc you Namjae, sorry about that.
> 
> But about the patch. It seems a little bit weird to change kernel
> for this. The way I am doing it is by changing ltp/fsx.c and
> ltp.fsstress.c to disable the particular mode:

I tend to agree, better to fix the kernel than to add a knob to turn it
off.  And fsx changes can happen a lot quicker than kernel changes.  [1]

And if it's really unsafe, and you really want to add a knob, I'd at least
default it to off until it's non-corrupting, and add a message that
this tunable will go away as soon as it's stable, so you'll have no
qualms about quickly deprecating it...

-Eric

[1] it'd be nifty to make an env. var in xfstests which can globally
disable certain fsx operations across all tests which run fsx...
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-04-15 16:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 20:21 [PATCH] ext4: add fallocate mode blocking for debugging purposes Theodore Ts'o
2014-04-13 22:00 ` Theodore Ts'o
2014-04-14 14:05   ` Namjae Jeon
2014-04-16 16:05     ` Lukáš Czerner
2014-04-15 16:02   ` Lukáš Czerner
2014-04-15 16:15     ` Eric Sandeen [this message]
2014-04-15 18:44       ` Theodore Ts'o
2014-04-15 19:13         ` Eric Sandeen
2014-04-15 22:32         ` Eric Sandeen
2014-04-15 23:30           ` Theodore Ts'o
2014-04-16  0:06             ` Dave Chinner
2014-04-16  5:47               ` Theodore Ts'o
2014-04-15 23:25         ` Dave Chinner
2014-04-16  0:23           ` Theodore Ts'o

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=534D5B2D.70408@redhat.com \
    --to=sandeen@redhat.com \
    --cc=lczerner@redhat.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).