On Sunday August 3, [EMAIL PROTECTED] wrote:
I can trigger it reliably with a 2.6.26 client. I've also triggered it
with 496d6c32d4d057cb44272d9bd587ff97d023ee92 reverted on the server.
It's harder to trigger with 2.6.27-rc1+ but I managed to get an Oops
on the fourth build after three
On Monday August 4, [EMAIL PROTECTED] wrote:
Neil Brown [EMAIL PROTECTED] writes:
What filesystem is being exported here?
Boring old ext3 (on LVM, on dm-crypt).
Good. That makes it easier.
Can you get an assembly version of exportfs_decode_fh, so we can check
what is happening
On Wednesday September 12, [EMAIL PROTECTED] wrote:
On Wednesday 12 September 2007 20:01, Greg KH wrote:
On Wed, Sep 12, 2007 at 07:32:07AM +0200, Robert Schwebel wrote:
On Tue, Sep 11, 2007 at 11:43:17AM +0200, Heiko Schocher wrote:
I have developed a device driver and use the sysFS to
