linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Daniel Borkmann <daniel@iogearbox.net>,
	Peter Zijlstra <peterz@infradead.org>,
	Michel Lespinasse <walken@google.com>
Cc: Yonghong Song <yhs@fb.com>,
	bpf@vger.kernel.org, linux-mm@kvack.org,
	Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	kernel-team@fb.com, Luigi Rizzo <lrizzo@google.com>,
	liam.howlett@oracle.com, akpm@linux-foundation.org
Subject: Re: [PATCH mm/bpf v2] mm: bpf: add find_vma_no_check() without lockdep_assert on mm->mmap_lock
Date: Wed, 8 Sep 2021 10:53:26 -0300	[thread overview]
Message-ID: <20210908135326.GZ1200268@ziepe.ca> (raw)
In-Reply-To: <ebcddf07-f329-05fa-8fdc-b2b9d6b0127b@iogearbox.net>

On Wed, Sep 08, 2021 at 02:20:17PM +0200, Daniel Borkmann wrote:

> > The warning is due to commit 5b78ed24e8ec("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()")
> > which added mmap_assert_locked() in find_vma() function. The mmap_assert_locked() function
> > asserts that mm->mmap_lock needs to be held. But this is not the case for
> > bpf_get_stack() or bpf_get_stackid() helper (kernel/bpf/stackmap.c), which
> > uses mmap_read_trylock_non_owner() instead. Since mm->mmap_lock is not held
> > in bpf_get_stack[id]() use case, the above warning is emitted during test run.
> > 
> > This patch added function find_vma_no_check() which does not have mmap_assert_locked() call and
> > bpf_get_stack[id]() helpers call find_vma_no_check() instead. This resolved the above warning.
> > 
> > I didn't use __find_vma() name because it has been used in drivers/gpu/drm/i915/i915_gpu_error.c:
> >      static struct i915_vma_coredump *
> >      __find_vma(struct i915_vma_coredump *vma, const char *name) { ... }
> > 
> > Cc: Luigi Rizzo <lrizzo@google.com>
> > Fixes: 5b78ed24e8ec("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()")
> > Signed-off-by: Yonghong Song <yhs@fb.com>
> 
> Luigi / Liam / Andrew, if the below looks reasonable to you, any objections to route the
> fix with your ACKs via bpf tree to Linus (or strong preference via -mm fixes)?

Michel added this remark along with the mmap_read_trylock_non_owner:

    It's still not ideal that bpf/stackmap subverts the lock ownership in this
    way.  Thanks to Peter Zijlstra for suggesting this API as the least-ugly
    way of addressing this in the short term.

Subverting lockdep and then adding more and more core MM APIs to
support this seems quite a bit more ugly than originally expected.

Michel's original idea to split out the lockdep abuse and put it only
in BPF is probably better. Obtain the mmap_read_trylock normally as
owner and then release ownership only before triggering the work. At
least lockdep will continue to work properly for the find_vma.

Jason


  reply	other threads:[~2021-09-08 13:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  4:44 Yonghong Song
2021-09-08 12:20 ` Daniel Borkmann
2021-09-08 13:53   ` Jason Gunthorpe [this message]
2021-09-08 14:15     ` Peter Zijlstra
2021-09-08 14:43       ` Luigi Rizzo
2021-09-08 15:12         ` Liam Howlett
2021-09-08 16:09           ` Yonghong Song
2021-09-08 17:09             ` Luigi Rizzo
2021-09-08 17:21               ` Alexei Starovoitov
2021-09-08 17:52                 ` Andrew Morton
2021-09-08 18:02                   ` Alexei Starovoitov
2021-09-08 18:15                     ` Andrew Morton
2021-09-08 18:20                       ` Alexei Starovoitov
2021-09-08 18:30                         ` Liam Howlett
2021-09-08 18:45                           ` Yonghong Song
2021-09-08 18:49                           ` Jason Gunthorpe
2021-09-08 19:11                             ` Yonghong Song
2021-09-08 23:33                               ` Jason Gunthorpe
2021-09-09  5:50                                 ` Yonghong Song
2021-09-09  8:05                           ` Peter Zijlstra
2021-09-08 18:43                     ` Liam Howlett
2021-09-08 19:42                       ` Alexei Starovoitov

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=20210908135326.GZ1200268@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=lrizzo@google.com \
    --cc=peterz@infradead.org \
    --cc=walken@google.com \
    --cc=yhs@fb.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