Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: tbJyrsBoJ6zNq1MIF6GSafk0WrkujB8cpxDse7DEw8IXwalltcGTkSUnjJsLcc13wHO1PoBsh3
 7iU33Ph7+1xw==
IronPort-SDR: EEk656pFV1uNDBCGprNQhPevw6EfpvA1RDD63LTK2PuJZ3ETOlVEEMnL/EiVDG6szj7HENFzjC
 aEcjIo2Osqsg==
From:   "Reshetova, Elena" <elena.reshetova@intel.com>
To:     Kees Cook <keescook@chromium.org>
CC:     Xiaoming Ni <nixiaoming@huawei.com>,
        Peter Zijlstra <peterz@infradead.org>,
        David Windsor <dwindsor@gmail.com>,
        Hans Liljestrand <ishkamiel@gmail.com>,
        Paul Moore <paul@paul-moore.com>,
        "edumazet@google.com" <edumazet@google.com>,
        "paulmck@kernel.org" <paulmck@kernel.org>,
        David Howells <dhowells@redhat.com>,
        "shakeelb@google.com" <shakeelb@google.com>,
        James Morris <jamorris@linux.microsoft.com>,
        "alex.huangjianhui@huawei.com" <alex.huangjianhui@huawei.com>,
        "dylix.dailei@huawei.com" <dylix.dailei@huawei.com>,
        "chenzefeng2@huawei.com" <chenzefeng2@huawei.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/3] Convert nsproxy, groups, and creds to refcount_t
Thread-Topic: [PATCH 0/3] Convert nsproxy, groups, and creds to refcount_t
Thread-Index: AQHWQOg7pvDM2vjI7kmUTaz/F8Qw8ajY8l4AgAAdh4CAABsdYIAA0yOAgAQFDHA=
Date:   Thu, 18 Jun 2020 07:39:31 +0000
Message-ID: <CY4PR1101MB23267DC8D2B1232744A5D6DCE79B0@CY4PR1101MB2326.namprd11.prod.outlook.com>
References: <20200612183450.4189588-1-keescook@chromium.org>
 <7be4d56b-0406-099b-e505-02e074c5173e@huawei.com>
 <202006142054.C00B3E9C9@keescook>
 <CY4PR1101MB23261B27ACF9D7FBC3969318E79C0@CY4PR1101MB2326.namprd11.prod.outlook.com>
 <202006151108.5B25D5A31@keescook>
In-Reply-To: <202006151108.5B25D5A31@keescook>
Accept-Language: en-US
Content-Language: en-US
dlp-version: 11.2.0.6
dlp-product: dlpe-windows
dlp-reaction: no-action
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e7ba76e3-73b0-4448-49fe-08d8135abcfb
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jun 2020 07:39:31.1034
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /u5j23VXjsL6uce9Rh+2Arn7OWMXjyjuf2aodCNKL0oq9rC/0eRYbTIAaRGOUazylCtFgpWm6evxzb+EcJGFuQxWY4iDjiDimaNOnzndHOE=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1287
X-OriginatorOrg: intel.com
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> > I have these ones also here in case anyone is interested:
> > https://github.com/ereshetova/linux-stable/commits/refcount_t_fs
> > https://github.com/ereshetova/linux-stable/commits/refcount_t_block
> >
> > They haven't been rebased for a while, but if there is an interest,
> > I can certainly do it.
>=20
> That would be great; yes!

Here are leftover pieces now rebased on top of next/stable:

https://github.com/ereshetova/linux-stable/commits/refcount_t_fs
https://github.com/ereshetova/linux-stable/commits/refcount_t_block

Haven't tested them beyond allyesconfig compile through...

There are also mm pieces (ignore bdi_writeback_congested.refcnt as it is al=
ready done)
 that were sent originally here:
https://lore.kernel.org/lkml/1487671124-11188-1-git-send-email-elena.reshet=
ova@intel.com/
But especially mm_struct pieces would need a new look and proper=20
checks.=20
Again, happy to do them also on a separate branch, if there is an interest =
to merge
them (I expect mm_struct to be much more sensitive structure for such chang=
es).

Best Regards,
Elena