Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
	Jianyong Wu <jianyong.wu@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	David Hildenbrand <david@redhat.com>,
	Gavin Shan <gshan@redhat.com>, Jia He <justin.he@arm.com>,
	nd <nd@arm.com>
Subject: Re: [PATCH v2] arm64/mm: avoid fixmap race condition when create pud mapping
Date: Mon, 13 Dec 2021 13:45:03 +0000	[thread overview]
Message-ID: <20211213134503.GD11570@willie-the-truck> (raw)
In-Reply-To: <CAMj1kXF3Kf_OP-EL6oRfstw6VdEaqowVPioABxfMv+1FnPvfew@mail.gmail.com>

On Mon, Dec 13, 2021 at 11:35:16AM +0100, Ard Biesheuvel wrote:
> On Mon, 13 Dec 2021 at 11:16, Anshuman Khandual
> <anshuman.khandual@arm.com> wrote:
> > On 12/10/21 3:24 PM, Jianyong Wu wrote:
> > > diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c
> > > index acfae9b41cc8..98ac09ae9588 100644
> > > --- a/arch/arm64/mm/mmu.c
> > > +++ b/arch/arm64/mm/mmu.c
> > > @@ -63,6 +63,7 @@ static pmd_t bm_pmd[PTRS_PER_PMD] __page_aligned_bss __maybe_unused;
> > >  static pud_t bm_pud[PTRS_PER_PUD] __page_aligned_bss __maybe_unused;
> > >
> > >  static DEFINE_SPINLOCK(swapper_pgdir_lock);
> > > +static DEFINE_SPINLOCK(fixmap_lock);
> > >
> > >  void set_swapper_pgd(pgd_t *pgdp, pgd_t pgd)
> > >  {
> > > @@ -329,6 +330,11 @@ static void alloc_init_pud(pgd_t *pgdp, unsigned long addr, unsigned long end,
> > >       }
> > >       BUG_ON(p4d_bad(p4d));
> > >
> > > +     /*
> > > +      * fixmap is global resource, thus it needs to be protected by a lock
> > > +      * in case of race condition.
> > > +      */
> >
> > Small nit, format and align this comment block. I guess
> > could also be done while merging this patch as well.
> >
> > > +     spin_lock(&fixmap_lock);
> > >       pudp = pud_set_fixmap_offset(p4dp, addr);
> > >       do {
> > >               pud_t old_pud = READ_ONCE(*pudp);
> > > @@ -359,6 +365,7 @@ static void alloc_init_pud(pgd_t *pgdp, unsigned long addr, unsigned long end,
> > >       } while (pudp++, addr = next, addr != end);
> > >
> > >       pud_clear_fixmap();
> > > +     spin_unlock(&fixmap_lock);
> > >  }
> > >
> > >  static void __create_pgd_mapping(pgd_t *pgdir, phys_addr_t phys,
> > >
> >
> > Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> 
> We have different fixmap slots for different page table levels, so
> 'fixmap_lock' is not the right name.
> 
> But we already have swapper_pgdir_lock as well, which serializes the
> use of the pgdir level fixmap slot. And we have no spinlocks
> protecting the other levels.
> 
> So should we perhaps clean this up more comprehensively? Wouldn't it
> be better to add a mutex to __create_pgd_mapping(), for instance?

That does sound like a better way to do things, but the simplicity of this
patch is quite attractive for backporting. Would you object to me queuing
it as-is, on the premise that I'm more than happy to take consolidation
changes on top?

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-12-13 13:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10  9:54 [PATCH v2] arm64/mm: avoid fixmap race condition when create pud mapping Jianyong Wu
2021-12-10 11:22 ` Catalin Marinas
2021-12-13  5:24   ` Jianyong Wu
2021-12-13  6:56 ` Anshuman Khandual
2021-12-13  7:27   ` Jianyong Wu
2021-12-13  7:37     ` David Hildenbrand
2021-12-13  9:57       ` Catalin Marinas
2021-12-13 10:16 ` Anshuman Khandual
2021-12-13 10:35   ` Ard Biesheuvel
2021-12-13 13:45     ` Will Deacon [this message]
2021-12-13 14:01       ` Ard Biesheuvel
2021-12-13 16:42 ` Will Deacon
2021-12-15 14:13 ` Qian Cai
2021-12-15 16:02   ` Catalin Marinas
2021-12-15 16:04     ` David Hildenbrand
2021-12-16  3:00       ` Jianyong Wu

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=20211213134503.GD11570@willie-the-truck \
    --to=will@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=gshan@redhat.com \
    --cc=jianyong.wu@arm.com \
    --cc=justin.he@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nd@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