https://bugzilla.novell.com/show_bug.cgi?id=231845 nfbrown@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #18 from nfbrown@novell.com 2007-04-29 19:43 MST ------- Unfortuantely the tcpdump is useless - it is always best to use "-w filename" to create a binary dump, and use "-s 0" to capture full packets. I doesn't really matter though - I managed to do some testing myself and think I can fix it. I have posted a discussion of the problem and a possible solution to the nfs community mailing list to get feedback from people who are more familiar with the code. The patch below fixes the symptom and I think it is safe, but it is the safety that I want feedback on. Stay tuned... diff .prev/fs/lockd/clntproc.c ./fs/lockd/clntproc.c --- .prev/fs/lockd/clntproc.c 2007-04-30 10:41:01.000000000 +1000 +++ ./fs/lockd/clntproc.c 2007-04-30 11:10:08.000000000 +1000 @@ -134,7 +134,7 @@ static void nlmclnt_setlockargs(struct n lock->oh.len = snprintf(req->a_owner, sizeof(req->a_owner), "%u@%s", (unsigned int)fl->fl_u.nfs_fl.owner->pid, utsname()->nodename); - lock->svid = fl->fl_u.nfs_fl.owner->pid; + lock->svid = 42; lock->fl.fl_start = fl->fl_start; lock->fl.fl_end = fl->fl_end; lock->fl.fl_type = fl->fl_type; -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.