linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Jeff Garzik <jeff@garzik.org>,
	open-osd mailing-list <osd-dev@open-osd.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
	Marcin Slusarz <marcin.slusarz@gmail.com>
Subject: [PATCHSET 0/3] exofs: Exportable by NFS
Date: Wed, 25 Mar 2009 11:45:18 +0200	[thread overview]
Message-ID: <49C9FD2E.3030201@panasas.com> (raw)


I'm adding three more patches to the exofs tree to be submitted for 2.6.30

With these patches I'm able to export an exofs filesystem via NFS and
pass Connectathon tests. The test exposed the 2G bug which is
fixed with a one liner in patch 2.

List of patches:
[PATCH 1/3] [SQUASHME] prints in hex

  Offsets and length should be printed in HEX for
  easier debugging, when they get big.
  (This patch will be squashed into the appropriate place
  in the original patchset)

[PATCH 2/3] [SQUASHME] exofs does support 64bit file sizes

  This fixes the BUG exposed by the Connectathon test. The Kernel
  assumes 32-bitness for filesystems unless told otherwise.
  (This patch will be squashed into the appropriate place
  in the original patchset)

[PATCH 3/3] exofs: export_operations

  In this patch we implement the export_operations vector
  to enable NFS
  (This patch is added to the original set)



Thanks for reviewing
Boaz

             reply	other threads:[~2009-03-25  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  9:45 Boaz Harrosh [this message]
2009-03-25  9:47 ` [PATCH 1/3] [SQUASHME] prints in hex Boaz Harrosh
2009-03-25  9:50 ` [PATCH 2/3] [SQUASHME] exofs does support 64bit file sizes Boaz Harrosh
2009-03-25 10:07 ` [PATCH 3/3] exofs: export_operations Boaz Harrosh

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=49C9FD2E.3030201@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=osd-dev@open-osd.org \
    --cc=zbr@ioremap.net \
    /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).