public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@akamai.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, jim.cromie@gmail.com
Subject: [PATCH 0/2] dyndbg: let's use the module notifier callback
Date: Thu, 16 Feb 2023 12:15:49 -0500	[thread overview]
Message-ID: <cover.1676566871.git.jbaron@akamai.com> (raw)

Hi,

Jim Cromie hit a BUG() while toggling jump label branches in a module
before they were properly initialized. This isn't currently an issue,
but will be as part of his pending classmap series. Seems like we
should covert to using module callback notifier for dynamic debug
anyways. First patch is just a cleanup.

Link: https://lore.kernel.org/lkml/20230113193016.749791-21-jim.cromie@gmail.com/

Thanks,

-Jason

Jason Baron (2):
  dyndbg: remove unused 'base' arg from __ddebug_add_module()
  dyndbg: use the module notifier callbacks

 include/linux/dynamic_debug.h | 13 ----------
 include/linux/module.h        |  3 +++
 kernel/module/internal.h      |  1 -
 kernel/module/main.c          | 30 ++++++---------------
 lib/dynamic_debug.c           | 49 ++++++++++++++++++++++++++++-------
 5 files changed, 51 insertions(+), 45 deletions(-)

-- 
2.17.1


             reply	other threads:[~2023-02-16 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 17:15 Jason Baron [this message]
2023-02-16 17:15 ` [PATCH 1/2] dyndbg: remove unused 'base' arg from __ddebug_add_module() Jason Baron
2023-02-16 17:15 ` [PATCH 2/2] dyndbg: use the module notifier callbacks Jason Baron
2023-02-17  6:02 ` [PATCH 0/2] dyndbg: let's use the module notifier callback jim.cromie

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=cover.1676566871.git.jbaron@akamai.com \
    --to=jbaron@akamai.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.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