From: Frank van Maarseveen <frankvm@frankvm.com>
To: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: 3.17.x 3.18.x nfs_permission(): put_rpccred() missing?
Date: Sun, 21 Dec 2014 12:40:15 +0100 [thread overview]
Message-ID: <20141221114015.GA25387@janus> (raw)
While updating the nfs-ngroups patch for 3.17 and 3.18 I noticed that
nfs_permission() seems to be missing a put_rpccred() call in the non
-ECHILD path.
--
Frank
next reply other threads:[~2014-12-21 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 11:40 Frank van Maarseveen [this message]
2014-12-22 16:21 ` 3.17.x 3.18.x nfs_permission(): put_rpccred() missing? Trond Myklebust
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=20141221114015.GA25387@janus \
--to=frankvm@frankvm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox