From: Boaz Harrosh <bharrosh@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Cc: amitd <notifications@github.com>
Subject: Re: [nfs-ganesha] Fix FATAL ERROR when FS_specific attribute is missing or empty in VFS config (#8)
Date: Thu, 24 Jan 2013 17:22:34 +0200 [thread overview]
Message-ID: <510151BA.3000006@panasas.com> (raw)
In-Reply-To: <nfs-ganesha/nfs-ganesha/pull/8@github.com>
I have a fix for this in my tree, for next push
On 01/24/2013 05:08 PM, amitd wrote:
> This happened in Release build due to uninitialized variable ret in fs_specific_has()
>
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------!
---
>
>
> You can merge this Pull Request by running
>
> git pull https://github.com/amitd/nfs-ganesha fix_fs_specific_has
>
> Or view, comment on, or merge it at:
>
> https://github.com/nfs-ganesha/nfs-ganesha/pull/8
>
>
> Commit Summary
>
> * In fs_specific_has(), properly initialize ret
>
>
> File Changes
>
> * *M* src/FSAL/FSAL_VFS/export.c (3)
>
>
> Patch Links:
>
> * https://github.com/nfs-ganesha/nfs-ganesha/pull/8.patch
> * https://github.com/nfs-ganesha/nfs-ganesha/pull/8.diff
>
parent reply other threads:[~2013-01-24 15:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <nfs-ganesha/nfs-ganesha/pull/8@github.com>]
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=510151BA.3000006@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=notifications@github.com \
/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.