From: "Reshetova, Elena" <elena.reshetova@intel.com>
To: "darrick.wong@oracle.com" <darrick.wong@oracle.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
David Windsor <dwindsor@gmail.com>,
Hans Liljestrand <ishkamiel@gmail.com>
Subject: RE: [PATCH 0/5] fs, xfs refcount conversions
Date: Thu, 20 Apr 2017 08:11:41 +0000 [thread overview]
Message-ID: <2236FBA76BA1254E88B949DDB74E612B41C8D726@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1488963219-11709-1-git-send-email-elena.reshetova@intel.com>
> v3:
> * fixed header file inclusion
I don't think I have heard anything back on this v3 patch set.
Is there still smth here to fix or could you take the changes in?
Best Regards,
Elena.
>
> Now when new refcount_t type and API are finally merged
> (see include/linux/refcount.h), the following
> patches convert various refcounters in the xfs susystem 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.
>
>
> Elena Reshetova (5):
> fs, xfs: convert xfs_bui_log_item.bui_refcount from atomic_t to
> refcount_t
> fs, xfs: convert xfs_efi_log_item.efi_refcount from atomic_t to
> refcount_t
> fs, xfs: convert xlog_ticket.t_ref from atomic_t to refcount_t
> fs, xfs: convert xfs_cui_log_item.cui_refcount from atomic_t to
> refcount_t
> fs, xfs: convert xfs_rui_log_item.rui_refcount from atomic_t to
> refcount_t
>
> fs/xfs/xfs_bmap_item.c | 4 ++--
> fs/xfs/xfs_bmap_item.h | 2 +-
> fs/xfs/xfs_extfree_item.c | 4 ++--
> fs/xfs/xfs_extfree_item.h | 2 +-
> fs/xfs/xfs_linux.h | 1 +
> fs/xfs/xfs_log.c | 10 +++++-----
> fs/xfs/xfs_log_priv.h | 2 +-
> fs/xfs/xfs_refcount_item.c | 4 ++--
> fs/xfs/xfs_refcount_item.h | 2 +-
> fs/xfs/xfs_rmap_item.c | 4 ++--
> fs/xfs/xfs_rmap_item.h | 2 +-
> 11 files changed, 19 insertions(+), 18 deletions(-)
>
> --
> 2.7.4
next prev parent reply other threads:[~2017-04-20 8:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 8:53 [PATCH 0/5] fs, xfs refcount conversions Elena Reshetova
2017-03-08 8:53 ` [PATCH 1/5] fs, xfs: convert xfs_bui_log_item.bui_refcount from atomic_t to refcount_t Elena Reshetova
2017-03-08 8:53 ` [PATCH 2/5] fs, xfs: convert xfs_efi_log_item.efi_refcount " Elena Reshetova
2017-03-08 8:53 ` [PATCH 3/5] fs, xfs: convert xlog_ticket.t_ref " Elena Reshetova
2017-03-08 15:50 ` Christoph Hellwig
2017-03-08 20:06 ` Kees Cook
2017-03-09 6:57 ` Reshetova, Elena
2017-03-08 8:53 ` [PATCH 4/5] fs, xfs: convert xfs_cui_log_item.cui_refcount " Elena Reshetova
2017-03-08 8:53 ` [PATCH 5/5] fs, xfs: convert xfs_rui_log_item.rui_refcount " Elena Reshetova
2017-04-20 8:11 ` Reshetova, Elena [this message]
2017-04-20 17:24 ` [PATCH 0/5] fs, xfs refcount conversions Darrick J. Wong
2017-04-20 22:04 ` Darrick J. Wong
2017-04-20 22:18 ` Kees Cook
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=2236FBA76BA1254E88B949DDB74E612B41C8D726@IRSMSX102.ger.corp.intel.com \
--to=elena.reshetova@intel.com \
--cc=darrick.wong@oracle.com \
--cc=dwindsor@gmail.com \
--cc=ishkamiel@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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).