From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: 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
Subject: Re: [PATCH v3] kasan/quarantine: fix bugs on qlist_move_cache()
Date: Mon, 4 Jul 2016 12:43:44 +0300 [thread overview]
Message-ID: <577A2FD0.4040800@virtuozzo.com> (raw)
In-Reply-To: <20160704043647.GA14840@js1304-P5Q-DELUXE>
On 07/04/2016 07:36 AM, Joonsoo Kim wrote:
> On Fri, Jul 01, 2016 at 05:17:10PM +0300, Andrey Ryabinin wrote:
>>
>>
>> On 07/01/2016 05:02 PM, 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.
>>>
>>> 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..cf92494 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;
>>
>> Can you please also get rid of either qlink or curr.
>> Those are essentially the same pointers.
>
> Hello,
>
> Before putting the qlist_node to the list, we need to calculate
> curr->next and remember it to iterate the list. I use curr
> for this purpose so qlink and curr are not the same pointer.
>
Right, I missed the fact that qlist_put() changes ->next pointer, thus we can't fetch ->next after qlist_put().
> Thanks.
>
--
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: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: 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>
Subject: Re: [PATCH v3] kasan/quarantine: fix bugs on qlist_move_cache()
Date: Mon, 4 Jul 2016 12:43:44 +0300 [thread overview]
Message-ID: <577A2FD0.4040800@virtuozzo.com> (raw)
In-Reply-To: <20160704043647.GA14840@js1304-P5Q-DELUXE>
On 07/04/2016 07:36 AM, Joonsoo Kim wrote:
> On Fri, Jul 01, 2016 at 05:17:10PM +0300, Andrey Ryabinin wrote:
>>
>>
>> On 07/01/2016 05:02 PM, 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.
>>>
>>> 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..cf92494 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;
>>
>> Can you please also get rid of either qlink or curr.
>> Those are essentially the same pointers.
>
> Hello,
>
> Before putting the qlist_node to the list, we need to calculate
> curr->next and remember it to iterate the list. I use curr
> for this purpose so qlink and curr are not the same pointer.
>
Right, I missed the fact that qlist_put() changes ->next pointer, thus we can't fetch ->next after qlist_put().
> Thanks.
>
next prev parent reply other threads:[~2016-07-04 9:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 14:02 [PATCH v3] kasan/quarantine: fix bugs on qlist_move_cache() js1304
2016-07-01 14:02 ` js1304
2016-07-01 14:03 ` Dmitry Vyukov
2016-07-01 14:03 ` Dmitry Vyukov
2016-07-01 14:09 ` Joonsoo Kim
2016-07-01 14:09 ` Joonsoo Kim
2016-07-01 14:15 ` Dmitry Vyukov
2016-07-01 14:15 ` Dmitry Vyukov
2016-07-01 14:18 ` Andrey Ryabinin
2016-07-01 14:18 ` Andrey Ryabinin
2016-07-01 14:20 ` Dmitry Vyukov
2016-07-01 14:20 ` Dmitry Vyukov
2016-07-01 14:37 ` Joonsoo Kim
2016-07-01 14:37 ` Joonsoo Kim
2016-07-01 14:17 ` Andrey Ryabinin
2016-07-01 14:17 ` Andrey Ryabinin
2016-07-04 4:36 ` Joonsoo Kim
2016-07-04 4:36 ` Joonsoo Kim
2016-07-04 9:43 ` Andrey Ryabinin [this message]
2016-07-04 9:43 ` 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=577A2FD0.4040800@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=kasan-dev@googlegroups.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.