From: Elena Reshetova <elena.reshetova@intel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, peterz@infradead.org,
gregkh@linuxfoundation.org, miklos@szeredi.hu,
Elena Reshetova <elena.reshetova@intel.com>
Subject: [PATCH 0/3] fs, fuse subsystem refcount conversions
Date: Fri, 3 Mar 2017 11:04:02 +0200 [thread overview]
Message-ID: <1488531845-23463-1-git-send-email-elena.reshetova@intel.com> (raw)
Now when new refcount_t type and API are finally merged
(see include/linux/refcount.h), the following
patches convert various refcounters in the fuse filesystem from atomic_t
to refcount_t. By doing this we prevent intentional or accidental
underflows or overflows that can led to use-after-free vulnerabilities.
The below patches are fully independent and can be cherry-picked separately.
Since we convert all kernel subsystems in the same fashion, resulting
in about 300 patches, we have to group them for sending at least in some
fashion to be manageable. Please excuse the long cc list.
These patches have been tested using tests supplied with libfuse.
Not sure if this is the right way to test it. No output or failures
with result to refcount conversions. refcount WARNs were on.
Elena Reshetova (3):
fs, fuse: convert fuse_file.count from atomic_t to refcount_t
fs, fuse: convert fuse_req.count from atomic_t to refcount_t
fs, fuse: convert fuse_conn.count from atomic_t to refcount_t
fs/fuse/dev.c | 10 +++++-----
fs/fuse/file.c | 8 ++++----
fs/fuse/fuse_i.h | 7 ++++---
fs/fuse/inode.c | 6 +++---
4 files changed, 16 insertions(+), 15 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-03 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 9:04 Elena Reshetova [this message]
2017-03-03 9:04 ` [PATCH 1/3] fs, fuse: convert fuse_file.count from atomic_t to refcount_t Elena Reshetova
2017-03-03 9:04 ` [PATCH 2/3] fs, fuse: convert fuse_req.count " Elena Reshetova
2017-03-03 9:04 ` [PATCH 3/3] fs, fuse: convert fuse_conn.count " Elena Reshetova
2017-03-03 16:05 ` [PATCH 0/3] fs, fuse subsystem refcount conversions Miklos Szeredi
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=1488531845-23463-1-git-send-email-elena.reshetova@intel.com \
--to=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=peterz@infradead.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).