From: Peter Lund <firefly@vax64.dk>
To: Christoph Lameter <clameter@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
trivial@kernel.org, linux-kernel@vger.kernel.org,
Momchil Velikov <velco@fadata.bg>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: [PATCH] avoid negative shifts in radix-tree.c, take 2
Date: Wed, 29 Aug 2007 14:34:25 +0200 [thread overview]
Message-ID: <1188390865.7216.5.camel@localhost.localdomain> (raw)
From: Peter Lund <firefly@vax64.dk>
Negative shifts are not allowed in C (the result is undefined).
It works on most platforms but not on the VAX with gcc 4.0.1 (it results in an
"operand reserved" fault).
Applies to Linux 2.6.22.
Signed-off-by: Peter Lund <firefly@vax64.dk>
---
Shifting by more than the width of the value on the left is also not allowed.
I think the extra '>> 1' tacked on at the end in the original code was an attempt
to work around that. Getting rid of that is an extra feature of this patch.
Since the shift amount is what causes the trouble, I felt it was better to name that
value than the return value, which in any case becames much easier to read after
removal of ' - 1' and '>> 1' and naming of the shift amount.
Here's the chapter and verse, taken from the final draft of the C99 standard
("6.5.7 Bitwise shift operators", paragraph 3):
"The integer promotions are performed on each of the operands. The
type of the result is that of the promoted left operand. If the
value of the right operand is negative or is greater than or equal
to the width of the promoted left operand, the behavior is
undefined."
Thank you to Jan-Benedict Glaw and Christoph Hellwig for review.
I could change the indentation so the variables and equal signs no longer line up but
I'm pretty sure that would not be an improvement.
I could also remove the else and unindent the second return statement but isn't that
just a matter of personal taste?
--- linux-2.6.22/lib/radix-tree.c.orig 2007-08-27 15:42:37.000000000 +0200
+++ linux-2.6.22/lib/radix-tree.c 2007-08-29 13:19:19.000000000 +0200
@@ -980,12 +980,13 @@
static __init unsigned long __maxindex(unsigned int height)
{
- unsigned int tmp = height * RADIX_TREE_MAP_SHIFT;
- unsigned long index = (~0UL >> (RADIX_TREE_INDEX_BITS - tmp - 1)) >> 1;
+ unsigned int width = height * RADIX_TREE_MAP_SHIFT;
+ int shift = RADIX_TREE_INDEX_BITS - width;
- if (tmp >= RADIX_TREE_INDEX_BITS)
- index = ~0UL;
- return index;
+ if (shift < 0)
+ return ~0UL;
+ else
+ return ~0UL >> shift;
}
static __init void radix_tree_init_maxindex(void)
next reply other threads:[~2007-08-29 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 12:34 Peter Lund [this message]
2007-08-29 12:47 ` [PATCH] avoid negative shifts in radix-tree.c, take 2 Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1188390865.7216.5.camel@localhost.localdomain \
--to=firefly@vax64.dk \
--cc=clameter@sgi.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=trivial@kernel.org \
--cc=velco@fadata.bg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.