[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5jKsX=0HE17JRiK-agq7R6RWg+03Ww_CaB9BzL4odLnZjA@mail.gmail.com>
Date: Tue, 4 Dec 2018 17:06:13 -0800
From: Kees Cook <keescook@...omium.org>
To: "Reshetova, Elena" <elena.reshetova@...el.com>
Cc: Ingo Molnar <mingo@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Greg KH <gregkh@...uxfoundation.org>,
Al Viro <viro@...iv.linux.org.uk>, Tejun Heo <tj@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
Li Zefan <lizefan@...wei.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Eric Paris <eparis@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Darren Hart <dvhart@...radead.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Linux-MM <linux-mm@...ck.org>, Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH 00/16] v6 kernel core pieces refcount conversions
On Wed, Nov 15, 2017 at 6:07 AM Elena Reshetova
<elena.reshetova@...el.com> wrote:
> Changes in v6:
> * memory ordering differences are outlined in each patch
> together with potential problematic areas.
> Note: I didn't include any statements in individual patches
> on why I think the memory ordering changes do not matter
> in that particular case since ultimately these are only
> known by maintainers (unless explicitly documented) and
> very hard to figure out reliably from the code.
> Therefore maintainers are expected to double check the
> specific pointed functions and make the end decision.
> * rebase on top of today's linux-next/master
*thread resurrection*
Was there a v7 for this series? I'd like to finish off any of the
known outstanding refcount_t conversions.
Thanks!
--
Kees Cook
Powered by blists - more mailing lists