Re: corrupted rpc message on GSS_DESTROY

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2012-04-06 at 23:56 +0200, Tigran Mkrtchyan wrote:
> Hi,
> 
> We are still see issued described in:
> 
> http://www.spinics.net/lists/linux-nfs/msg22142.html
> 
> Now even the see partial context.
> By looking at kernel's GSS implementation I see following:
> 
> The auth_gss.c:gss_marshal() in some cases may return NULL.
> The NULL value is passed to xdr_adjust_iovec() which
> calculates message length as:
> 
>  return iov->iov_len = ((u8 *) p - (u8 *) iov->iov_base);
> 
> where p is NULL in such case.  I don't think it's an expected
> behavior.

As far as I can see, a zero reply in gss_marshal() results in
rpc_xdr_encode() printing "RPC: couldn't encode RPC header, exit EIO"
and then calling rpc_exit(). I don't see how that could result in a
corrupted buffer.

Cheers
  Trond
-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com

��.n��������+%������w��{.n�����{��w���jg��������ݢj����G�������j:+v���w�m������w�������h�����٥



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux