All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhouyi Zhou <zhouzhouyi@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
	Alexander Potapenko <glider@google.com>,
	kasan-dev <kasan-dev@googlegroups.com>,
	Linux-MM <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] kasan: fix livelock in qlist_move_cache
Date: Wed, 29 Nov 2017 07:02:01 +0800	[thread overview]
Message-ID: <CAABZP2xvWFOXZMGgNrnx5fDJGrXybrM3DXFEdymXf1RLD7STJA@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+aRGC9vVaHCXmeEiL5ywjQRTK+yNn+TAWKPLB3Gpd4U_A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]

hi,
     I will prepare the environment to let the phenonmenon reappear today
right after I reached my company.
Cheers

On Wednesday, November 29, 2017, Dmitry Vyukov <dvyukov@google.com> wrote:

> On Tue, Nov 28, 2017 at 6:56 PM, Dmitry Vyukov <dvyukov@google.com
> <javascript:;>> wrote:
> > On Tue, Nov 28, 2017 at 12:30 PM, Zhouyi Zhou <zhouzhouyi@gmail.com
> <javascript:;>> wrote:
> >> Hi,
> >>    By using perf top, qlist_move_cache occupies 100% cpu did really
> >> happen in my environment yesterday, or I
> >> won't notice the kasan code.
> >>    Currently I have difficulty to let it reappear because the frontend
> >> guy modified some user mode code.
> >>    I can repeat again and again now is
> >> kgdb_breakpoint () at kernel/debug/debug_core.c:1073
> >> 1073 wmb(); /* Sync point after breakpoint */
> >> (gdb) p quarantine_batch_size
> >> $1 = 3601946
> >>    And by instrument code, maximum
> >> global_quarantine[quarantine_tail].bytes reached is 6618208.
> >
> > On second thought, size does not matter too much because there can be
> > large objects. Quarantine always quantize by objects, we can't part of
> > an object into one batch, and another part of the object into another
> > object. But it's not a problem, because overhead per objects is O(1).
> > We can push a single 4MB object and overflow target size by 4MB and
> > that will be fine.
> > Either way, 6MB is not terribly much too. Should take milliseconds to
> process.
> >
> >
> >
> >
> >>    I do think drain quarantine right in quarantine_put is a better
> >> place to drain because cache_free is fine in
> >> that context. I am willing do it if you think it is convenient :-)
>
>
> Andrey, do you know of any problems with draining quarantine in push?
> Do you have any objections?
>
> But it's still not completely clear to me what problem we are solving.
>

[-- Attachment #2: Type: text/html, Size: 2483 bytes --]

  reply	other threads:[~2017-11-28 23:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  4:04 [PATCH 1/1] kasan: fix livelock in qlist_move_cache zhouzhouyi
2017-11-28  4:04 ` zhouzhouyi
2017-11-28  4:05 ` Zhouyi Zhou
2017-11-28  4:05   ` Zhouyi Zhou
2017-11-28  7:45   ` Dmitry Vyukov
2017-11-28  7:45     ` Dmitry Vyukov
2017-11-28  8:00     ` Zhouyi Zhou
2017-11-28  8:00       ` Zhouyi Zhou
2017-11-28  8:12       ` Dmitry Vyukov
2017-11-28  8:12         ` Dmitry Vyukov
2017-11-28  8:33         ` Zhouyi Zhou
2017-11-28  8:33           ` Zhouyi Zhou
2017-11-28  8:58           ` Dmitry Vyukov
2017-11-28  8:58             ` Dmitry Vyukov
2017-11-28  9:17             ` Zhouyi Zhou
2017-11-28  9:17               ` Zhouyi Zhou
2017-11-28  9:27               ` Dmitry Vyukov
2017-11-28  9:27                 ` Dmitry Vyukov
2017-11-28 11:30                 ` Zhouyi Zhou
2017-11-28 11:30                   ` Zhouyi Zhou
2017-11-28 17:56                   ` Dmitry Vyukov
2017-11-28 17:56                     ` Dmitry Vyukov
2017-11-28 17:57                     ` Dmitry Vyukov
2017-11-28 17:57                       ` Dmitry Vyukov
2017-11-28 23:02                       ` Zhouyi Zhou [this message]
2017-11-28 23:41                       ` Zhouyi Zhou
2017-11-28 23:41                         ` Zhouyi Zhou
2017-11-29  4:54                         ` Zhouyi Zhou
2017-11-29  4:54                           ` Zhouyi Zhou
2017-11-29  9:03                           ` Dmitry Vyukov
2017-11-29  9:03                             ` 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=CAABZP2xvWFOXZMGgNrnx5fDJGrXybrM3DXFEdymXf1RLD7STJA@mail.gmail.com \
    --to=zhouzhouyi@gmail.com \
    --cc=aryabinin@virtuozzo.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.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.