From: Peter Xu <peterx@redhat.com>
To: Tal Zussman <tz2294@columbia.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
David Hildenbrand <david@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] userfaultfd: remove (VM_)BUG_ON()s
Date: Tue, 10 Jun 2025 09:11:20 -0400 [thread overview]
Message-ID: <aEgu-DA3pgKSYHRK@x1.local> (raw)
In-Reply-To: <20250607-uffd-fixes-v2-2-339dafe9a2fe@columbia.edu>
On Sat, Jun 07, 2025 at 02:40:01AM -0400, Tal Zussman wrote:
> BUG_ON() is deprecated [1]. Convert all the BUG_ON()s and VM_BUG_ON()s
> to use VM_WARN_ON_ONCE().
>
> While at it, also convert the WARN_ON_ONCE()s in move_pages() to use
> VM_WARN_ON_ONCE(), as the relevant conditions are already checked in
> validate_range() in move_pages()'s caller.
>
> [1] https://www.kernel.org/doc/html/v6.15/process/coding-style.html#use-warn-rather-than-bug
>
> Signed-off-by: Tal Zussman <tz2294@columbia.edu>
> ---
> fs/userfaultfd.c | 59 +++++++++++++++++++++++++-------------------------
> mm/userfaultfd.c | 66 +++++++++++++++++++++++++++-----------------------------
> 2 files changed, 61 insertions(+), 64 deletions(-)
>
> diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
> index 22f4bf956ba1..80c95c712266 100644
> --- a/fs/userfaultfd.c
> +++ b/fs/userfaultfd.c
> @@ -165,14 +165,14 @@ static void userfaultfd_ctx_get(struct userfaultfd_ctx *ctx)
> static void userfaultfd_ctx_put(struct userfaultfd_ctx *ctx)
> {
> if (refcount_dec_and_test(&ctx->refcount)) {
> - VM_BUG_ON(spin_is_locked(&ctx->fault_pending_wqh.lock));
> - VM_BUG_ON(waitqueue_active(&ctx->fault_pending_wqh));
> - VM_BUG_ON(spin_is_locked(&ctx->fault_wqh.lock));
> - VM_BUG_ON(waitqueue_active(&ctx->fault_wqh));
> - VM_BUG_ON(spin_is_locked(&ctx->event_wqh.lock));
> - VM_BUG_ON(waitqueue_active(&ctx->event_wqh));
> - VM_BUG_ON(spin_is_locked(&ctx->fd_wqh.lock));
> - VM_BUG_ON(waitqueue_active(&ctx->fd_wqh));
> + VM_WARN_ON_ONCE(spin_is_locked(&ctx->fault_pending_wqh.lock));
> + VM_WARN_ON_ONCE(waitqueue_active(&ctx->fault_pending_wqh));
> + VM_WARN_ON_ONCE(spin_is_locked(&ctx->fault_wqh.lock));
> + VM_WARN_ON_ONCE(waitqueue_active(&ctx->fault_wqh));
> + VM_WARN_ON_ONCE(spin_is_locked(&ctx->event_wqh.lock));
> + VM_WARN_ON_ONCE(waitqueue_active(&ctx->event_wqh));
> + VM_WARN_ON_ONCE(spin_is_locked(&ctx->fd_wqh.lock));
> + VM_WARN_ON_ONCE(waitqueue_active(&ctx->fd_wqh));
> mmdrop(ctx->mm);
> kmem_cache_free(userfaultfd_ctx_cachep, ctx);
I didn't follow closely on the latest discussions on BUG_ON, but here I
just stumbled on top of this chunk, it does look like a slight overkill
using tons of bools for each of them.. even if the doc suggested
WARN_ON_ONCE().
David might have a better picture of what's our plan for mm to properly
assert while reducing the overhead as much as possible.
For this specific one, if we really want to convert we could also merge
them into one, so one bool to cover all.
--
Peter Xu
next prev parent reply other threads:[~2025-06-10 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 6:39 [PATCH v2 0/4] mm: userfaultfd: assorted fixes and cleanups Tal Zussman
2025-06-07 6:40 ` [PATCH v2 1/4] userfaultfd: correctly prevent registering VM_DROPPABLE regions Tal Zussman
2025-06-07 14:40 ` Jason A. Donenfeld
2025-06-07 22:04 ` Andrew Morton
2025-06-09 15:02 ` Peter Xu
2025-06-07 6:40 ` [PATCH v2 2/4] userfaultfd: remove (VM_)BUG_ON()s Tal Zussman
2025-06-10 7:26 ` David Hildenbrand
2025-06-17 23:10 ` Tal Zussman
2025-06-23 15:18 ` David Hildenbrand
2025-06-10 13:11 ` Peter Xu [this message]
2025-06-10 13:17 ` David Hildenbrand
2025-06-07 6:40 ` [PATCH v2 3/4] userfaultfd: prevent unregistering VMAs through a different userfaultfd Tal Zussman
2025-06-10 7:30 ` David Hildenbrand
2025-06-17 20:50 ` Tal Zussman
2025-06-07 6:40 ` [PATCH v2 4/4] userfaultfd: remove UFFD_CLOEXEC, UFFD_NONBLOCK, and UFFD_FLAGS_SET Tal Zussman
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=aEgu-DA3pgKSYHRK@x1.local \
--to=peterx@redhat.com \
--cc=Jason@zx2c4.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tz2294@columbia.edu \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).