[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0ea832fa-de39-47fa-8666-5743a68a8519@kadam.mountain>
Date: Thu, 3 Aug 2023 12:08:32 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Su Hui <suhui@...china.com>, chuck.lever@...cle.com,
jlayton@...nel.org, neilb@...e.de, kolga@...app.com,
Dai.Ngo@...cle.com, tom@...pey.com,
trond.myklebust@...merspace.com, anna@...nel.org,
nathan@...nel.org, trix@...hat.com, bfields@...ldses.org,
linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] fs: lockd: avoid possible wrong NULL parameter
I could have sworn there was an issue with glibc annotating these
parameters as non-NULL, but maybe it was a different function.
With the memcpy() bug in 2010, there were never any numbers to show that
it helped improve performance. The only person who measured was Linus
and it hurt performance on his laptop. So from a kernel developer
perspective it just seemed totally bonkers.
regards,
dan carpenter
Powered by blists - more mailing lists