From: Uladzislau Rezki <urezki@gmail.com>
To: Huang Adrian <adrianhuang0701@gmail.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
ahuang12@lenovo.com, akpm@linux-foundation.org,
andreyknvl@gmail.com, bhe@redhat.com, dvyukov@google.com,
glider@google.com, hch@infradead.org, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ryabinin.a.a@gmail.com, sunjw10@lenovo.com,
vincenzo.frascino@arm.com
Subject: Re: [PATCH 1/1] mm/vmalloc: Combine all TLB flush operations of KASAN shadow virtual address into one operation
Date: Wed, 31 Jul 2024 15:38:33 +0200 [thread overview]
Message-ID: <Zqo-WbpZ9zmYVLA2@pc636> (raw)
In-Reply-To: <CAHKZfL1i3D7wgbdLWz3xiK7KkAXAxrsyQjFmFarrM94tJPYh3Q@mail.gmail.com>
On Wed, Jul 31, 2024 at 08:39:00AM +0800, Huang Adrian wrote:
> On Wed, Jul 31, 2024 at 12:42 AM Uladzislau Rezki <urezki@gmail.com> wrote:
> > Thank you for posting this! So tasklist_lock is not a problem.
> > I assume you have a full output of lock_stat. Could you please
> > paste it for v6.11-rc1 + KASAN?
>
> Full output: https://gist.github.com/AdrianHuang/2c2c97f533ba467ff32781590279ccc9
>
I do not see anything obvious. So it means that CSD lock debugging should be done.
But this is another story :)
Thank you for helping!
--
Uladzislau Rezki
next prev parent reply other threads:[~2024-07-31 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 16:52 Adrian Huang
2024-07-28 21:18 ` Andrew Morton
2024-07-29 11:12 ` Huang Adrian
2024-07-29 11:29 ` Uladzislau Rezki
2024-07-30 9:36 ` Adrian Huang
2024-07-30 11:38 ` Uladzislau Rezki
2024-07-30 16:27 ` Huang Adrian
2024-07-30 16:42 ` Uladzislau Rezki
2024-07-31 0:39 ` Huang Adrian
2024-07-31 13:38 ` Uladzislau Rezki [this message]
2024-07-29 8:30 ` Baoquan He
2024-07-29 11:19 ` Huang Adrian
2024-07-30 1:18 ` Andrew Morton
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=Zqo-WbpZ9zmYVLA2@pc636 \
--to=urezki@gmail.com \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bhe@redhat.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hch@infradead.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--cc=sunjw10@lenovo.com \
--cc=vincenzo.frascino@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox