Linux Modules
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Jason Baron <jbaron@akamai.com>
Cc: jim.cromie@gmail.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org
Subject: Re: [PATCH v3 0/2] dyndbg: let's use the module notifier callback
Date: Fri, 3 Mar 2023 14:06:27 -0800	[thread overview]
Message-ID: <ZAJvY5IiqTh4WXgm@bombadil.infradead.org> (raw)
In-Reply-To: <cover.1677861177.git.jbaron@akamai.com>

On Fri, Mar 03, 2023 at 11:50:54AM -0500, Jason Baron wrote:
> 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 to match other subsystems and remove core module code.
> First patch is just a cleanup.
> 
> Link: https://lore.kernel.org/lkml/20230113193016.749791-21-jim.cromie@xxxxxxxxx/
> 
> I've rebased this series onto modules-next tree. Although the first patch
> is a cleanup entirely internal to dynamic debug I think it's a nice cleanup
> to have as part of this series.

Thanks! Queued onto modules-next.

  Luis


      parent reply	other threads:[~2023-03-03 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 16:50 [PATCH v3 0/2] dyndbg: let's use the module notifier callback Jason Baron
2023-03-03 16:50 ` [PATCH v3 1/2] dyndbg: remove unused 'base' arg from __ddebug_add_module() Jason Baron
2023-03-06 17:56   ` Vincenzo Palazzo
2023-03-03 16:50 ` [PATCH v3 2/2] dyndbg: use the module notifier callbacks Jason Baron
2023-03-06 17:57   ` Vincenzo Palazzo
2023-03-09 20:58     ` Luis Chamberlain
2023-03-03 22:06 ` Luis Chamberlain [this message]

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=ZAJvY5IiqTh4WXgm@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@akamai.com \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@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