From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
"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 14:13:59 -0500 [thread overview]
Message-ID: <534D84F7.30003@redhat.com> (raw)
In-Reply-To: <20140415184442.GC4456@thunk.org>
On 4/15/14, 1:44 PM, Theodore Ts'o wrote:
> On Tue, Apr 15, 2014 at 11:15:41AM -0500, Eric Sandeen wrote:
>>
>> 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...
>
> Yeah, I went back and forth on this. One of there reasons why I added
> a kernel knob is that *I* can make the kernel change a lot faster than
> it would be to tweak all of the various xfstests program to globally
> disable certain operations in fsx, fstress, etc.
>
> I also had a sneaking suspicion that we might have a similar issue
> with the INSERT RANGE patches which are coming down the pike, and so
> having a general way of also being able INSERT RANGE if to be able to
> quickly determine whether a potential bug was caused by INSERT RANGE
> or some other pending changes might also be useful.
>
> I freely admit it is a bit of a hack, though. Does the hack smell
> less bad if we wrap it in CONFIG_EXT4FS_DEBUG?
>
>> [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...
>
> Yes, although as I mentioned above, it would be really nice if it
> worked across all of the various tests, and not just be limited to
> fsx, or even just fsx and fstress.
Well, for tests which are specific to collapse range, it'd be trivial
to add a "collapse" group, and exclude it.
For generic stress tests which happen to do collapse range, it'd take
a bit more. But that'd probably still be the generic solution.
XFS got bitten too, there were collapse range problems. But the fixes
are already in the pipe AFAIK.
-Eric
> - Ted
>
>
>
next prev parent reply other threads:[~2014-04-15 19:14 UTC|newest]
Thread overview: 15+ 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
2014-04-15 18:44 ` Theodore Ts'o
2014-04-15 19:13 ` Eric Sandeen [this message]
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 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=534D84F7.30003@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 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.