linux-ext4 - Re: [PATCH RFC 00/30] Ext4 snapshots

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Jun 2011 09:40:33 +0300
From:	"Amir G." <amir73il@...rs.sourceforge.net>
To:	"Ted Ts'o" <tytso@....edu>
Cc:	Eric Sandeen <sandeen@...hat.com>,
	Lukas Czerner <lczerner@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH RFC 00/30] Ext4 snapshots - core patches

On Mon, Jun 6, 2011 at 11:55 PM, Ted Ts'o <tytso@....edu> wrote:
> On Mon, Jun 06, 2011 at 10:31:33AM -0500, Eric Sandeen wrote:
>> > For one reason, a snapshot file format is currently an indirect file
>> > and big_alloc
>> > doesn't support indirect mapped files.
>> > I am not saying it cannot be done, but if it does, there would be
>> > several obstacles
>> > to cross.
>>
>> I know I'm kind of just throwing a bomb out here, but I am very concerned
>> about the ever-growing feature (in)compatibility matrix in ext4.
>
> bigalloc doesn't support indirect blocks mainly because it was faster
> to get things working if I didn't have to worry about indirect blocks.
> It wouldn't be _that_ hard to make bigalloc work on indirect blocks.
> I'll get around to it at some point.
>
> dioread_nolock is something that I had hoped to clean up by now, by
> making this the default way we do all buffered writebacks, for all
> block sizes.
>
>> Take for example dioread_nolock caveats:
>>
>>           "However this does not work with nobh
>>            option and the mount will fail. Nor does it work with
>>            data journaling and dioread_nolock option will be
>>            ignored with kernel warning. Note that dioread_nolock
>>            code path is only used for extent-based files."
>
> Hey, at least we got rid of nobh!  :-)
>
>> If ext4 matches the lifespan of ext3, in 10 years I fear that it will look
>> more like a collection of various individuals' pet projects, rather than
>> any kind of well-designed, cohesive project.
>>
>> How long can we really keep adding features which are semi- or wholly-
>> incompatible with other features?
>>
>> Consider this a cry in the wilderness for less rushed feature introduction,
>> and a more holistic approach to ext4 design...
>
> It's something I do worry about; and I do share your concern.  At the
> same time, the reality is that we are a little like the Old Dutch
> Masters, who had take into account the preference of their patrons
> (i.e., in our case, those who pay our paychecks :-).
>
> In the case of dioread_nolock, I allowed dioread_nolock in even though
> it was a not a complete solution since internally, we had critical
> business for it, and in my judgement, (a) it wasn't that horrible
> (most of the horrible code paths was already being used for AIO/DIO),
> and (b) I had a plan for how to clean it up eventually.  The
> fs/ext4/page_io.c implementation was in fact the first part of my
> cleanup plan, so we've made some progress; it's just not gone as fast
> as I would like.
>
> Snapshots are an example of a feature where I am very much worried
> about taking on technical debt.  On the other hand, there are a lot of
> people who are quite excited of it as a feature, so I'm hoping we can
> clean it up enough we don't put a huge maintenance burden on
> ourselves.
>
> It should be possible to make snapshots work on bigalloc file systems,
> once support is added for indirect blocks.  The COW granulaity will
> have to be done at the cluster level, of course, though.  So from a
> design perspective it should be possible to make things knit together.
>

The question is why *should* we knit those 2 features together?
There is a patron for snapshots and there is a patron for big_alloc,
but is there a patron for both mixed? I don't thinks so.
*This* is a maintenance burden, because none of the patrons will pay
us to support this configuration.

What's so bad about mutually excluding features, which are useful
on their own? For one thing, it keeps the test matrix smaller, so it is
actually realistic to follow it through.

I hear Eric's cry in the wilderness and I can relate to it.
Maybe is the distros that need to take action about it and declare
only a reduces set of features matrix 'supported'.
We can even try to write generic mutual exclusion rules, which
will be enforced by mke2fs/tune2fs and ext4.

Amir.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html