linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Windsor <dwindsor@gmail.com>
To: linux-nfs@vger.kernel.org, netdev@vger.kernel.org
Cc: kernel-hardening@lists.openwall.com, bfields@fieldses.org,
	jlayton@poochiereds.net, keescook@chromium.org,
	elena.reshetova@intel.com, dwindsor@gmail.com
Subject: [RFC][PATCH] nfsd: add +1 to reference counting scheme for struct nfsd4_session
Date: Thu,  9 Feb 2017 02:38:21 -0500	[thread overview]
Message-ID: <1486625901-10094-1-git-send-email-dwindsor@gmail.com> (raw)

In furtherance of the KSPP effort to add overflow protection to kernel
reference counters, a new type (refcount_t) and API have been created.
Part of the refcount_t API is refcount_inc(), which will not increment a
refcount_t variable if its value is 0 (as this would indicate a possible
use-after-free condition). 

In auditing the kernel for refcounting corner cases, we've come across the
case of struct nfsd4_session.  

             reply	other threads:[~2017-02-11  6:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  7:38 David Windsor [this message]
2017-02-11  6:42 ` [RFC][PATCH] nfsd: add +1 to reference counting scheme for struct nfsd4_session David Windsor
2017-02-11 12:31   ` Jeff Layton
2017-02-11 14:01     ` David Windsor
2017-02-11 14:09       ` Jeff Layton
2017-02-13 10:38       ` Christoph Hellwig
2017-02-13 11:42         ` David Windsor
2017-02-13 12:12           ` Christoph Hellwig
2017-02-14 13:48             ` David Windsor
2017-02-12  1:15     ` Bruce Fields
2017-02-12  1:42       ` David Windsor
2017-02-13 10:54   ` [kernel-hardening] " Hans Liljestrand
2017-02-13 11:46     ` David Windsor
2017-02-15 16:45       ` Bruce Fields

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=1486625901-10094-1-git-send-email-dwindsor@gmail.com \
    --to=dwindsor@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=elena.reshetova@intel.com \
    --cc=jlayton@poochiereds.net \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@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).