[lkml]   [2006]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: GFS2 and DLM

On Tue, 2006-06-27 at 10:35 +0200, Ingo Molnar wrote:
> * Andrew Morton <> wrote:
> > On Tue, 27 Jun 2006 08:33:39 +0200
> > Ingo Molnar <> wrote:
> >
> > > Isnt this whole episode highly hypocritic to begin with?
> >
> > Might be, but that's not relevant to GFS2's suitability.
> it is relevant to a certain degree, because it creates a (IMO) false
> impression of merging showstoppers. After months of being in -mm, and
> after addressing all issues that were raised (and there was a fair
> amount of review activity December last year iirc), one week prior the
> close of the merge window a 'huge' list of issues are raised. (after
> belovingly calling the GFS2 code a "huge mess", to create a positive and
> productive tone for the review discussion i guess.)
> So far in my reading there are only 2 serious ones in that list:
> - tty_* use in cluster-aware quota.c. Firstly, ocfs2 doesnt do quota -
> which is fair enough, but this also means that there was no in-tree
> filesystem to base stuff off. Secondly, the tty_* use was inherited
> from fs/quota.c - hardly something i'd consider a fatal sin. Anyway,
> despite the mitigating factors it is an arguably lame thing and
> it should be (and will be) fixed.
This one is now fixed in the git tree:
Also fixed/changed in this tree is:

o Mark GFS2 file_operations const
o Mark GFS2 address_space_operations const
o Update gfs2_statfs() API in line with change in Linus' tree
o Update gfs2_get_sb() API in line with change in Linus' tree (thanks
to Andrew Morton for this one)
o Updated to latest Linus tree

So I think that brings the code back uptodate after my holiday last

> - GFP_NOFAIL: most other journalling filesystems seem to be doing this
> or worse. Fixing it is _hard_. Suddenly this becomes a showstopper?
> Huh?
> (the "use the generic facilities" arguments are only valid if the
> generic facilities can be used as-is, and if they are just optimal as
> the one implemented by the filesystem.)
> Ingo
I believe that this point is now resolved (so far as GFS2 going upstream
is concerned) from the discussions that have gone on in my absence. Its
obviously still an ongoing concern for a number of filesystems, not just
GFS2 and I'll be working on ways to reduce the current "nofail"
allocation calls in the future,


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-07-03 15:31    [W:0.107 / U:13.264 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site