From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Alexander Potapenko <glider@google.com>,
adech.fo@gmail.com, dvyukov@google.com, cl@linux.com,
akpm@linux-foundation.org, kcc@google.com,
iamjoonsoo.kim@lge.com
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2] lib/stackdepot.c: allow the stack trace hash to be zero
Date: Fri, 15 Apr 2016 19:27:11 +0300 [thread overview]
Message-ID: <5711165F.5080304@gmail.com> (raw)
In-Reply-To: <1460549245-131634-1-git-send-email-glider@google.com>
On 04/13/2016 03:07 PM, Alexander Potapenko wrote:
> Do not bail out from depot_save_stack() if the stack trace has zero hash.
> Initially depot_save_stack() silently dropped stack traces with zero
> hashes, however there's actually no point in reserving this zero value.
>
> Reported-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Signed-off-by: Alexander Potapenko <glider@google.com>
Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
> ---
> lib/stackdepot.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/lib/stackdepot.c b/lib/stackdepot.c
> index 654c9d8..9e0b031 100644
> --- a/lib/stackdepot.c
> +++ b/lib/stackdepot.c
> @@ -210,10 +210,6 @@ depot_stack_handle_t depot_save_stack(struct stack_trace *trace,
> goto fast_exit;
>
> hash = hash_stack(trace->entries, trace->nr_entries);
> - /* Bad luck, we won't store this stack. */
> - if (hash == 0)
> - goto exit;
> -
> bucket = &stack_table[hash & STACK_HASH_MASK];
>
> /*
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Alexander Potapenko <glider@google.com>,
adech.fo@gmail.com, dvyukov@google.com, cl@linux.com,
akpm@linux-foundation.org, kcc@google.com,
iamjoonsoo.kim@lge.com
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2] lib/stackdepot.c: allow the stack trace hash to be zero
Date: Fri, 15 Apr 2016 19:27:11 +0300 [thread overview]
Message-ID: <5711165F.5080304@gmail.com> (raw)
In-Reply-To: <1460549245-131634-1-git-send-email-glider@google.com>
On 04/13/2016 03:07 PM, Alexander Potapenko wrote:
> Do not bail out from depot_save_stack() if the stack trace has zero hash.
> Initially depot_save_stack() silently dropped stack traces with zero
> hashes, however there's actually no point in reserving this zero value.
>
> Reported-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Signed-off-by: Alexander Potapenko <glider@google.com>
Acked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
> ---
> lib/stackdepot.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/lib/stackdepot.c b/lib/stackdepot.c
> index 654c9d8..9e0b031 100644
> --- a/lib/stackdepot.c
> +++ b/lib/stackdepot.c
> @@ -210,10 +210,6 @@ depot_stack_handle_t depot_save_stack(struct stack_trace *trace,
> goto fast_exit;
>
> hash = hash_stack(trace->entries, trace->nr_entries);
> - /* Bad luck, we won't store this stack. */
> - if (hash == 0)
> - goto exit;
> -
> bucket = &stack_table[hash & STACK_HASH_MASK];
>
> /*
>
next prev parent reply other threads:[~2016-04-15 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 12:07 [PATCH v2] lib/stackdepot.c: allow the stack trace hash to be zero Alexander Potapenko
2016-04-13 12:07 ` Alexander Potapenko
2016-04-15 16:27 ` Andrey Ryabinin [this message]
2016-04-15 16:27 ` Andrey Ryabinin
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=5711165F.5080304@gmail.com \
--to=ryabinin.a.a@gmail.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.