From: Peter Zijlstra <peterz@infradead.org>
To: Liljestrand Hans <ishkamiel@gmail.com>
Cc: "Reshetova, Elena" <elena.reshetova@intel.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Greg KH <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
"will.deacon@arm.com" <will.deacon@arm.com>,
Boqun Feng <boqun.feng@gmail.com>,
David Windsor <dwindsor@gmail.com>,
"aik@ozlabs.ru" <aik@ozlabs.ru>,
"david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
Subject: [kernel-hardening] Re: Conversion from atomic_t to refcount_t: summary of issues
Date: Tue, 10 Jan 2017 15:58:29 +0100 [thread overview]
Message-ID: <20170110145829.GB5680@worktop> (raw)
In-Reply-To: <1482247208.28665.121.camel@cs-046.org.aalto.fi>
On Tue, Dec 20, 2016 at 05:20:08PM +0200, Liljestrand Hans wrote:
> fs/inode.c:813 find_inode_fast
>
> This seems to be doing a search for freed up objects that are then
> reused, maybe. Not sure if we can guarantee the refcount is 0, nor if it
> would be appropriate to use refcount_set even if we could?
This one is actually quite difficult. I'll try and poke at it some.
next prev parent reply other threads:[~2017-01-10 14:58 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 11:56 [kernel-hardening] Conversion from atomic_t to refcount_t: summary of issues Reshetova, Elena
2016-11-28 12:13 ` [kernel-hardening] " Peter Zijlstra
2016-11-28 12:44 ` Peter Zijlstra
2016-11-28 12:48 ` Peter Zijlstra
2016-11-28 14:12 ` [kernel-hardening] " Reshetova, Elena
2016-11-29 3:19 ` [kernel-hardening] " Alexey Kardashevskiy
2016-11-29 9:31 ` Peter Zijlstra
2016-11-30 0:23 ` Alexey Kardashevskiy
2016-11-29 15:35 ` [kernel-hardening] " Reshetova, Elena
2016-11-29 15:47 ` Peter Zijlstra
2016-12-01 19:15 ` [kernel-hardening] " Peter Zijlstra
2016-12-01 21:31 ` David Windsor
2016-12-01 23:03 ` Peter Zijlstra
2016-12-01 23:20 ` Kees Cook
2016-12-01 23:29 ` David Windsor
2016-12-02 1:17 ` Boqun Feng
2016-12-02 20:25 ` David Windsor
2016-12-07 13:24 ` Peter Zijlstra
2016-12-07 19:03 ` David Windsor
2016-12-09 14:48 ` David Windsor
2016-12-07 13:36 ` Peter Zijlstra
2016-12-01 23:20 ` David Windsor
2016-12-07 13:21 ` Peter Zijlstra
2016-12-02 15:44 ` Liljestrand Hans
2016-12-02 16:14 ` Greg KH
2016-12-07 13:52 ` Peter Zijlstra
2016-12-07 15:59 ` David Windsor
2016-12-07 16:26 ` Peter Zijlstra
2016-12-07 16:31 ` David Windsor
2016-12-16 12:10 ` [kernel-hardening] " Reshetova, Elena
2016-12-16 14:01 ` [kernel-hardening] " Peter Zijlstra
2016-12-19 7:55 ` [kernel-hardening] " Reshetova, Elena
2016-12-19 10:12 ` [kernel-hardening] " Peter Zijlstra
2016-12-20 9:13 ` [kernel-hardening] " Reshetova, Elena
2016-12-20 9:30 ` [kernel-hardening] " Greg KH
2016-12-20 9:40 ` [kernel-hardening] " Reshetova, Elena
2016-12-20 9:51 ` [kernel-hardening] " Greg KH
2016-12-20 9:55 ` [kernel-hardening] " Reshetova, Elena
2016-12-20 10:26 ` [kernel-hardening] " Greg KH
2016-12-20 9:41 ` Peter Zijlstra
2016-12-20 9:58 ` [kernel-hardening] " Reshetova, Elena
2016-12-20 10:55 ` [kernel-hardening] " Liljestrand Hans
2016-12-20 13:13 ` Peter Zijlstra
2016-12-20 13:35 ` Reshetova, Elena
2016-12-20 15:20 ` Liljestrand Hans
2016-12-20 15:52 ` Peter Zijlstra
2017-01-10 14:58 ` Peter Zijlstra [this message]
2016-12-07 14:13 ` Peter Zijlstra
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=20170110145829.GB5680@worktop \
--to=peterz@infradead.org \
--cc=aik@ozlabs.ru \
--cc=boqun.feng@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ishkamiel@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.