All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Halaney <ahalaney@redhat.com>
To: Jason Baron <jbaron@akamai.com>, Jim Cromie <jim.cromie@gmail.com>
Cc: Andrew Halaney <ahalaney@redhat.com>, linux-kernel@vger.kernel.org
Subject: [PATCH v3 1/3] dyndbg: make dyndbg a known cli param
Date: Mon, 20 Sep 2021 15:54:42 -0500	[thread overview]
Message-ID: <20210920205444.20068-2-ahalaney@redhat.com> (raw)
In-Reply-To: <20210920205444.20068-1-ahalaney@redhat.com>

Right now dyndbg shows up as an unknown parameter if used on boot:

    Unknown command line parameters: dyndbg=+p

That's because it is unknown, it doesn't sit in the __param
section, so the processing done to warn users supplying an unknown
parameter doesn't think it is legitimate.

Install a dummy handler to register it. dynamic debug needs to search
the whole command line for modules listed that are currently builtin,
so there's no real work to be done in this callback.

Fixes: 86d1919a4fb0 ("init: print out unknown kernel parameters")
Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
---
 lib/dynamic_debug.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index cb5abb42c16a..84c16309cc63 100644
--- a/lib/dynamic_debug.c
+++ b/lib/dynamic_debug.c
@@ -761,6 +761,18 @@ static __init int ddebug_setup_query(char *str)
 
 __setup("ddebug_query=", ddebug_setup_query);
 
+/*
+ * Install a noop handler to make dyndbg look like a normal kernel cli param.
+ * This avoids warnings about dyndbg being an unknown cli param when supplied
+ * by a user.
+ */
+static __init int dyndbg_setup(char *str)
+{
+	return 1;
+}
+
+__setup("dyndbg=", dyndbg_setup);
+
 /*
  * File_ops->write method for <debugfs>/dynamic_debug/control.  Gathers the
  * command text from userspace, parses and executes it.
-- 
2.31.1


  reply	other threads:[~2021-09-20 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 20:54 [PATCH v3 0/3] Trivial dynamic debug fixups Andrew Halaney
2021-09-20 20:54 ` Andrew Halaney [this message]
2021-09-22 18:23   ` [PATCH v3 1/3] dyndbg: make dyndbg a known cli param jim.cromie
2021-09-20 20:54 ` [PATCH v3 2/3] dyndbg: Remove support for ddebug_query param Andrew Halaney
2021-09-20 20:54 ` [PATCH v3 3/3] Documentation: dyndbg: Improve cli param examples Andrew Halaney
2021-09-22 18:04 ` [PATCH v3 0/3] Trivial dynamic debug fixups Jason Baron
2021-10-08 15:58 ` Jason Baron
2021-10-08 16:01   ` Greg Kroah-Hartman
2021-10-08 16:27     ` Andrew Halaney
2021-10-13 11:35       ` Greg Kroah-Hartman
2021-10-13 13:54         ` Jason Baron
2021-10-13 15:40 Jason Baron
2021-10-13 15:40 ` [PATCH v3 1/3] dyndbg: make dyndbg a known cli param Jason Baron

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=20210920205444.20068-2-ahalaney@redhat.com \
    --to=ahalaney@redhat.com \
    --cc=jbaron@akamai.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.