LKML Archive on
help / color / mirror / Atom feed
* [PATCH] docs: deprecated.rst: Clarify open-coded arithmetic with literals
@ 2021-08-27 17:12 Len Baker
  2021-08-27 19:06 ` Joe Perches
  0 siblings, 1 reply; 4+ messages in thread
From: Len Baker @ 2021-08-27 17:12 UTC (permalink / raw)
  To: Jonathan Corbet, Kees Cook
  Cc: Len Baker, Gustavo A. R. Silva, Joe Perches, linux-doc,
	linux-kernel, linux-hardening

Although using literals for size calculation in allocator arguments may
be harmless due to compiler warnings in case of overflows, it is better
to refactor the code to avoid the use of open-coded math idiom.

So, clarify the preferred way in these cases.

Suggested-by: Kees Cook <>
Signed-off-by: Len Baker <>
 Documentation/process/deprecated.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/process/deprecated.rst b/Documentation/process/deprecated.rst
index 9d83b8db8874..fdfafdefe296 100644
--- a/Documentation/process/deprecated.rst
+++ b/Documentation/process/deprecated.rst
@@ -60,7 +60,8 @@ smaller allocation being made than the caller was expecting. Using those
 allocations could lead to linear overflows of heap memory and other
 misbehaviors. (One exception to this is literal values where the compiler
 can warn if they might overflow. Though using literals for arguments as
-suggested below is also harmless.)
+suggested below is also harmless. So, the preferred way in these cases is
+to refactor the code to keep the open-coded math idiom out.)

 For example, do not use ``count * size`` as an argument, as in::


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-08-29 14:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-27 17:12 [PATCH] docs: deprecated.rst: Clarify open-coded arithmetic with literals Len Baker
2021-08-27 19:06 ` Joe Perches
2021-08-27 19:22   ` Gustavo A. R. Silva
2021-08-29 14:32   ` Len Baker

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).