From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: js1304@gmail.com, Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com,
Kuthonuzo Luruo <poll.stdin@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v4] kasan/quarantine: fix bugs on qlist_move_cache()
Date: Mon, 4 Jul 2016 12:49:08 +0300 [thread overview]
Message-ID: <577A3114.9080008@virtuozzo.com> (raw)
In-Reply-To: <1467606714-30231-1-git-send-email-iamjoonsoo.kim@lge.com>
On 07/04/2016 07:31 AM, js1304@gmail.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> There are two bugs on qlist_move_cache(). One is that qlist's tail
> isn't set properly. curr->next can be NULL since it is singly linked
> list and NULL value on tail is invalid if there is one item on qlist.
> Another one is that if cache is matched, qlist_put() is called and
> it will set curr->next to NULL. It would cause to stop the loop
> prematurely.
>
> These problems come from complicated implementation so I'd like to
> re-implement it completely. Implementation in this patch is really
> simple. Iterate all qlist_nodes and put them to appropriate list.
>
> Unfortunately, I got this bug sometime ago and lose oops message.
> But, the bug looks trivial and no need to attach oops.
>
> v4: fix cache size bug s/cache->size/obj_cache->size/
> v3: fix build warning
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> ---
> mm/kasan/quarantine.c | 21 +++++++--------------
> 1 file changed, 7 insertions(+), 14 deletions(-)
>
> diff --git a/mm/kasan/quarantine.c b/mm/kasan/quarantine.c
> index 4973505..b2e1827 100644
> --- a/mm/kasan/quarantine.c
> +++ b/mm/kasan/quarantine.c
> @@ -238,30 +238,23 @@ static void qlist_move_cache(struct qlist_head *from,
> struct qlist_head *to,
> struct kmem_cache *cache)
> {
> - struct qlist_node *prev = NULL, *curr;
> + struct qlist_node *curr;
>
> if (unlikely(qlist_empty(from)))
> return;
>
> curr = from->head;
> + qlist_init(from);
> while (curr) {
> struct qlist_node *qlink = curr;
> struct kmem_cache *obj_cache = qlink_to_cache(qlink);
>
> - if (obj_cache == cache) {
> - if (unlikely(from->head == qlink)) {
> - from->head = curr->next;
> - prev = curr;
> - } else
> - prev->next = curr->next;
> - if (unlikely(from->tail == qlink))
> - from->tail = curr->next;
> - from->bytes -= cache->size;
> - qlist_put(to, qlink, cache->size);
> - } else {
> - prev = curr;
> - }
> curr = curr->next;
Nit: Wouldn't be more appropriate to swap 'curr' and 'qlink' variable names?
Because now qlink is acts as a "current" pointer.
> +
> + if (obj_cache == cache)
> + qlist_put(to, qlink, obj_cache->size);
> + else
> + qlist_put(from, qlink, obj_cache->size);
> }
> }
>
>
--
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 <aryabinin@virtuozzo.com>
To: <js1304@gmail.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>, <kasan-dev@googlegroups.com>,
Kuthonuzo Luruo <poll.stdin@gmail.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v4] kasan/quarantine: fix bugs on qlist_move_cache()
Date: Mon, 4 Jul 2016 12:49:08 +0300 [thread overview]
Message-ID: <577A3114.9080008@virtuozzo.com> (raw)
In-Reply-To: <1467606714-30231-1-git-send-email-iamjoonsoo.kim@lge.com>
On 07/04/2016 07:31 AM, js1304@gmail.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> There are two bugs on qlist_move_cache(). One is that qlist's tail
> isn't set properly. curr->next can be NULL since it is singly linked
> list and NULL value on tail is invalid if there is one item on qlist.
> Another one is that if cache is matched, qlist_put() is called and
> it will set curr->next to NULL. It would cause to stop the loop
> prematurely.
>
> These problems come from complicated implementation so I'd like to
> re-implement it completely. Implementation in this patch is really
> simple. Iterate all qlist_nodes and put them to appropriate list.
>
> Unfortunately, I got this bug sometime ago and lose oops message.
> But, the bug looks trivial and no need to attach oops.
>
> v4: fix cache size bug s/cache->size/obj_cache->size/
> v3: fix build warning
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> ---
> mm/kasan/quarantine.c | 21 +++++++--------------
> 1 file changed, 7 insertions(+), 14 deletions(-)
>
> diff --git a/mm/kasan/quarantine.c b/mm/kasan/quarantine.c
> index 4973505..b2e1827 100644
> --- a/mm/kasan/quarantine.c
> +++ b/mm/kasan/quarantine.c
> @@ -238,30 +238,23 @@ static void qlist_move_cache(struct qlist_head *from,
> struct qlist_head *to,
> struct kmem_cache *cache)
> {
> - struct qlist_node *prev = NULL, *curr;
> + struct qlist_node *curr;
>
> if (unlikely(qlist_empty(from)))
> return;
>
> curr = from->head;
> + qlist_init(from);
> while (curr) {
> struct qlist_node *qlink = curr;
> struct kmem_cache *obj_cache = qlink_to_cache(qlink);
>
> - if (obj_cache == cache) {
> - if (unlikely(from->head == qlink)) {
> - from->head = curr->next;
> - prev = curr;
> - } else
> - prev->next = curr->next;
> - if (unlikely(from->tail == qlink))
> - from->tail = curr->next;
> - from->bytes -= cache->size;
> - qlist_put(to, qlink, cache->size);
> - } else {
> - prev = curr;
> - }
> curr = curr->next;
Nit: Wouldn't be more appropriate to swap 'curr' and 'qlink' variable names?
Because now qlink is acts as a "current" pointer.
> +
> + if (obj_cache == cache)
> + qlist_put(to, qlink, obj_cache->size);
> + else
> + qlist_put(from, qlink, obj_cache->size);
> }
> }
>
>
next prev parent reply other threads:[~2016-07-04 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 4:31 [PATCH v4] kasan/quarantine: fix bugs on qlist_move_cache() js1304
2016-07-04 4:31 ` js1304
2016-07-04 9:49 ` Andrey Ryabinin [this message]
2016-07-04 9:49 ` Andrey Ryabinin
2016-07-06 0:57 ` Joonsoo Kim
2016-07-06 0:57 ` Joonsoo Kim
2016-07-05 13:29 ` Dmitry Vyukov
2016-07-05 13:29 ` Dmitry Vyukov
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=577A3114.9080008@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=poll.stdin@gmail.com \
/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.