mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc4: Disable __compiletime_object_size for GCC 4.6+
Date: Wed, 13 Nov 2013 10:39:13 -0800	[thread overview]
Message-ID: <20131113183913.GK4994@outflux.net> (raw)
In-Reply-To: <1365821348-7177-1-git-send-email-linux@roeck-us.net>

Hi Guenter,

On Fri, Apr 12, 2013 at 07:49:08PM -0700, Guenter Roeck wrote:
> __builtin_object_size is known to be broken on gcc 4.6+.
> See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48880 for details.
> 
> This causes unnecssary build warnings and errors such as
> 
> In function 'copy_from_user', inlined from 'sb16_copy_from_user'
> 	at sound/oss/sb_audio.c:878:22:
> arch/x86/include/asm/uaccess_32.h:211:26: error: call to 'copy_from_user_overflow'
> 	declared with attribute error: copy_from_user() buffer size is not provably correct
> make[3]: [sound/oss/sb_audio.o] Error 1 (ignored)
> 
> Disable it where broken.

Is there an alternative? This means that things like
DEBUG_STRICT_USER_COPY_CHECKS are being rendered useless. I don't think
this is _always_ broken, just under certain situations, right?

-Kees

> 
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
>  include/linux/compiler-gcc4.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/compiler-gcc4.h b/include/linux/compiler-gcc4.h
> index 68b162d..842de22 100644
> --- a/include/linux/compiler-gcc4.h
> +++ b/include/linux/compiler-gcc4.h
> @@ -13,7 +13,7 @@
>  #define __must_check 		__attribute__((warn_unused_result))
>  #define __compiler_offsetof(a,b) __builtin_offsetof(a,b)
>  
> -#if GCC_VERSION >= 40100
> +#if GCC_VERSION >= 40100 && GCC_VERSION < 40600
>  # define __compiletime_object_size(obj) __builtin_object_size(obj, 0)
>  #endif
>  
> -- 
> 1.7.9.7
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Kees Cook
Chrome OS Security

  reply	other threads:[~2013-11-13 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13  2:49 Guenter Roeck
2013-11-13 18:39 ` Kees Cook [this message]
2013-11-13 20:24   ` Guenter Roeck
2013-11-13 20:57   ` H. Peter Anvin
2013-11-14  1:19     ` Guenter Roeck

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=20131113183913.GK4994@outflux.net \
    --to=keescook@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®