From: Steven Whitehouse <swhiteho@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Russell Cattelan <cattelan@redhat.com>,
Patrick Caulfield <pcaulfie@redhat.com>,
David Teigland <teigland@redhat.com>,
Kevin Anderson <kanderso@redhat.com>, Ingo Molnar <mingo@elte.hu>,
hch@infradead.org
Subject: [PATCHSET] The GFS2 filesystem (for review)
Date: Thu, 31 Aug 2006 14:26:55 +0100 [thread overview]
Message-ID: <1157030815.3384.782.camel@quoit.chygwyn.com> (raw)
Hi,
Following on from this message are the 16 patches of GFS2 which we are
again posting for review. Since the last posting we have, I hope,
addressed all the issues raised as well as fixing a number of bugs. In
particular, we have now only one new exported symbol (see patch 16 of
the series).
It is now possible to mount the gfs2meta filesystem for a particular
gfs2 filesystem at the same time as the gfs2 filesystem is mounted. In
fact we enforce that rule at least for the time being due to
dependencies in mounting the two filesystems.
Christoph requested that we find a different way to deal with the
problem of the VFS checking the file size in the direct i/o read path
before handing control to GFS2 (in other words at a point when the size
may change). We have done this with a two line patch to filemap.c (also
in patch 16 of the series) so that its logic is now very similar to that
followed in the direct i/o write path. This has eliminated the need for
us to duplicate parts of the core VFS code inside GFS2.
As usual the git tree is at:
git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6.git
It is based off a fairly recent pull from Linus' tree and includes the
DLM which is not included in the patch set being posted here.
Steve.
next reply other threads:[~2006-08-31 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 13:26 Steven Whitehouse [this message]
2006-09-01 21:27 ` Pavel Machek
2006-09-04 13:07 ` Steven Whitehouse
2006-09-04 19:42 ` Pavel Machek
2006-09-05 13:59 ` Steven Whitehouse
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=1157030815.3384.782.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.com \
--cc=cattelan@redhat.com \
--cc=hch@infradead.org \
--cc=kanderso@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pcaulfie@redhat.com \
--cc=teigland@redhat.com \
/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
all inboxes | Powered by JetHome®