Message-ID: <40BC8824.4060809@serice.net>
Date: Tue, 01 Jun 2004 08:44:04 -0500
From: Paul Serice <paul@serice.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040127
MIME-Version: 1.0
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iso9660 inodes beyond 4GB
References: <40BB714B.8050504@serice.net> <16572.868.477203.352122@cse.unsw.edu.au>
In-Reply-To: <16572.868.477203.352122@cse.unsw.edu.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 875
Lines: 27

 > 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.

Thanks, that definitely triggers an error.


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

I'm not sure who I have to thank, but the code in fs/exportfs made it
much easier than expected.


Paul Serice

-
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/