mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Yang Shi <yang.shi@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linaro-kernel@lists.linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ubsan: cosmetic fix to Kconfig text
Date: Mon, 8 Feb 2016 10:48:17 +0300	[thread overview]
Message-ID: <56B84841.7060904@virtuozzo.com> (raw)
In-Reply-To: <1454717113-5094-1-git-send-email-yang.shi@linaro.org>

On 02/06/2016 03:05 AM, Yang Shi wrote:
> When enabling UBSAN_SANITIZE_ALL, the kernel image size gets increased
> significantly (~3x). So, it sounds better to have some note in Kconfig.
> 
> And, fixed a typo.
> 
> Signed-off-by: Yang Shi <yang.shi@linaro.org>
> ---

Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>

>  lib/Kconfig.ubsan | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/Kconfig.ubsan b/lib/Kconfig.ubsan
> index 49518fb..e07c1ba 100644
> --- a/lib/Kconfig.ubsan
> +++ b/lib/Kconfig.ubsan
> @@ -18,6 +18,8 @@ config UBSAN_SANITIZE_ALL
>  	  This option activates instrumentation for the entire kernel.
>  	  If you don't enable this option, you have to explicitly specify
>  	  UBSAN_SANITIZE := y for the files/directories you want to check for UB.
> +	  Enabling this option will get kernel image size increased
> +	  significantly.
>  
>  config UBSAN_ALIGNMENT
>  	bool "Enable checking of pointers alignment"
> @@ -25,5 +27,5 @@ config UBSAN_ALIGNMENT
>  	default y if !HAVE_EFFICIENT_UNALIGNED_ACCESS
>  	help
>  	  This option enables detection of unaligned memory accesses.
> -	  Enabling this option on architectures that support unalligned
> +	  Enabling this option on architectures that support unaligned
>  	  accesses may produce a lot of false positives.
> 

      reply	other threads:[~2016-02-08  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06  0:05 Yang Shi
2016-02-08  7:48 ` Andrey Ryabinin [this message]

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=56B84841.7060904@virtuozzo.com \
    --to=aryabinin@virtuozzo.com \
    --cc=akpm@linux-foundation.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yang.shi@linaro.org \
    /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®