Messages in this thread Patch in this message | | | From | Jan Engelhardt <> | Subject | [PATCH] rcu: avoid checking for constant | Date | Thu, 12 Jan 2012 06:11:44 +0100 |
| |
When compiling kernel or module code with -O0, "offset" is no longer considered a constant, and therefore always triggers the build error that BUILD_BUG_ON is defined to yield.
What is the rationale between the forced constant check, introduced in 9ab1544eb4196ca8d05c433b2eb56f74496b1ee3?
Signed-off-by: Jan Engelhardt <jengelh@medozas.de> --- include/linux/rcupdate.h | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h index 2cf4226..38c5ba5 100644 --- a/include/linux/rcupdate.h +++ b/include/linux/rcupdate.h @@ -805,8 +805,6 @@ void __kfree_rcu(struct rcu_head *head, unsigned long offset) { typedef void (*rcu_callback)(struct rcu_head *); - BUILD_BUG_ON(!__builtin_constant_p(offset)); - /* See the kfree_rcu() header comment. */ BUILD_BUG_ON(!__is_kfree_rcu_offset(offset)); -- 1.7.7
| |