From: Mohamed Alzayat <alzayat@mpi-sws.org>
To: Will Deacon <will@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linux-mm@kvack.org
Subject: Re: Potential bug in soft-dirty bits (with test case)
Date: Tue, 20 Apr 2021 20:32:50 +0200 [thread overview]
Message-ID: <CA+32v5wi7QbY6p+BbLkNz9mgdUbi71zwFmq5o6TMw2XDXrhogA@mail.gmail.com> (raw)
In-Reply-To: <20201130125045.GG24563@willie-the-truck>
Thanks a lot Vlastimil, and Peter for the pointers! Many thanks Will
for actually fixing it (v5.12)!
Thanks,
Mohamed
On Mon, Nov 30, 2020 at 1:50 PM Will Deacon <will@kernel.org> wrote:
>
> On Mon, Nov 30, 2020 at 01:02:41PM +0100, Peter Zijlstra wrote:
> > On Mon, Nov 30, 2020 at 12:51:59PM +0100, Vlastimil Babka wrote:
> > > On 11/30/20 11:37 AM, Mohamed Alzayat wrote:
> >
> > > > Thanks for confirming, Vlastimil!
> > > >
> > > > The first bad commit is: 0758cd8304942292e95a0f750c374533db378b32
> > > > asm-generic/tlb: avoid potential double flush
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0758cd8304942292e95a0f750c374533db378b32
> > > >
> > > > Reverting this commit solves the problem, but this might not be the
> > > > right way of fixing it.
> > >
> > > Thanks for bisecting! Let's CC people involved in that commit. All important
> > > should be in the quoted conversation above.
> >
> > There's a thread about it here:
> >
> > https://lkml.kernel.org/r/20201120143557.6715-1-will@kernel.org
> >
> > That softdirty code really shouldn't be using mmu_gather imo, but I'm
> > still not clear on what exactly is broken why there.
>
> I'll spin a v2 of that series soon, so I'll add folks here to cc. The
> fact that a test noticed the missing invalidation is a pretty good reason
> for us to add it back!
Thanks, everyone! I appreciate your helpful comments and pointers,
looking forward to the v2 of that series. Until then, reverting to
double TLB flush works fine on recent kernels (tested on v5.10-rc5).
Thanks,
Mohamed
>
> Will
>
prev parent reply other threads:[~2021-04-20 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:15 Mohamed Alzayat
2020-11-27 16:40 ` Vlastimil Babka
2020-11-30 10:37 ` Mohamed Alzayat
2020-11-30 11:51 ` Vlastimil Babka
2020-11-30 12:02 ` Peter Zijlstra
2020-11-30 12:50 ` Will Deacon
2021-04-20 18:32 ` Mohamed Alzayat [this message]
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+32v5wi7QbY6p+BbLkNz9mgdUbi71zwFmq5o6TMw2XDXrhogA@mail.gmail.com \
--to=alzayat@mpi-sws.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox