From: Peter Zijlstra <peterz@infradead.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Elena Reshetova <elena.reshetova@intel.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <h.peter.anvin@intel.com>,
Will Deacon <will.deacon@arm.com>,
David Windsor <dwindsor@gmail.com>
Subject: [kernel-hardening] Re: [RFCv2 PATCH 00/18] refcount_t API + usage
Date: Thu, 19 Jan 2017 09:52:14 +0100 [thread overview]
Message-ID: <20170119085214.GG6485@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170118203534.GA22446@kroah.com>
On Wed, Jan 18, 2017 at 09:35:34PM +0100, Greg KH wrote:
> I think the refcount_t patch should also go to tip given it depends on
> the kref patches. But that's up to Peter, he would know best...
Yeah, so I held back on that and the kref conversion, because I wanted
to get the kref fixup thingies in first. If there's no fallout from that
I can stuff in the refcount_t bits.
next prev parent reply other threads:[~2017-01-19 8:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:11 [kernel-hardening] [RFCv2 PATCH 00/18] refcount_t API + usage Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 01/18] kref: Add KREF_INIT() Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 02/18] kref: Add kref_read() Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 03/18] kref: Kill kref_sub() Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 04/18] kref: Use kref_get_unless_zero() more Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 05/18] kref: Implement kref_put_lock() Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 06/18] kref: Avoid more abuse Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 07/18] kref: Implement using refcount_t Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 08/18] kernel, mm: convert from atomic_t to refcount_t Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 09/18] net: " Elena Reshetova
2017-01-18 18:39 ` [kernel-hardening] " David Windsor
2017-01-19 1:11 ` Kees Cook
2017-01-19 3:29 ` David Windsor
2017-01-19 7:48 ` Reshetova, Elena
2017-01-19 15:08 ` David Windsor
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 10/18] fs: " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 11/18] security: " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 12/18] sound: " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 13/18] ipc: covert " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 14/18] tools: convert " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 15/18] block: " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 16/18] drivers: net " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 17/18] drivers: misc drivers " Elena Reshetova
2017-01-18 9:11 ` [kernel-hardening] [RFCv2 PATCH 18/18] drivers: infiniband " Elena Reshetova
2017-01-18 10:30 ` [kernel-hardening] Re: [RFCv2 PATCH 00/18] refcount_t API + usage Greg KH
2017-01-18 20:06 ` Kees Cook
2017-01-18 20:35 ` Greg KH
2017-01-18 20:57 ` Kees Cook
2017-01-19 8:52 ` Peter Zijlstra [this message]
2017-01-23 7:52 ` [kernel-hardening] " Reshetova, Elena
2017-01-23 8:36 ` [kernel-hardening] " Greg KH
2017-01-23 8:52 ` [kernel-hardening] " Reshetova, Elena
2017-01-18 21:52 ` [kernel-hardening] " Eric Biggers
2017-01-19 8:31 ` Reshetova, Elena
2017-01-19 9:19 ` Peter Zijlstra
2017-01-19 10:22 ` Reshetova, Elena
2017-01-19 12:52 ` Peter Zijlstra
2017-01-19 14:15 ` Reshetova, Elena
2017-01-19 15:20 ` [kernel-hardening] " David Windsor
2017-01-19 16:00 ` [kernel-hardening] " Reshetova, Elena
2017-01-19 19:18 ` [kernel-hardening] " Eric Biggers
2017-01-20 8:36 ` Peter Zijlstra
2017-01-20 9:20 ` Reshetova, Elena
2017-01-20 10:23 ` gregkh
2017-01-20 10:44 ` Solar Designer
2017-01-20 17:52 ` Eric Biggers
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=20170119085214.GG6485@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=h.peter.anvin@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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.