lkml.org 
[lkml]   [2004]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH] iso9660 inodes beyond 4GB
On Monday May 31, paul@serice.net wrote:
> This is my third attempt to patch the isofs code. It is a completely
> different patch from the previous two. I do not think there are any
> trade-offs with this patch.
snip
>
> Lastly, the current code uses the default export_operations to handle
> accessing the file system through NFS. The problem with this is that
> the default NFS operations assume that iget() works which is no longer
> the case because of the necessary switch to iget5_locked(). So, I had
> to implement the NFS operations too.
>
> I did not, however, implement the NFS get_parent() method. So, the
> default method which just returns an error is used. This is not a
> reduction in functionality because the current code also uses the
> default method. If someone can explain what I need to do to trigger
> this error, I will gladly try to implement the method.
>

The easiest way to trigger the error is:
export the filesystem and mount it on some client.
On the client, cd into some subdirectory.
On the server, unexport, unmount, remount, reexport
(i.e. simulate a reboot).
On the client "ls -l"

That should cause the server to try to call get_parent to find the
path back up to the root of the filesystem.

A quick glance at the rest of the export related code suggests that it
is all ok.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:03    [W:0.169 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site