From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] nfs-utils patches
Date: Wed, 17 Dec 2008 15:24:09 -0500 [thread overview]
Message-ID: <49495FE9.1030209@RedHat.com> (raw)
In-Reply-To: <20081211182820.6882.20716.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
Chuck Lever wrote:
> Hi Steve-
>
> Three more patches for nfs-utils in the IPv6 series.
>
> The first is a minor bug fix for the sm-notify command, since we've
> been focusing on that area recently. It fixes a use-after-free.
>
> The next two don't add new IPv6 functionality, but are prerequisites.
> The first adds a new string parsing API that specifically handles
> mount options that take a numeric value. The second changes the
> handler for one such option (retry= in this case) to use the new API.
>
> Subsequent patches will make use of this new API to handle mount
> options that are used to fill in pmap structs.
>
> ---
>
> Chuck Lever (3):
> text-based mount command: use po_get_numeric() for handling retry=
> text-based mount command: add function to parse numeric mount options
> sm-notify command: fix a use-after-free bug
Committed....
steved.
prev parent reply other threads:[~2008-12-17 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 18:33 [PATCH 0/3] nfs-utils patches Chuck Lever
[not found] ` <20081211182820.6882.20716.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-12-11 18:33 ` [PATCH 1/3] sm-notify command: fix a use-after-free bug Chuck Lever
2008-12-11 18:33 ` [PATCH 2/3] text-based mount command: add function to parse numeric mount options Chuck Lever
2008-12-11 18:33 ` [PATCH 3/3] text-based mount command: use po_get_numeric() for handling retry= Chuck Lever
2008-12-17 20:24 ` Steve Dickson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49495FE9.1030209@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.