linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@gmail.com>
To: hirofumi@mail.parknet.co.jp, akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Namjae Jeon <linkinjeon@gmail.com>,
	Namjae Jeon <namjae.jeon@samsung.com>
Subject: [PATCH v6 0/7] fat (exportfs): support stale_rw and nostale_ro mount options.
Date: Sun, 10 Feb 2013 00:01:21 +0900	[thread overview]
Message-ID: <1360422081-12144-1-git-send-email-linkinjeon@gmail.com> (raw)

From: Namjae Jeon <namjae.jeon@samsung.com>

This patch set eliminates the client side ESTALE errors when a FAT partition
exported over NFS has it's dentries evicted from the cache. The idea is to
find the on-disk location_'i_pos' of the dirent of the inode that has been
evicted and use it to rebuild the inode.

Change log
v6:
Dummy inode approach to eliminate custom function fat_traverse_cluster().

v5:
Modified  fat_ent_read() arguments so that the custom function 
fat_read_next_clus() can be eliminated.

v(no name):
Define two nfs export_operation structures, one for 'stale_rw' mounts and 
the other for 'nostale_ro'

fat_nfs_get_inode does not hold i_mutex of parent directory. So introduce
fat_lock_build_inode().

v4:
Instead of assigning i_pos to inode->i_ino, assign it to kstat->ino

v3:
Dropped busy-list approach and made the filesystem read only when
rebuilding evicted inodes, by providing stale_rw and nostale_ro mount options
 
v2:
Introduced a list of busy i_pos values for inodes that are unlinked but
having open file handles. Did this to avoid assigning such i_pos values to new
files created at same location.

v1:
Permanent inode number based approach by assigning i_pos to i_ino.
Added custom function fat_read_next_clus() and  fat_traverse_cluster()
to read disk entries.

Namjae Jeon (7):
  fat: Introduce 2 new values for the -o nfs mount option
  fat: move fat_i_pos_read to fat.h
  fat: introduce a helper fat_get_blknr_offset()
  fat: restructure export_operations
  fat (exportfs): rebuild inode if ilookup() fails
  fat (exportfs): rebuild directory-inode if fat_dget() fails
  Documentation: update nfs option in filesystem/vfat.txt
-- 
1.7.9.5

                 reply	other threads:[~2013-02-09 15:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1360422081-12144-1-git-send-email-linkinjeon@gmail.com \
    --to=linkinjeon@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.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;
as well as URLs for NNTP newsgroup(s).