linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: Fix "kernel BUG at fs/nfs/nfs3xdr.c:1338!"
Date: Thu, 20 Jan 2011 22:11:17 +0100	[thread overview]
Message-ID: <4D38A4F5.8070904@redhat.com> (raw)
In-Reply-To: <20110120191639.3122.24837.stgit@matisse.1015granger.net>

On 01/20/2011 08:18 PM, Chuck Lever wrote:
> Milan Broz <mbroz@redhat.com> reports:

>> [  105.327979] kernel BUG at fs/nfs/nfs3xdr.c:1338!

> 
> nfs3_xdr_enc_setacl3args() is not properly setting up the target
> buffer before nfsacl_encode() attempts to encode the ACL.
> 
> Introduced by commit d9c407b1 "NFS: Introduce new-style XDR encoding
> functions for NFSv3."

Yes, patch fixes the problem for me.

Thanks,
Milan

      reply	other threads:[~2011-01-20 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 19:18 [PATCH] NFS: Fix "kernel BUG at fs/nfs/nfs3xdr.c:1338!" Chuck Lever
2011-01-20 21:11 ` Milan Broz [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=4D38A4F5.8070904@redhat.com \
    --to=mbroz@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).