Re: [PATCH] RISC-V: Acquire mmap lock before invoking walk_page_range

2020-06-18 Thread Palmer Dabbelt
On Wed, 17 Jun 2020 13:37:32 PDT (-0700), Atish Patra wrote: As per walk_page_range documentation, mmap lock should be acquired by the caller before invoking walk_page_range. mmap_assert_locked gets triggered without that. The details can be found here. http://lists.infradead.org/pipermail/linux

Re: [PATCH] RISC-V: Acquire mmap lock before invoking walk_page_range

2020-06-18 Thread Atish Patra
On Wed, Jun 17, 2020 at 7:29 PM Zong Li wrote: > > On Thu, Jun 18, 2020 at 8:01 AM Michel Lespinasse wrote: > > > > On Wed, Jun 17, 2020 at 1:38 PM Atish Patra wrote: > > > As per walk_page_range documentation, mmap lock should be acquired by the > > > caller before invoking walk_page_range. mma

Re: [PATCH] RISC-V: Acquire mmap lock before invoking walk_page_range

2020-06-17 Thread Zong Li
On Thu, Jun 18, 2020 at 8:01 AM Michel Lespinasse wrote: > > On Wed, Jun 17, 2020 at 1:38 PM Atish Patra wrote: > > As per walk_page_range documentation, mmap lock should be acquired by the > > caller before invoking walk_page_range. mmap_assert_locked gets triggered > > without that. The details

Re: [PATCH] RISC-V: Acquire mmap lock before invoking walk_page_range

2020-06-17 Thread Michel Lespinasse
On Wed, Jun 17, 2020 at 1:38 PM Atish Patra wrote: > As per walk_page_range documentation, mmap lock should be acquired by the > caller before invoking walk_page_range. mmap_assert_locked gets triggered > without that. The details can be found here. > > http://lists.infradead.org/pipermail/linux-r

[PATCH] RISC-V: Acquire mmap lock before invoking walk_page_range

2020-06-17 Thread Atish Patra
As per walk_page_range documentation, mmap lock should be acquired by the caller before invoking walk_page_range. mmap_assert_locked gets triggered without that. The details can be found here. http://lists.infradead.org/pipermail/linux-riscv/2020-June/010335.html Fixes: 395a21ff859c(riscv: add AR