[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210622000549.GA2384990@nvidia.com>
Date: Mon, 21 Jun 2021 21:05:49 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Kees Cook <keescook@...omium.org>
Cc: Yishai Hadas <yishaih@...dia.com>,
Doug Ledford <dledford@...hat.com>,
linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] IB/mlx4: Avoid field-overflowing memcpy()
On Wed, Jun 16, 2021 at 01:37:44PM -0700, Kees Cook wrote:
> In preparation for FORTIFY_SOURCE performing compile-time and run-time
> field bounds checking for memcpy(), memmove(), and memset(), avoid
> intentionally writing across neighboring array fields.
>
> Use the ether_addr_copy() helper instead, as already done for smac.
>
> Signed-off-by: Kees Cook <keescook@...omium.org>
> Reviewed-by: Leon Romanovsky <leonro@...dia.com>
> ---
> drivers/infiniband/hw/mlx4/qp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to for-next, thanks
Jason
Powered by blists - more mailing lists