On 01/26/2011 10:35 AM, Chuck Lever wrote:
>
> On Jan 26, 2011, at 7:57 AM, Steve Dickson wrote:
>
>> A unallocated piece of memory, instead of a NULL point, was being
>> used to initialize a ->next point in the mount link list which
>> caused a segfault after a few remote accesses via the showmount
>> command.
>
> I thought there was a patch on the list just like this last week... in any event:
>
> Reviewed-by: Chuck Lever <chuck.lever@xxxxxxxxxx>
Thanks!
steved.
>
>
>>
>> Signed-off-by: Steve Dickson <steved@xxxxxxxxxx>
>> ---
>> utils/mountd/rmtab.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/utils/mountd/rmtab.c b/utils/mountd/rmtab.c
>> index d339296..527377f 100644
>> --- a/utils/mountd/rmtab.c
>> +++ b/utils/mountd/rmtab.c
>> @@ -205,6 +205,7 @@ mountlist_list(void)
>> }
>> if (stb.st_mtime != last_mtime) {
>> mountlist_freeall(mlist);
>> + mlist = NULL;
>> last_mtime = stb.st_mtime;
>>
>> setrmtabent("r");
>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
