Re: [NFS] Re: [NFS client] NFS locks not released on abnormal process termination

From: Philippe Troin (phil_at_fifi.org)
Date: 12/09/03

  • Next message: Oliver Hunt: "Re: udev sysfs docs Re: State of devfs in 2.6?"
    To: "Chris Croswhite" <csc@cadence.com>
    Date: 	09 Dec 2003 11:26:48 -0800
    
    

    "Chris Croswhite" <csc@cadence.com> writes:

    > Philippe,
    >
    > What patches are you refering to?

    The one in <87llpms8yr.fsf@ceramic.fifi.org> named
    linux-2.4.23-nfs-lock-race-2.patch

    Here a link to MARC, since the sourceforge mailing list web page
    sucks:

      http://marc.theaimsgroup.com/?l=linux-nfs&m=107095817723325&w=2

    Phil.

    > -----Original Message-----
    > From: Philippe Troin [mailto:phil@fifi.org]
    > Sent: Tue 09-Dec-03 10:46
    > To: Trond Myklebust
    > Cc: Kenny Simpson; linux-kernel@vger.kernel.org; nfs@lists.sourceforge.net
    > Subject: [NFS] Re: [NFS client] NFS locks not released on abnormal process termination
    > Trond Myklebust <trond.myklebust@fys.uio.no> writes:
    >
    > > >>>>> " " == Philippe Troin <phil@fifi.org> writes:
    > >
    > > > From my reading of the patch, it supersedes the old patch, and
    > > > is only
    > > > necessary on the client. Is also does not compile :-)
    > >
    > > Yeah, I admit I didn't test it out...
    > >
    > > > Here's an updated patch which does compile.
    > >
    > > Thanks.
    > >
    > > > I am still running tests, but so far it looks good (that is all
    > > > locks are freed when a process with locks running on a NFS
    > > > client is killed).
    > >
    > > Good...
    >
    > I've ran test overnight on four boxen, and no locks were lost.
    > I guess you can send this patch to Marcello now.
    >
    > I've tested with the enclosed program.
    >
    >
    > > There are still 2 other issues with the generic POSIX locking code.
    > > Both issues have to do with CLONE_VM and have been raised on
    > > linux-kernel & linux-fsdevel. Unfortunately they met with no response,
    > > so I'm unable to pursue...
    >
    > Can we help? Pointers?
    >
    > Phil.
    >
    >
    >
    >
    >
    > -------------------------------------------------------
    > This SF.net email is sponsored by: SF.net Giveback Program.
    > Does SourceForge.net help you be more productive? Does it
    > help you create better code? SHARE THE LOVE, and help us help
    > YOU! Click Here: http://sourceforge.net/donate/
    > _______________________________________________
    > NFS maillist - NFS@lists.sourceforge.net
    > https://lists.sourceforge.net/lists/listinfo/nfs
    -
    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/


  • Next message: Oliver Hunt: "Re: udev sysfs docs Re: State of devfs in 2.6?"

    Relevant Pages

    • Re: Memory leak in 2.6.11-rc1?
      ... > I've just checked Phil's mails - both Phil and myself are using ... > netfilter on the troublesome boxen. ... > is not empty in all cases so far where ip_fragmenthas been called. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Slow I/O with SMP, Fusion-MPT and u160 SCSI JBOD
      ... Phil, ... What happens if you pull 1gb or 2gb of memory from your box? ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: xor as a lazy comparison
      ... The cycles saved for old compilers is not rational to ... >> have obfuscated code. ... Phil. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Process start times moving in reverse on 2.6.8.1
      ... >> it is a gradual drift. ... I'd say this is a keeper, but can track it longer if you prefer. ... Phil ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)