All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Zhaoyang Huang <huangzhaoyang@gmail.com>
Cc: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>, Ke Wang <ke.wang@unisoc.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] mm: fix racing of vb->va when kasan enabled
Date: Mon, 20 Jun 2022 12:43:59 +0200	[thread overview]
Message-ID: <CA+KHdyXpdow7SYsbq_7F0zDd5-nYGi6db7R11R3--g3gUu-59w@mail.gmail.com> (raw)
In-Reply-To: <CAGWkznHPdk_yqn2GWPDJaT32+4MnFLnRjdjBkaFv9BLMh4yM=g@mail.gmail.com>

> > >
> > Is it easy to reproduce? If so could you please describe the steps? As i see
> > the freeing of the "vb" is RCU safe whereas vb->va is not. But from the first
> > glance i do not see how it can accessed twice. Hm..
> It was raised from a monkey test on A13_k515 system and got 1/20 pcs
> failed. IMO, vb->va which out of vmap_purge_lock protection could race
> with a concurrent ra freeing within __purge_vmap_area_lazy.
>
Do you have exact steps how you run "monkey" test?

-- 
Uladzislau Rezki

  reply	other threads:[~2022-06-20 10:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  2:52 [PATCH] mm: fix racing of vb->va when kasan enabled zhaoyang.huang
2022-05-26  6:31 ` Xuewen Yan
2022-06-19 21:03   ` Uladzislau Rezki
2022-06-20  6:58     ` Zhaoyang Huang
2022-06-20 10:43       ` Uladzislau Rezki [this message]
2022-06-20 11:23         ` Zhaoyang Huang
2022-06-21  9:26           ` Uladzislau Rezki
2022-06-21 11:00             ` Zhaoyang Huang
2022-06-21 14:29               ` Uladzislau Rezki
2022-06-22  3:15                 ` Zhaoyang Huang
2022-06-22  6:04                   ` Zhaoyang Huang
2022-06-24 10:27                     ` Uladzislau Rezki
2022-06-24 10:51                       ` Uladzislau Rezki

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=CA+KHdyXpdow7SYsbq_7F0zDd5-nYGi6db7R11R3--g3gUu-59w@mail.gmail.com \
    --to=urezki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=huangzhaoyang@gmail.com \
    --cc=ke.wang@unisoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=zhaoyang.huang@unisoc.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.