[PATCH 00/14] Prepare for fallback and fg/bg support in text mounts

[PATCH 00/14] Prepare for fallback and fg/bg support in text mounts

[Chuck Lever]

Hi Neil-

Here's a refresh of the patch series to prepare nfs-utils for introducing
support for version/protocol fallback and fg/bg to text-based NFS mounts.

This series addresses some minor memory leaks, adds comments and new error
reporting functions, and fixes a handful of umount misbehaviors.

-- 
corporate:    <chuck dot lever at oracle dot com>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: [PATCH 00/14] Prepare for fallback and fg/bg support in text mounts

[Neil Brown]

On Monday September 24, chuck.lever@oracle.com wrote:
> Hi Neil-
> 
> Here's a refresh of the patch series to prepare nfs-utils for introducing
> support for version/protocol fallback and fg/bg to text-based NFS mounts.
> 
> This series addresses some minor memory leaks, adds comments and new error
> reporting functions, and fixes a handful of umount misbehaviors.

Thanks.  all applied.

I still don't think there is any point calling "free" just before
"exit" (patches 5 and 6) but it doesn't hurt....

NeilBrown

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: [PATCH 00/14] Prepare for fallback and fg/bg support in text mounts

[Chuck Lever]

[-- Attachment #1: Type: text/plain, Size: 464 bytes --]

Neil Brown wrote:
> I still don't think there is any point calling "free" just before
> "exit" (patches 5 and 6) but it doesn't hurt....

Granted, I'm being paranoid there.  I have a few goals:

1.  Consistently use a defensive coding style to help prevent the 
introduction of new leaks;

2.  We want a clean baseline valgrind report so we can see newly 
introduced leaks easily, because:

3.  We don't want a memory leak during long-running backgrounded mounts.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs