locking in 2.4.0-prex (was [NFS] lockdsvc: Invalid argument)

• Next message: Jamie Lokier: "Re: does anyone have a minimal opendir/readdir/closedir implementation?"
• Previous message: Kurt Garloff: "Re: Proposal: Linux Kernel Patch Management System"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> " " == Aaron T Porter <atporter@primate.net> writes:

> Hey -- I'm running 2.4.0-test6, using knfsd serving a few
> Solaris systems. When they try to write, I'm getting "Err#91
> ERESTART" which points to lockd. Trying to restart gives
> lockdsvc: Invalid argument, which Trond seems to imply[1]
> should be irrelevant, but something is obviously
> wrong. Suggestions?

Something seems to have broken with the locking changes introduced in
the 2.4.0-prex series.

The connectathon NFS test suite now causes a 'panic()' in
fs/locks.c:locks_free_lock() when running the various parent/child
locking tests.

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

• Next message: Jamie Lokier: "Re: does anyone have a minimal opendir/readdir/closedir implementation?"
• Previous message: Kurt Garloff: "Re: Proposal: Linux Kernel Patch Management System"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:20 EST