[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190804124820.GH4832@mtr-leonro.mtl.com>
Date: Sun, 4 Aug 2019 15:48:20 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Chuhong Yuan <hslester96@...il.com>
Cc: Saeed Mahameed <saeedm@...lanox.com>,
"David S . Miller" <davem@...emloft.net>,
Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...pe.ca>, linux-rdma@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Use refcount_t for refcount
On Fri, Aug 02, 2019 at 08:10:35PM +0800, Chuhong Yuan wrote:
> Reference counters are preferred to use refcount_t instead of
> atomic_t.
> This is because the implementation of refcount_t can prevent
> overflows and detect possible use-after-free.
>
> First convert the refcount field to refcount_t in mlx5/driver.h.
> Then convert the uses to refcount_() APIs.
You can't do it, because you need to ensure that driver compiles and
works between patches. By converting driver.h alone to refcount_t, you
simply broke mlx5 driver.
NAK, to be clear.
And please don't sent series of patches as standalone patches.
Thanks,
Powered by blists - more mailing lists