From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Kuthonuzo Luruo <poll.stdin@gmail.com>
Cc: js1304@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] kasan/quarantine: fix NULL pointer dereference bug
Date: Fri, 1 Jul 2016 14:17:43 +0300 [thread overview]
Message-ID: <57765157.8020909@virtuozzo.com> (raw)
In-Reply-To: <CAHPzcFmZNZe62MFg0-iz1fJneFeG1w4nFFuG-xmpD2sJHovDgQ@mail.gmail.com>
On 07/01/2016 01:55 PM, Kuthonuzo Luruo wrote:
> On Fri, Jul 1, 2016 at 1:41 PM, Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:
>>
>>
>> On 07/01/2016 10:53 AM, js1304@gmail.com wrote:
>>> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>>>
>>> If we move an item on qlist's tail, we need to update qlist's tail
>>> properly. curr->next can be NULL since it is singly linked list
>>> so it is invalid for tail. curr is scheduled to be moved so
>>> using prev would be correct.
>>
>> Hmm.. prev may be the element that moved in 'to' list. We need to assign the last element
>> from which is in ther 'from' list.
>
> something like this should handle qlink == head == tail:
>
> --- a/mm/kasan/quarantine.c
> +++ b/mm/kasan/quarantine.c
> @@ -251,11 +251,11 @@ static void qlist_move_cache(struct qlist_head *from,
> if (obj_cache == cache) {
> if (unlikely(from->head == qlink)) {
> from->head = curr->next;
> - prev = curr;
> + prev = from->head;
This will break 'to' list.
> } else
> prev->next = curr->next;
> if (unlikely(from->tail == qlink))
> - from->tail = curr->next;
> + from->tail = prev;
> from->bytes -= cache->size;
> qlist_put(to, qlink, cache->size);
> } else {
>
>
--
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: Kuthonuzo Luruo <poll.stdin@gmail.com>
Cc: <js1304@gmail.com>, Andrew Morton <akpm@linux-foundation.org>,
"Alexander Potapenko" <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>, <kasan-dev@googlegroups.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] kasan/quarantine: fix NULL pointer dereference bug
Date: Fri, 1 Jul 2016 14:17:43 +0300 [thread overview]
Message-ID: <57765157.8020909@virtuozzo.com> (raw)
In-Reply-To: <CAHPzcFmZNZe62MFg0-iz1fJneFeG1w4nFFuG-xmpD2sJHovDgQ@mail.gmail.com>
On 07/01/2016 01:55 PM, Kuthonuzo Luruo wrote:
> On Fri, Jul 1, 2016 at 1:41 PM, Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:
>>
>>
>> On 07/01/2016 10:53 AM, js1304@gmail.com wrote:
>>> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>>>
>>> If we move an item on qlist's tail, we need to update qlist's tail
>>> properly. curr->next can be NULL since it is singly linked list
>>> so it is invalid for tail. curr is scheduled to be moved so
>>> using prev would be correct.
>>
>> Hmm.. prev may be the element that moved in 'to' list. We need to assign the last element
>> from which is in ther 'from' list.
>
> something like this should handle qlink == head == tail:
>
> --- a/mm/kasan/quarantine.c
> +++ b/mm/kasan/quarantine.c
> @@ -251,11 +251,11 @@ static void qlist_move_cache(struct qlist_head *from,
> if (obj_cache == cache) {
> if (unlikely(from->head == qlink)) {
> from->head = curr->next;
> - prev = curr;
> + prev = from->head;
This will break 'to' list.
> } else
> prev->next = curr->next;
> if (unlikely(from->tail == qlink))
> - from->tail = curr->next;
> + from->tail = prev;
> from->bytes -= cache->size;
> qlist_put(to, qlink, cache->size);
> } else {
>
>
next prev parent reply other threads:[~2016-07-01 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 7:53 [PATCH] kasan/quarantine: fix NULL pointer dereference bug js1304
2016-07-01 7:53 ` js1304
2016-07-01 8:11 ` Andrey Ryabinin
2016-07-01 8:11 ` Andrey Ryabinin
2016-07-01 10:55 ` Kuthonuzo Luruo
2016-07-01 10:55 ` Kuthonuzo Luruo
2016-07-01 11:17 ` Andrey Ryabinin [this message]
2016-07-01 11:17 ` Andrey Ryabinin
2016-07-01 13:55 ` [PATCH v2] kasan/quarantine: fix bugs on qlist_move_cache() js1304
2016-07-01 13:55 ` js1304
2016-07-01 14:03 ` Joonsoo Kim
2016-07-01 14:03 ` Joonsoo Kim
2016-07-02 8:43 ` kbuild test robot
2016-07-01 13:57 ` [PATCH] kasan/quarantine: fix NULL pointer dereference bug Joonsoo Kim
2016-07-01 13:57 ` Joonsoo Kim
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=57765157.8020909@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.